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

JCR Browser App: Do not use 'jcrName' property value for the Node-Name column. One can not change NodeNames anymore!

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Critical Critical
    • 6.2.4
    • 6.2.1
    • jcr browser
    • None

      Tested:

      On current 6.2.2-SNAPSHOT

      Situation:

      • A node has the property 'jcrName' from a app.
        only when a Node has the proeprty 'jcrName' this problem exists. And all nodes generated form a genericApp will have it! see MGNLUI-6007
      • The JCR Browser app uses the 'jcrName' to display the name of the node, the default behavior of all apps.

      Problem Major:

      One can not change the node name! Not at all!

      One can double click the name, but only edits the value of the property 'jcrName' (orange) BUT NOT the node name itself (red) (not as the form field does in detail subApp). So the node name is untouched and can therefore not be changed via the JCR Browser app (red).

      Problem Minor

      You don't see the real physical node name in the JCR browser app, you always see the the 'jcrName' if existing. This is very confusing for beginners, and even for people with more experience. Especially it is an inconsistent behavior to all former JCR-Browsers.

       

      No workaround

      Also there is no workaround, I tried it with the decorator and all its variations:

      subApps: 
        browser: 
          workbench: 
            contentViews: 
              tree: 
                columns: 
                  name:
                    class: info.magnolia.ui.contentapp.column.jcr.JcrTitleColumnDefinition
                    #$type: jcrTitleColumn
                    propertyName: name
                    #name: name
      

      I would have expected targeting a non existing property will work, as also in all other apps. When the property does not exist, it usually displays the physical node name.
      But its not falling back to the node name when the property does not exists, which is strange behavior as it works properly if 'jcrBrowser' does not exist.

        Acceptance criteria

              Unassigned Unassigned
              cringele Christian Ringele
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD