-
Bug
-
Resolution: Fixed
-
Neutral
-
5.3
The ContentAppMigrationTask between 5.2.x and 5.3 uses a bunch of QueryTasks as subtasks. Because JCR queries may NOT account for unsaved changes in current session (see MAGNOLIA-5857), this results in incomplete updates for some modules, when updating straight from 4.5 to 5.3.
We should replace these QueryTasks with newly-introduced NodeVisitorTask.
Acceptance criteria
- is depended upon by
-
MGNLDATA-257 Cannot start companyApp after update from Magnolia 4.5.19
- Closed
-
MGNLDATA-261 Migration diffs when migrating from 4.5 to 5.2.x
- Closed
- mentioned in
-
Page Loading...