The configuration of FORM between a new instance and a migrated instance must be the same (MGNLFORM-148)

[MGNLFORM-150] Add in a version handler the delta between the previous config (done with migration 1.1.2) and the new done with migration 1.2.x Created: 21/Jan/13  Updated: 29/Aug/13  Resolved: 30/Jul/13

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:
Relates
relates to MGNLMIGRATION-249 Fix integration tests of migration Closed
relation
is related to MAGNOLIA-5205 SetPropertyTask should be able to set... Closed
Template:
Date of First Response:

 Description   

Run a migration of Form with the migration module v1.2.1, export the configuration.
Start a fresh instance on magnolia 4.5.7, export the configuration of Form.

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.
http://hudson.magnolia-cms.com/view/Product_Team/job/magnolia-bundle_trunk/#3244/

Comment by Daniel Lipp [ 29/Jul/13 ]

Needs to be checked - together with MAGNOLIA-5205 it caused ce-bundle failure:

http://hudson.magnolia-cms.com/view/Product_Team/job/magnolia-bundle_trunk/#3244/

Generated at Mon Feb 12 05:37:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.