You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.rst
+23-17Lines changed: 23 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Export and import all kinds of data from and to Plone sites using a intermediate
27
27
The main use-case is migrations since it enables you to for example migrate from Plone 4 with Archetypes and Python 2 to Plone 6 with Dexterity and Python 3 in one step.
28
28
Most features use `plone.restapi` to serialize and deserialize data.
29
29
30
-
See also the training on migrating with exportimport: https://training.plone.org/migrations/exportimport.html
30
+
See also the training on migrating with ``exportimport``: https://training.plone.org/migrations/exportimport.html
31
31
32
32
.. contents:: Contents
33
33
:local:
@@ -96,7 +96,7 @@ When a in-place-migration is not required you can choose this addon to migrate t
96
96
97
97
* Export content from a Plone site (it supports Plone 4 and 5, Archetypes and Dexterity, Python 2 and 3).
98
98
* Import the exported content into a new site (Plone 5.2+, Dexterity, Python 3)
99
-
* Export and import relations, users and groups with their roles, translations, local roles, ordering, dedault-pages, comments, portlets and redirects.
99
+
* Export and import relations, users and groups with their roles, translations, local roles, ordering, default-pages, comments, portlets and redirects.
100
100
101
101
How to migrate additional features like Annotations or Marker Interfaces is discussed in the FAQ section.
102
102
@@ -107,7 +107,7 @@ You can use this addon to
107
107
108
108
* Archive your content as json
109
109
* Export data to prepare a migration to another system
110
-
* Combine content from mutiple plone-sites into one.
110
+
* Combine content from multiple plone-sites into one.
111
111
* Import a plone-site as a subsite into another.
112
112
* Import content from other systems as long as it fits the required format.
113
113
* Update or replace existing data
@@ -156,8 +156,8 @@ To fix this you can check the checkbox "Modify exported data for migrations".
156
156
This will modify the data during export:
157
157
158
158
* Drop unused data (e.g. `next_item` and `components`)
159
-
* Remove all relationfields
160
-
* Change some fieldnames that changed between AT and DX
159
+
* Remove all relation fields
160
+
* Change some field names that changed between Archetypes and Dexterity
161
161
162
162
* ``excludeFromNav`` → ``exclude_from_nav``
163
163
* ``allowDiscussion`` → ``allow_discussion``
@@ -174,8 +174,8 @@ This will modify the data during export:
174
174
* ``contactName`` → ``contact_name``
175
175
* ``contactPhone`` → ``contact_phone``
176
176
177
-
* Update view names on Folders and Collection thet changed since Plone 4.
178
-
* Export ATTopic and their criteria to Collections with querystrings.
177
+
* Update view names on Folders and Collection that changed since Plone 4.
178
+
* Export ``ATTopic`` and their criteria to Collections with querystrings.
179
179
* Update Collection-criteria.
180
180
* Links and images in Richtext-Fields of content and portlets have changes since Plone 4.
181
181
the view ``/@@fix_html`` allows you to fix these.
@@ -191,8 +191,8 @@ You can choose between four options how to deal with content that already exists
191
191
* Update: Reuse and only overwrite imported data
192
192
* Ignore: Create with a new id
193
193
194
-
Imported content is initially created with ``invokeFactory`` using portal_type and id of the exported item before deserialing the rest of the data.
195
-
You can set additional values by specifying a dict ``factory_kwargs`` that will be passed to the facory.
194
+
Imported content is initially created with ``invokeFactory`` using portal_type and id of the exported item before deserializing the rest of the data.
195
+
You can set additional values by specifying a dict ``factory_kwargs`` that will be passed to the factory.
196
196
Like this you can set values on the imported object that are expected to be there by subscribers to IObjectAddedEvent.
197
197
198
198
@@ -558,7 +558,7 @@ Here we drop empty lines from the creators:
558
558
item["creators"] = [i for i in item.get("creators", []) if i]
559
559
return item
560
560
561
-
This example migrates a PloneHelpCenter to a simple folder/document structure during import.
561
+
This example migrates a ``PloneHelpCenter`` to a simple folder/document structure during import.
562
562
There are a couple more types to handle (as folder or document) but you get the idea, don't you?
563
563
564
564
.. code-block:: python
@@ -834,7 +834,7 @@ It may also happen, when you have validators that rely on content or configurati
834
834
835
835
.. note::
836
836
837
-
For relationfields this is not necessary since relations are imported after content anyway!
837
+
For relation fields this is not necessary since relations are imported after content anyway!
838
838
839
839
There are two ways to handle these issues:
840
840
@@ -1279,7 +1279,7 @@ This custom export exports and imports some selected settings and addons from a
1279
1279
**Import:**
1280
1280
1281
1281
The import installs the addons and load the settings in the registry.
1282
-
Since Plone 5 portal_properties is no longer used.
1282
+
Since Plone 5 ``portal_properties`` is no longer used.
1283
1283
1284
1284
.. code-block:: python
1285
1285
@@ -1450,7 +1450,7 @@ Export:
1450
1450
)
1451
1451
return actions
1452
1452
1453
-
Import exported PloneFormGen data into Easyform:
1453
+
Import exported ``PloneFormGen`` data into ``Easyform``:
1454
1454
1455
1455
.. code-block:: python
1456
1456
@@ -2131,6 +2131,13 @@ Written by
2131
2131
:alt:Starzel.de
2132
2132
2133
2133
2134
+
Translations
2135
+
============
2136
+
2137
+
This product has been translated into
2138
+
2139
+
- Spanish
2140
+
2134
2141
2135
2142
Installation
2136
2143
============
@@ -2147,14 +2154,14 @@ Install collective.exportimport by adding it to your buildout::
2147
2154
2148
2155
and then running ``bin/buildout``
2149
2156
2150
-
You don't need to activate the add-on in the Site Setup Add-ons control panel to be able to use the forms @@export_content and @@import_content in your site.
2157
+
You don't need to activate the add-on in the Site Setup Add-ons control panel to be able to use the forms ``@@export_content`` and ``@@import_content`` in your site.
2151
2158
2152
2159
You do need to add it to your buildout configuration and run buildout to make these features available at all. See https://docs.plone.org/manage/installing/installing_addons.html for details.
2153
2160
2154
2161
Installing in Plone 4
2155
2162
---------------------
2156
2163
2157
-
collective.exportimport depends on plone.restapi. For Plone 4, you need to pin plone.restapi to 7.x . When installing plone.restapi version 7.x.x in Plone 4 you may need to add the following version pins to your buildout::
2164
+
``collective.exportimport`` depends on ``plone.restapi``. For Plone 4, you need to pin ``plone.restapi`` to 7.x . When installing ``plone.restapi`` version 7.x.x in Plone 4 you may need to add the following version pins to your buildout::
2158
2165
2159
2166
[versions]
2160
2167
PyJWT = 1.7.1
@@ -2191,8 +2198,7 @@ collective.exportimport depends on plone.restapi . For Plone 4, you need to pin
2191
2198
contextlib2 = 0.6.0.post1
2192
2199
2193
2200
2194
-
These versions are taken from the plone.restapi 7.x README: https://pypi.org/project/plone.restapi/7.8.1/
2195
-
2201
+
These versions are taken from the ``plone.restapi`` 7.x README: https://pypi.org/project/plone.restapi/7.8.1/
0 commit comments