A tool that allows to migrate objects from a content-type to another
Project description
Introduction
This simple package allows to migrate from a portal-type to another. This is done by Products.contentmigration, we only provide a simple interface that allows to select source and destination portal_types.
Installation
You only need to add the product to eggs and launch the buildout. No installation needed, is only a view.
buildout.cfg:
[instance] eggs += rt.atmigrator
Usage
To migrate some contents, you only need to call “@@migrate-types” view in site root.
Remember to update the catalog after migration to align metadatas.
TODO
Handle more specific queries (for example filtering by path or review_state)
Handle custom migration behaviors (pre and post migration) for specified portal_types with some additional plugins
Compatibility
This product is tested with Plone 3.3.x and 4.2.x (with tests).
Changelog
0.1.0 (2013-03-12)
Initial release
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file rt.atmigrator-0.1.0.zip
.
File metadata
- Download URL: rt.atmigrator-0.1.0.zip
- Upload date:
- Size: 24.9 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 2ffeb819fe58d81f15652fccd840450fe4478a06c96a238cfa3ae8c0230aed17 |
|
MD5 | 3d2c0c0fa29df4e96b4e4418343d4859 |
|
BLAKE2b-256 | 0b02f9aaccd4a65e81621f4540b2dc9f4c2ebfe0abcaffb82a46f7308bef7e12 |