Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-2650

Nodes with colons not visible in JCR Browser

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 5.2.8, 5.3.2
    • 5.2.1
    • workbench
    • None

      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).

        Acceptance criteria

              pmundt Philip Mundt
              ahietala Antti Hietala
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD