[MGNLCT-61] Reference fields to CT-retrofitted app does not work after restart Created: 10/Sep/18  Updated: 13/Dec/18  Resolved: 11/Dec/18

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

Type: Bug Priority: Critical
Reporter: Christopher Zimmermann Assignee: Christopher Zimmermann
Resolution: Obsolete Votes: 1
Labels: None
Remaining Estimate: 0d
Time Spent: 1h
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by MGNLUI-4537 Define relationships between content ... Closed
Relates
relates to MGNLUI-4824 Control of dependencies between CTs (... 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: Content Types finalization
Story Points: 8

 Description   

In order for a CT to have a reference to an existing App, such as Assets, it is necessary to "retrofit" that app - that is, to create a CT for that existing app, and to decorate that existing app with a new class and a "contentType" field.

After that has been done, the YAML file for the new CT must be "touched". After this, the reference fields are displayed correctly in the CT-generated editor subapp.

But, after a restart of Magnolia, the reference fields are no longer displayed correctly when the editor is opened. The log displays:

ERROR agnolia.ui.form.field.factory.AbstractFieldFactory: Unknown configured type Asset

If the CT file is then "touched" again, the editor works as expected - the references work again.

 



 Comments   
Comment by Aleksandr Pchelintcev [ 10/Sep/18 ]

czimmermann maybe module dependencies aren't properly declared? (if that currently effects the content types at all)

Comment by Christoph Meier [ 12/Sep/18 ]

I can confirm the bug - have tried it out with (hopefully proper) module dependencies. 

Comment by Hieu Nguyen Duc [ 11/Dec/18 ]

I tried reproducing it with a CT "page" and decorated app but didn't see the unknown configured type Page. I guessed it has been fixed by "lazy referencing" MGNLUI-4824

    - name: image
      type: asset
    - name: page
      type: page

Maybe someone could double-check and close it.

Comment by Christoph Meier [ 11/Dec/18 ]

hieu.nguyen,
my guess is, that MGNLUI-4824 has also fixed MGNLCT-61 (but it is just a guess).

Comment by Mikaël Geljić [ 11/Dec/18 ]

Thanks hieu.nguyen for confirming

Comment by Christopher Zimmermann [ 13/Dec/18 ]

Also confirmed.

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