![]() |
|
|
|
|
Change By:
|
Philip Mundt
(22/Jul/14 7:56 AM)
|
|
Description:
|
Workbench cannot display nodes that contain a colon character. The Imaging module generates such nodes: {{jcr:content}}. This change was introduced with the move from DMS to DAM. In 4.5 the same node was named {{document}} and a JCR browser tree was able to display it.
4.5: {{/pop/promo/dms/demo-project/img/bk/Opener/coral-light/document}}
5.2: {{/pop/promo/dam/demo-project/img/bk/Opener/coral-light/jcr:content}}
This issue impacts users because trees like /trees/imaging will be phased out and replaced by the JCR Browser. A user cannot inspect the imaging workspace and learn how the rendition generation works, for example.
The issue is actually a combination of a not proper config (see attached screenshot for a correct one)
- {{includeSystemNodes}} should be specified as true
- a {{mgnl:resource nodeType}} missing in the configuration . This causes the generated query not to contain {{mgnl:resource}} which is subnode of {{jcr:content}}.
Still with this configuration {{jcr}} and {{mgnl}} properties are not visible which may not be the desired behaviour for a JCR browser. Reason for that is the hardcoded skipping of system properties at {{info.magnolia.ui.workbench.tree.HierarchicalJcrContainer.getChildren(Item)}}
(see: MGNLUI-3021).
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
