[MGNLUI-5514] Editing app definition via resources causes detail subapp to fail (linkField) Created: 19/Nov/19  Updated: 05/Mar/21  Resolved: 05/Mar/21

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

Type: Bug Priority: Neutral
Reporter: Šimon Demočko Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File stacktrace    
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:

 Description   

Steps to reproduce: 

  1. On a local instance edit contacts-v8 app definition. http://localhost:8080/magnoliaAuthor/.magnolia/admincentral#app:resources:edit;/contacts/apps/contacts-v8.yaml:edit
  2. Make any change to the file. Adding a new line after datasource definition is enough. 
  3. Try to edit any contact, subapp does not open.

 

[rest of stack trace ommitted — open stacktrace attachment for more]

Caused by: java.lang.IllegalArgumentException: Could not find a chooser dialog definition at LinkField definition linkField at info.magnolia.ui.field.factory.LinkFieldFactory.<init>(LinkFieldFactory.java:67) ... 171 more

Note: This seems irreversible. Removing the edit does not help, nor does deletion of the JCR override (delete the edited file, publish deletion, reverts to previous config, the app still crashes)

I believe this is not related to the contacts app itself, but I failed to reproduce this with the DAM app second time. Even though I am pretty sure in the morning I somehow had that happen also in the new DAM app. If this turns out to be only contacts related, the ticket will be moved.



 Comments   
Comment by Roman Kovařík [ 05/Mar/21 ]

Closing this as can't reproduce.
Might be caused by a wrong YAML, marking the hotfix as deleted but actually having still the empty deleted version in place?

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