The configuration of FORM between a new instance and a migrated instance must be the same
(MGNLFORM-148)
|
|
| Status: | Closed |
| Project: | Magnolia Form Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.4.8, 2.0.3, 2.1 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Samuel Schmitt | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
Run a migration of Form with the migration module v1.2.1, export the configuration. Both configuration must be compared and the delta must be represented by a task in the version handler. |
| Comments |
| Comment by Robert Šiška [ 23/Jul/13 ] |
|
Differences between updated and fresh installations are now detected automatically by magnolia-migration-integration module. |
| Comment by Jan Haderka [ 26/Jul/13 ] |
|
You can't change the update task in 4 minor versions back ... that won't be executed again if someone already ran the migration. Instead you need new update task for the latest version (1.4.8) to check current value of that property and set it right if it is still different. |
| Comment by Daniel Lipp [ 29/Jul/13 ] |
|
Both tickets together cause ce-bundle to fail - e.g. |
| Comment by Daniel Lipp [ 29/Jul/13 ] |
|
Needs to be checked - together with http://hudson.magnolia-cms.com/view/Product_Team/job/magnolia-bundle_trunk/#3244/ |