[MGNLUI-6031] JCR Browser App: Do not use 'jcrName' property value for the Node-Name column. One can not change NodeNames anymore! Created: 08/Jul/20  Updated: 21/Oct/20  Resolved: 21/Oct/20

Status: Closed
Project: Magnolia UI
Component/s: jcr browser
Affects Version/s: 6.2.1
Fix Version/s: 6.2.4

Type: Bug Priority: Critical
Reporter: Christian Ringele Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File JCR-BrowserApp - jcrName Property Problem.png    
Issue Links:
causality
dependency
is depended upon by MGNLUI-6315 Migrate JCR Browser to new UI FW Closed
relation
is related to MGNLUI-6007 Dynamic generated contentType based a... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: nodeName

 Description   

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.



 Comments   
Comment by Roman Kovařík [ 21/Oct/20 ]

Closing as superseeded by MGNLUI-6007/MGNLUI-6336.

Generated at Mon Feb 12 09:32:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.