Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: Blocker
Fix Version/s: 2.5
Affects Version/s: 2.5
Component/s: base system
Labels:
None

Template:
Acceptance criteria:

Empty

show more show less

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.

Acceptance criteria

depends upon

MGNLUI-375 Actions availability in Pages app initial state is wrong

Closed

is causing

MGNLSTK-1075 Infinite loop in TemplateCategoryUtil#isContentPage

Closed

MGNLSTK-1052 Template availability expects to be passed the parent node

Closed

MGNLSTK-1051 TemplateCategoryUtil should use NodeTypes.Renderable.getTemplate(Node)

Closed

is related to

MGNLUI-387 TemplateSelectorField queries for available templates using the wrong node

Closed

Assignee:: Federico Grilli

Reporter:: Federico Grilli

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 07/Dec/12 1:41 PM

Updated:: 11/Feb/13 11:42 AM

Resolved:: 07/Dec/12 4:33 PM

Date of First Response:: 10/Dec/12 2:28 PM

Details

Description

Checklists

Attachments

Issue Links

Activity

People

Dates