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

Convert non "is_original" modules to a newly created module with aggregation during migration? #126

Closed
exponentcms opened this issue Apr 27, 2020 · 3 comments
Assignees

Comments

@exponentcms
Copy link
Owner

Consider un-linking modules made from existing content in pre-2.0 during migration and create a new module using aggregation and linking to other module (already migrated)

@exponentcms
Copy link
Owner Author

(from [6fd319c]) Implements aggregation during migration with modules created by existing content. Compared to previous implementation where multiple modules pointed to the same src/content, this version creates an additional module (with no content) and sets aggregation to point to the original module (with content).

[#66 state:resolved]
6fd319c

@exponentcms
Copy link
Owner Author

(from [d5fc336]) Implements aggregation during migration with OLD SCHOOL modules (calendar) created by existing content.

[#66 state:resolved]
d5fc336

@exponentcms
Copy link
Owner Author

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

No branches or pull requests

2 participants