[MGNLMIGRATION-192] Don't migrate structure of content of custom controls. Created: 13/Dec/12  Updated: 05/Mar/13  Resolved: 01/Mar/13

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: 1.2
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Robert Šiška Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
Template:
Acceptance criteria:
Empty
Release notes required:
Yes
Date of First Response:

 Description   

When there is a custom control which stores its data in a certain structure, don't migrate it as it were page.



 Comments   
Comment by Robert Šiška [ 08/Feb/13 ]

NPE error

Comment by Natascha Desmarais [ 11/Feb/13 ]

Add another constructor that goes without the blacklist parameter and calls the new constructor with blacklist=null to ensure backward compatibility with 1.2

Also, the blacklist parameter could use a little more detailed description (for example, is a path needed, or just the name?). Best would be probably to provide a code example within the comment.

Comment by Natascha Desmarais [ 01/Mar/13 ]

The idea was to overload the task that is actually called from all the (external) deltas: ContentModuleMigrationTask(...) sorry that I didn't point this out specifically the first time.

Comment by Robert Šiška [ 01/Mar/13 ]

@Natasha (facepalm) Of course, thanks. I didn't think, apparently.

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