[MGNLSTK-1050] Template availability no longer working correctly Created: 07/Dec/12  Updated: 11/Feb/13  Resolved: 07/Dec/12

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: base system
Affects Version/s: 2.5
Fix Version/s: 2.5

Type: Bug Priority: Blocker
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLSTK-1075 Infinite loop in TemplateCategoryUtil... Closed
is causing MGNLSTK-1052 Template availability expects to be p... Closed
is causing MGNLSTK-1051 TemplateCategoryUtil should use NodeT... Closed
dependency
depends upon MGNLUI-375 Actions availability in Pages app ini... Closed
relation
is related to MGNLUI-387 TemplateSelectorField queries for ava... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

During the latest tests run I realized that several things are broken with template availability.
This is partly due to the metadata as mixin changes and partly to the fact that before a page was first created then its properties set, whereas now a the two operations are done at the same time. Bottom line: old code needs to be adapted.



 Comments   
Comment by Tobias Mattsson [ 10/Dec/12 ]

I'm closing the ticket because the Sprint has ended. This problem is actually the cause of a bug in MGNLUI and the changes made in this ticket only creates a workaround for it. I have filed MGNLSTK-1052 to revert this and MGNLUI-387 to fix it for real.

Also created MGNLSTK-1051 for the use of PropertyUtil rather than NodeTypes.Renderable.getTemplate().

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