7 | | To perform its tasks, quintagroup.transmogrifier basically uses: |
8 | | |
9 | | * [http://pypi.python.org/pypi/collective.transmogrifier collective.transmogrifier package] |
10 | | * [http://plone.org/products/marshall Products.Marshall product] |
11 | | |
12 | | Quintagrop transmogrifier functionality binds to Plone via portal_setup (GenericSetup) import/export interfaces. |
13 | | |
14 | | You can manage import/export procedure by configuring pipeline and appropriate blueprints in collective.transmogrifier configlet, which appears after products installation. |
15 | | |
16 | | = Common Use Case: Content Migration from Plone 3 to Plone 4 = |
17 | | |
18 | | Common task for quintagroup.transmogrifier package is migration of content from old Plone version to a new one. |
19 | | |
20 | | In the following example we describe the process of content migration from Plone 3.2.3 to Plone 4.0 instance (both Plone 3.2.3 and Plone 4.0 are buildout-based instances). |
21 | | |
22 | | So, to migrate content from Plone 3 website to Plone 4 you have to complete the following steps: |
| 7 | To migrate content from Plone 3 website to Plone 4 you have to complete the following steps: |