[MGNLMIGRATION-206] Inheritance - it should not be configured in a page definition but only in the site definition Created: 10/Jan/13  Updated: 27/Feb/13  Resolved: 25/Feb/13

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

Type: Bug Priority: Neutral
Reporter: Natascha Desmarais Assignee: Samuel Schmitt
Resolution: Fixed Votes: 0
Labels: inheritance, migrationto45
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File config.modules.extended-templating-kit.config.sites.update-training.xml     PNG File migration_inheritance_behavior.png    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

As we set by default an inheritance configuration on all extra nodes (site def and pages template), this has a drawback when we want to change the default setting.
Let's say by default it's on "components=all" and i want "components = filtered". I have to update the sitedef and remove it form all the pages templates.
For this reason we must just put the inheritance config in the site def.



 Comments   
Comment by Samuel Schmitt [ 11/Jan/13 ]

Maybe something to do in 10. Remove template redundancy

Comment by Samuel Schmitt [ 15/Jan/13 ]

No more inheritance node on pages defintion

Comment by Jan Haderka [ 23/Jan/13 ]

First commit seems to be completely unrelated to this ticket. Perhaps it belongs to some other ticket? IF so please make sure to mention it in the comment for future reference.

Comment by Samuel Schmitt [ 23/Jan/13 ]

First commit is not relevant to the current issue, it is link to this ticket MGNLMIGRATION-203.

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