[MGNLSTK-1009] Extends:override doesn't work as expected Created: 03/Oct/12  Updated: 27/Nov/12  Resolved: 27/Nov/12

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: paragraphs, templates
Affects Version/s: 2.0.4
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Zdenek Skodik Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

The use case is quite simple:

  • child site definition extends a parent, and overrides parts of areas, i.e. availableComponents
  • child page template definition extends a parent, and overrides parts of areas, i.e. availableComponents
  • these child definitions get merged and you end up with both lists of components to choose from, however one would expect to end up just with those defined on the page template definition level like usually


 Comments   
Comment by Milan Divilek [ 27/Nov/12 ]

It's not an issue because

What's defined in prototype is defined for area with disregard of template, such components are then globally available to any template registered for this site. One can then add any template specific components so that you end with list which results from merging this local template settings and global prototype. If any of those templates are meant to not use the given components from prototype, you disable them at the template level.

Generated at Mon Feb 12 07:32:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.