[MGNLUI-5840] Compatibility: asset type in custom content app is saved without `jcr:` prefix Created: 27/Apr/20  Updated: 20/Jan/21  Resolved: 24/Sep/20

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.3
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Bartosz Staryga Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2020-04-27 at 08.57.37.png    
Issue Links:
Problem/Incident
causes MGNLDAM-927 CLONE - Provide compatibility to asse... Closed
causes MGNLUI-6289 Provide compatibility to asset links Closed
Relates
causality
is causing MGNLUI-6244 DOC: Provide examples for all preconf... 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: UI framework implementation

 Description   

Steps to reproduce

I am having content type with asset prop:

- name: logo
  label: Logo
  type: asset

Expected results

Save asset with`jcr:` prefix

Actual results

Auto generated app saves the asset without `jcr:` prefix e.g.:

Having this e.g. out of the box asset resolver is not working when creating the delivery endpoints.

Workaround

At the dialog definitions, change from:

appName: dam

To

appName: dam-chooser

That way, the image reference will be saved with the needed jcr: prefix and the REST call will resolve the Images references properly.

Development notes

Issue in compatibility - both should behave the same way.

 



 Comments   
Comment by Šimon Demočko [ 24/Sep/20 ]

In the meantime, we deprecated dam-chooser and replaced it with damLinkField, see https://documentation.magnolia-cms.com/display/DOCS62/Link+field 

Since it's deprecated, it should even show as a problem in definitions app. 

Comment by Bartosz Staryga [ 24/Sep/20 ]

sdemocko can we have example of using damlinkfiled in the docs?
that's the most used link field by devs and no example there

Comment by Šimon Demočko [ 24/Sep/20 ]

Sounds reasonable. I filed it as MGNLUI-6244. Feel free to add info there if necessary

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