[MGNLUI-6007] Dynamic generated contentType based apps: Usage of 'jcrName' and 'name' property unclear Created: 01/Jul/20 Updated: 09/Nov/20 Resolved: 15/Oct/20 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | app, app framework, content app, content types |
| Affects Version/s: | 6.2.1 |
| Fix Version/s: | 6.2.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Christian Ringele | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 7h 19m | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | nodeName | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | UI FW 11, UI FW 12, UI FW 13 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 8 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
Tested:On current 6.2.2-SNAPSHOT Situation:contentType 'event' contains a model. Scope of questions:
Strange things I observed: Former use case:One defines via 'name' property in the contentType's model the possibility to:
Only one field in the details form is the goal! Problem now:
No proper way to define an "Event Name". Situation:Case 1 & 2 behave absolutely the the same (always yellow in print screens): Case 1: #Case 1 - no 'name' or 'jcrName' datasource: workspace: events namespaces: mt: https://www.magnolia-travel.com/jcr/1.0/mt autoCreate: true model: nodeType: event properties: - name: location required: true Case 1: #Case 2 - only 'jcrName' datasource: workspace: events namespaces: mt: https://www.magnolia-travel.com/jcr/1.0/mt autoCreate: true model: nodeType: event properties: - name: jcrName required: true - name: location required: true Case 3: #Case 3 - all possible names. Especially former working 'name' datasource: workspace: events namespaces: mt: https://www.magnolia-travel.com/jcr/1.0/mt autoCreate: true model: nodeType: event properties: - name: jcrName required: true - name: name required: true - name: eventName required: true - name: location required: true
Case 1 & 2 in the dynamic generated Detail's Form:
Case 3 in the dynamic generated Detail's Form:
Case 1 & 2 (yellow) and Case 3 (Orange) in JCR App:
Case 1 & 2 (yellow) and Case 3 (Orange) in Content App:
Related problem
What is the mean/wanted behaviorTo handle name for nodes including special characters (display, rename, duplicate operations):
JCR browser shows only real node names, doesn't synchronise any property during previously mentioned operations (reminder: JCR browser is an app for developers, manipulation of content via this app should be avoided in production environment). |
| Comments |
| 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: Have a look into
Update, this is wrong: One can not get rid or overload the auto created view column using 'name' 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: |
| 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 'name', as all others also do OTB. Having to use '' is also very cumbersome in all templating. |
| Comment by Christian Ringele [ 30/Sep/20 ] |
|
Out of my view this is resolved since 6.2.3. Instead of this code (6.2.2): name: name: jcrName ## Needed until MGNLUI-6007 is resolved. nodeTypeToIcon: event: icon-datepicker I can now use this proper code (6.2.3): jcrName: nodeTypeToIcon: event: icon-datepicker |
| Comment by Roman Kovařík [ 15/Oct/20 ] |
|
For documentation: new JcrDatasourceDefinition#nodeNameProperty configuration:
|
| Comment by Ashraf Khamis [ 15/Oct/20 ] |
|
Added the new nodeNameProperty to https://documentation.magnolia-cms.com/display/DOCS62/JCR+data+source. Reviewed by Roman. No entry required for the 6.2.4 release notes. |
| Comment by Šimon Demočko [ 20/Oct/20 ] |
|
Copying from slack: Trying to rename item in JCR to another item with the same name does not validate, but throws an exception instead. Also, the rename is editing jcrName instead of node name, but that's intentional, I guess Gif in this thread: https://magnolia-cms.slack.com/archives/CKSC4TJQK/p1603194523192000?thread_ts=1603194482.191800&cid=CKSC4TJQK |
| Comment by Šimon Demočko [ 20/Oct/20 ] |
|
( If you rename the jcrName property to sth else like "jcrNamea" then the rename node dialog shows the node name, not the jcrName anymore. The same problem occurs when inline editing Gifs in thread: https://magnolia-cms.slack.com/archives/CKSC4TJQK/p1603207729201100 |
| Comment by Šimon Demočko [ 20/Oct/20 ] |
|
Rename item action in a content-type generated app shows node-name in the dialog instead of the actual name of the content. (escaped with dashes etc.) |
| Comment by Šimon Demočko [ 20/Oct/20 ] |
|
When you create a page, if the name has spaces, it will store it with dashes instead of spaces. This was there before. But now when you rename, you can rename it so it has spaces. When you create a page, there is no name nor jcrName property to it. When you rename a page using rename item action in Pages app, jcrName property is created under that page |
| Comment by Šimon Demočko [ 20/Oct/20 ] |
|
For the sake of completeness, I'll add my note here about dialog validation showing node-name instead of name when failing validation during renaming of a Persona to a name that already exists. |
| Comment by Roman Kovařík [ 21/Oct/20 ] |
|
Closing this as split into follow up issues under |