Extends feature breaks templates&dialog definitions (MAGNOLIA-3353)

[MAGNOLIA-3354] Extends Templates: Registered templates get lost below wrong configuration Created: 02/Nov/10  Updated: 21/Jun/11  Resolved: 16/May/11

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.3.8
Fix Version/s: 4.4.4

Type: Sub-task Priority: Major
Reporter: Christian Ringele Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen shot 2010-11-02 at 10.49.55 AM.png     PNG File Screen shot 2010-11-02 at 10.51.44 AM.png     PNG File Screen shot 2010-11-02 at 10.52.11 AM.png    
Template:
Date of First Response:

 Description   

Base setup:
Adding a template definition, which extends another template definition (see print screen).

Problem:
If the value of the extends property is set wrong, all template definitions registered below the wrong node are invalid.
So if placed for example below the stkSection (see print screen), all template below are not found anymore (print screen).

Behavior on correct reconfiguration:
When correcting the wrong extends value, all templates are registered correct again.

What should be changed:
Following template definitions of a wrong definition should be still registered. and usable.



 Comments   
Comment by Jan Haderka [ 02/Nov/10 ]

Actually I disagree. When the configuration is broken it should not be ignored, but propagated to the users otherwise it is much harder to track down later. This is the same for the case where you delete some node that is being extended by the others. Such extending nodes should stop working since they are no longer correctly configured. Is there an error message logged on setting incorrect value to extends? If not then this is IMHO the only thing that should change.

Generated at Mon Feb 12 03:45:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.