some changes for plone2.1 export #1

Open
wants to merge 29 commits into from

3 participants

@yboussard
Plone Collective member

Add possibility to configure export via ini file and I had a new Article322Wrapper

yboussard added some commits Feb 23, 2011
@yboussard yboussard 1 - Add possibility to configure export via ini file.
    This file is located in $INSTANCE_HOME and is name jsonmigrator.ini.
    You can configure the mapping of class
    2 - Add new options :
    MAX_CACHE_DB : purge zodb cache every x item treat (avoid memory error on big Data.fs)
    JUST_TREAT_WAPPER : just treat classname that are mapping on a wrapper
    3 - Add logging support
    4 - Add Article322Wrapper -> for old plone article
ba8abb3
@yboussard yboussard add some documentation to plone2.0_export.rst 4db2f82
@yboussard yboussard add some documentation to plone2.0_export.rst 2d3c657
@yboussard yboussard add some documentation to wrappers e0c3acf
@garbas

nice .. i have some work on migration scripts planned tomorrow and i'll also look what you done here. will get back to you tomorrow.

@yboussard
Plone Collective member

Hi,

I do some change to jsonmigrator . Now plone2.0_export.py add some extra info for attached field (import as BaseUnit to preserve filename, encoding ...) . Add also some work for plone article (see updated documentation) and lingua plone relation.

Regards Youenn.

@idgserpro
Plone Collective member

@yboussard collective.blueprint.jsonmigrator was "renamed" to collective.jsonmigrator.

Would you mind:

  • Checking collective.jsonmigrator source code and see if something similar to your pull was done there;
  • If nothing similar was done, redo the PR in collective.jsonmigrator.

...since the plans for collective.blueprint.jsonmigrator is to make it inactive?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment