-
Notifications
You must be signed in to change notification settings - Fork 16
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
Include more migrations in default content migration #73
Labels
enhancement
New feature or request
Comments
Portlets can contain relations, for example the Collection portlet points to a Collection. I guess this is with a relation. |
No, it only stores a uuid:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some export/imports that do not rely on other content (that might not yet exists at the time of importing) could be included in the default export/import of content. One example is constrains which is implemented like that in #71
Other options are:
We could add hooks like
item = self.export_constrain(item, obj)
andself.import_constrain(obj, item)
for each to make it easy to override. We could also add checkboxes so enable/disable these extra-steps during export.In client projects I also export/import some marker-interfaces and annotations but I don't think that could be generalized.
It would probably be enough to add some more dokumentation with simple examples how that do that.
The text was updated successfully, but these errors were encountered: