Convert non "is_original" modules to a newly created module with aggregation during migration?
Reported by dleffler | March 26th, 2011 @ 03:53 PM | in Release Candidate 1 (closed)
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)
Comments and changes to this ticket
-
expNinja April 26th, 2011 @ 02:56 AM
- State changed from “open” to “resolved”
(from [6fd319ce4bd324d62acb2331cac440215e2258f1]) 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] https://github.com/exponentcms/exponent-cms/commit/6fd319ce4bd324d6...
-
expNinja April 26th, 2011 @ 03:49 AM
(from [d5fc336b6c7ff6d4e742a33da6d276833e018191]) Implements aggregation during migration with OLD SCHOOL modules (calendar) created by existing content.
[#66 state:resolved] https://github.com/exponentcms/exponent-cms/commit/d5fc336b6c7ff6d4...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
People watching this ticket
expNinja
Tags
Referenced by
-
66
Convert non "is_original" modules to a newly created module with aggregation during migration?
[#66
state:resolved]
https://github.com/exponentcms/expo...
-
66
Convert non "is_original" modules to a newly created module with aggregation during migration?
[#66
state:resolved]
https://github.com/exponentcms/expo...