[MGNLCT-143] jcrName field added in m6 content-type app Created: 07/May/20  Updated: 27/Oct/20  Resolved: 19/Oct/20

Status: Closed
Project: Content Types
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Sang Ngo Huu
Resolution: Obsolete Votes: 0
Labels: 62-misc
Remaining Estimate: Not Specified
Time Spent: 7.05d
Original Estimate: Not Specified

Attachments: PNG File Events App - Dynamic generated view column using name.png     Zip Archive MGNLCT143test.zip     PNG File app-m5.png     PNG File app-m6.png     PNG File image-2020-08-07-04-03-02-546.png     PNG File image-2020-08-07-04-14-53-132.png     PNG File image-2020-08-07-04-36-07-155.png     PNG File image-2020-08-07-04-41-54-834.png    
Issue Links:
Relates
relates to MGNLUI-6007 Dynamic generated contentType based a... Closed
relates to CONTTAGS-90 'Tag name' is incorrectly applied to ... Closed
causality
relation
is related to MGNLUI-6073 Name property in content types does n... Closed
supersession
is superseded by 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
Sprint: UI FW 10, UI FW 11, UI FW 12, UI FW 13
Story Points: 8

 Description   

With the same app and content-type definition It seems that the m6 app has an extra field 'jcrName', or that the field is not merged with a name field as it is in m5.

See these screenshots to see the differences.

I would expect the M6 app to have the same result as the M5 style app, I dont want the jcrName field.

 



 Comments   
Comment by Simon Lutz [ 18/May/20 ]
  • M6 requires 'jcrName' property, not 'name' as in M5
  • Moving from M5 to M6, the jcrName would be set to name if it wasn't used before (without special characters)
  • FTL will continue to work, content remains - the UI would show node names = jcrName
Comment by Christopher Zimmermann [ 18/May/20 ]

We had some discussion about at least 2 possible paths to take. 1) Inform customers that they need to migrate to the new handling of name/jcrName. or 2) provide backwards compatibility for customers so that they do not have to migrate anything.

Here some notes from PM/customer perspective if migration was required:

  • First I need to change my ContentType definition, I need to remove the name property (if I had it).
  • I need to add an i18n propery so that I dont get 'myapp.jcrName.label' label.
  • Then I need to do a migration on my content to rename all the 'name' properties to 'jcrName'.
  • I need to handle anywhere that the 'name' property was being used: my templates, my code, clients of the rest endpoint. (But its possible it was not used anywhere.)

 

And some more general feelings about any Migration efforts.....

  • Shoot, this does not work anymore? This is already bad if the developer discovers it, its worse if one of the users is discovering it and reporting to the developers the problem.
  • Why should I need to invest extra work in order to use the new version of Magnolia?
  • Hmm, this migration looks expensive. We've been thinking about another platform. Maybe lets postpone the migration effort and rather look deeper into switching.
Comment by Christian Ringele [ 01/Jul/20 ]

The problem is out if my view not the auto created 'jcrName' field, but that the auto created dynamic app uses the field 'name' to display the nodes name.

What should be either:
a) auto ‘jcrName’ in Form, AND dynamic app uses in view for node name the ‘jcrName’
b) auto ‘name’ in Form, AND dynamic app uses in view for node name the ‘name’
But not vise versa is it is:
Wrong: auto ‘jcrName’ in Form, BUT dynamic app uses in view for node name the ‘name’

Have a look into MGNLUI-6007:

 

Update, this is wrong:
"Because the BIG problem  is:

One can not get rid or overload the auto created view column using 'name'

So  you always have it there for nothing in the end. It just hurts."

I was now able to overload it with this code:

subApps:
  browser:
    workbench:
      contentViews:
        tree:
          columns:
            name:
              name: jcrName

I fell into the trap of this bug: CFGUI-119

Comment by Christian Ringele [ 14/Jul/20 ]

Using now a contentType based app with a model, I'm pretty sure it should display and use jcrName, as all others also do OTB.

Comment by Christopher Zimmermann [ 07/Sep/20 ]

slutz Could you provide more information on the proposed approach? Is it that in a contenttyupe file, or app file,  I could add a line that would cause it to use 'name' instead of 'jcrName'?

Comment by Šimon Demočko [ 19/Oct/20 ]

Superseded by MGNLUI-6007

Generated at Mon Feb 12 00:37:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.