C.exportimport versions

Hi, I want to migrate a plone 5.0.5 site to 5.2 will collective.exportimport but I'm struggling to get it installed. So far I have pinned the following but not sure where/when it will end:

plone.restapi = 2.2.1
plone.schema = 1.2.0
importlib-metadata = 1.5.2
zipp = 1.1.1
diff_cover = 4.0.1

Does anyone have a versions file that pins all the right products?

Do you get conflicts? If not, then pinn plone.restapi to a version that still supports Plone 5.0.5 (I think any version below 8.0.0 should do that) and let buildout pick versions.

See Document version pins needed for Plone 4.3 (7.x.x) · Issue #1150 · plone/plone.restapi · GitHub for pinns that work in 4.3. They might also work in 5.0.5. Otherwise create a ticket there in plone.restapi and I will mirror the version-pinns in the exportimport-docs.

Thanks @pbauer, I got the buildout to run and got my first export by pinnging the following:

plone.restapi = 2.2.1
plone.schema = 1.2.0
importlib-metadata = 2.1.1
zipp = 1.2.0
configparser = 4.0.2
contextlib2 = 0.6.0.post1
pathlib2 = 2.3.6
scandir = 1.10.0
six = 1.16.0
pyrsistent = 0.16.1

Great. Make sure to check out the branch support_trees (Support export and import of content trees by pbauer · Pull Request #40 · collective/collective.exportimport · GitHub) since that also allows you to export the whole portal in one go.

1 Like

support_trees branch is great, thank you!

1 Like

I omitted 2 pins in my previous response, namely plone.api and PyJWT.

Here is the full list to get c.exportimport working on 5.0.5:

plone.restapi = 2.2.1
plone.schema = 1.2.0
importlib-metadata = 2.1.1
zipp = 1.2.0
configparser = 4.0.2
contextlib2 = 0.6.0.post1
pathlib2 = 2.3.6
scandir = 1.10.0
six = 1.16.0
pyrsistent = 0.16.1
plone.api = 1.11.0
PyJWT= 1.7.1

Note also that if you want to migrate PFG content to EasyForm before exporting, use the following pins to install it:

collective.easyform = 2.2.1
plone.schemaeditor = 2.0.18
plone.app.textfield = 1.2.8

Once installed, simply run /@@migrate-ploneformgen

And lastly, as @pbauer suggested, use the support_trees branch if it hasn't been merged.

1 Like

Plone Foundation Code of Conduct