Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sustainable exports #39

Open
sneridagh opened this issue Dec 3, 2024 · 0 comments
Open

Sustainable exports #39

sneridagh opened this issue Dec 3, 2024 · 0 comments
Assignees
Labels
01 type: bug something does not work 12 prio: high should be fixed soon

Comments

@sneridagh
Copy link
Member

sneridagh commented Dec 3, 2024

If we want to use plone.exportimport not just for "snapshots"/migrations but also for maintaining example content, we need to fix these:

  • It overrides always modified and created which are not needed/relevant, maybe for a migration, but not for a snapshot/example content.
  • The exportimport.versions field contain an object that changes the UID always... probably to the "previous" version of the last export...
  • It also exports fields with no value to null. In Plone RESTAPI idiom this is not needed, since in import all non existent fields should remain empty, not set.
  • It exports parents and items this are not required, nor needed by the import.

Maybe we should differentiate both use cases (snapshots/migration and example content)?

@sneridagh sneridagh added 01 type: bug something does not work 12 prio: high should be fixed soon labels Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
01 type: bug something does not work 12 prio: high should be fixed soon
Projects
None yet
Development

No branches or pull requests

2 participants