Plone Migration Tool for migrating content between two Plone websites that allows to export content from one Plone website and import it into another one.
Project description
quintagroup.transmogrifier package includes Plone blueprints for collective.transmogrifier pipelines
that are used for exporting/importing Plone site content. So, quintagroup.transmogrifier package can
be used as independent Plone Migration Tool by providing ways for handling content migration from one
Plone site to another. This package overrides GenericSetup 'Content' step - so this package can be used
out-the-box to migrate site content.
The included blueprints allow to:
* quintagroup.transmogrifierreturn queried items from the catalog
* create pipeline items from contents of Plone site folders
* walk through different GenericSetup import contexts and yield items for every folder
* generate and parse manifest files - listings of objects contained in some foldere in XML format
* migrate properties for objects that inherit from OFS.PropertyManager.PropertyManager mixin class
* use context sensitive components (adapters) to do needed corrections in data generated in previous sections
* set references for content objects
* migrate comments for site content
* extract data from Archetypes file fields
* apply stylesheet to some XML data stored on item.
You can manage import/export procedure by configuring pipeline and appropriate blueprints in quintagroup.transmogrifier
configlet that appears after products installation.
Apart from standard Plone content types migration, quintagroup.transmogrifier allows to carry out migration of
additional Plone content types. There are special packages used for such cases: these are
quintagroup.transmogrifier.simpleblog2quills (allows blog migration from SimpleBlog to Quills) and
quintagroup.transmogrifier.pfm2pfg (allows forms migration from PloneFromMailer to PloneFormGen).
Credits
-------
Design and development by:
* Bohdan Koval
* Andriy Mylenkyy
* Vitaliy Podoba
* Volodymyr Cherepanyak
* Myroslav Opyr
Changelog
=========
0.3 (2010-09-07)
----------------
- Plone4 compatibility [tomster, csenger]
- updated tests for Plone4 and Plone3 [fenix, liebster]
- added sections for export/import of portlet assignments [koval]
0.2 (2010-01-04)
----------------
- the "quintagroup.transmogrifier" namespace removed [koval]
- added interface import/export steps [mylan]
- merged plone21 branch [piv]
- various fixes [piv, mylan, koval]
- history update, release [chervol]
0.1 (2009-11-19)
----------------
- Initial release
that are used for exporting/importing Plone site content. So, quintagroup.transmogrifier package can
be used as independent Plone Migration Tool by providing ways for handling content migration from one
Plone site to another. This package overrides GenericSetup 'Content' step - so this package can be used
out-the-box to migrate site content.
The included blueprints allow to:
* quintagroup.transmogrifierreturn queried items from the catalog
* create pipeline items from contents of Plone site folders
* walk through different GenericSetup import contexts and yield items for every folder
* generate and parse manifest files - listings of objects contained in some foldere in XML format
* migrate properties for objects that inherit from OFS.PropertyManager.PropertyManager mixin class
* use context sensitive components (adapters) to do needed corrections in data generated in previous sections
* set references for content objects
* migrate comments for site content
* extract data from Archetypes file fields
* apply stylesheet to some XML data stored on item.
You can manage import/export procedure by configuring pipeline and appropriate blueprints in quintagroup.transmogrifier
configlet that appears after products installation.
Apart from standard Plone content types migration, quintagroup.transmogrifier allows to carry out migration of
additional Plone content types. There are special packages used for such cases: these are
quintagroup.transmogrifier.simpleblog2quills (allows blog migration from SimpleBlog to Quills) and
quintagroup.transmogrifier.pfm2pfg (allows forms migration from PloneFromMailer to PloneFormGen).
Credits
-------
Design and development by:
* Bohdan Koval
* Andriy Mylenkyy
* Vitaliy Podoba
* Volodymyr Cherepanyak
* Myroslav Opyr
Changelog
=========
0.3 (2010-09-07)
----------------
- Plone4 compatibility [tomster, csenger]
- updated tests for Plone4 and Plone3 [fenix, liebster]
- added sections for export/import of portlet assignments [koval]
0.2 (2010-01-04)
----------------
- the "quintagroup.transmogrifier" namespace removed [koval]
- added interface import/export steps [mylan]
- merged plone21 branch [piv]
- various fixes [piv, mylan, koval]
- history update, release [chervol]
0.1 (2009-11-19)
----------------
- Initial release
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
quintagroup.transmogrifier-0.3.zip
(165.5 kB
view details)
File details
Details for the file quintagroup.transmogrifier-0.3.zip
.
File metadata
- Download URL: quintagroup.transmogrifier-0.3.zip
- Upload date:
- Size: 165.5 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 2756bd94564f234ce3c4193500e791fb372e7ed94d5558c6c3d912a2de6a4394 |
|
MD5 | d132eb9c474dea64c19f8e46bdf90b51 |
|
BLAKE2b-256 | 83dd83e6c8211f6acc8e36e10d2278b4b68f025c8dba4de13369c27716e9c52e |