[MGNLUI-2765] Enhance template availability call and usage in pages app Created: 21/Mar/14 Updated: 09/Mar/21 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | pages app |
| Affects Version/s: | 5.2.3 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Eric Hechinger | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Description |
|
Currently TemplateSelectorFieldFactory and TemplateTypeRestrictionDropConstraint have to create a tmp child node in order to check the template availability. // creates a temporary node underneath the parent to overcome a restriction in template availability, // see MGNLSTK-1185 try { Node tempNode = associatedNode.addNode("temp", NodeTypes.Page.NAME); templates = templateAssignment.getAvailableTemplates(tempNode); associatedNode.getSession().removeItem(tempNode.getPath()); } catch (RepositoryException e) { log.error("Could not create temporary node to get available templates.", e); } This behavior may easily changed by:
|