[MGNLCT-151] DOCS: Document that an M6 CT-app cannot 'reference' an M5-CT app Created: 24/Jun/20  Updated: 29/Sep/20  Resolved: 07/Sep/20

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

Type: Task Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLUI-5913 Problems with references in m6 conten... Closed
caused by MGNLCT-73 CT-generated apps can reference V8 st... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Documentation update required:
Yes

 Description   

Developers are likely to run into trouble in their migrations with references between apps. It must be clearly documented that 'reference' properties will lead to broken behaviour if an M6 CT-based app attempts to reference an M5 CT-based app.

It should also be documented how they can work around this by adding a link field explicitly in the app definition (not in the content type definition.)

For details, see: https://jira.magnolia-cms.com/browse/MGNLUI-6044



 Comments   
Comment by Christopher Zimmermann [ 07/Sep/20 ]

THis is fixed in Magnolia 6.2.3 - therefore no specific documentation changes are required.

See: https://jira.magnolia-cms.com/browse/MGNLCT-156

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