[MGNLCMNT-73] The configuration of Commenting between a new instance and a migrated instance must be the same Created: 21/Jan/13  Updated: 06/Dec/13  Resolved: 29/Jul/13

Status: Closed
Project: Commenting (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.5

Type: Task Priority: Major
Reporter: Samuel Schmitt Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLCMNT-86 CLONE - The configuration of Commenti... Closed
dependency
is depended upon by MGNLMIGRATION-216 Define integration tests in order to ... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLCMNT-75 Add in a version handler the delta be... Sub-task Closed Robert Šiška  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

As discussed for STK (MGNLSTK-1073), when the migration module change its logic it could happen that a new version of Commenting and a migrated one dont have the same configuration.



 Comments   
Comment by Jan Haderka [ 26/Jul/13 ]

While the subtasks ensures, there is no difference between what migration module produces and what is clean installation, there is still the diff if someone already ran the migration. We need normal update task in the latest version to check as well.

Comment by Jan Haderka [ 08/Oct/13 ]

Fix for this issue was reverted on master in http://git.magnolia-cms.com/gitweb/?p=modules/commenting.git;a=commit;h=727f40bcfb3a1f225312d09afab0f0ea99f7f5e3 while releasing alpha-1 version.

Generated at Mon Feb 12 00:02:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.