-
Story
-
Resolution: Outdated
-
Major
-
None
-
None
-
None
As a developer I want my M6 contentTypes-based app to reference M5 contentTypes-based apps so that I can benefit from contentTypes easy usage when I am linking to apps that have not been upgraded to M6.
Developers will want to use the new framework and upgrade their apps to M6. Also internally at Magnolia we want to upgrade demo projects to M6. However these apps often need to link to M5 contentTypes, such as those shipped by Magnolia like 'Categories' and 'Stories', or those shipped in other modules, that the developer does not have control over.
If M6 contentTypes do not support linking to m5 contentTypes, then developers need to resort to the "inline decoration' feature in the app definition to supply the linkField by hand. Doing this makes contentTypes harder to use and understand and makes demos more complicated and less convincing.
- depends upon
-
MGNLUI-5350 Cut number of columns visible in chooser by default, make configurable
- Closed
- is related to
-
MGNLUI-6044 LinkField to M5 app not working in detail sub apps
- Closed