-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
5.2-rc1, 5.1.2
This cause problem during activation. SubApps node can be removed from public instance after activation. Activating Configuration:/modules/contact/apps for example will remove Configuration:/modules/contact/apps/contacts/subApps on the public instance. This is due to using mgnl:content for the subApps node, because parent node is type mgnl:contentNode.
MGNLUI-1123 ticket will have to be reverted -> will be done in MGNLUI-2379
- is related to
-
MGNLUI-1123 Cannot create a folder (mgnl:content) under a content node
- Closed
-
MGNLUI-2379 Change availability of add folder action in configuration app
- Closed
-
CNTCTSAPP-64 Primary node type of subApps is mgnl:content
- Closed
-
MGNLCAT-113 Primary node type of subApps is mgnl:content
- Closed
-
MGNLDAM-337 Primary node type of subApps is mgnl:content
- Closed
-
MGNLDATA-226 Primary node type of subApps is mgnl:content
- Closed
-
MGNLGROOVY-92 Primary node type of subApps is mgnl:content
- Closed
-
MGNLGS-47 Primary node type of subApps is mgnl:content
- Closed
-
MGNLINTEMPL-45 Primary node type of subApps is mgnl:content
- Closed
-
MGNLRES-79 Primary node type of subApps is mgnl:content
- Closed
-
MGNLREST-40 Primary node type of subApps is mgnl:content
- Closed
-
MGNLRSSAGG-123 Primary node type of subApps is mgnl:content
- Closed
-
MGNLUI-2380 Primary node type of subApps is mgnl:content
- Closed
- relates to
-
MGNLFORUM-266 subApps node hase wrong nodeType, is mgnl:content but should be mgnl:contentNode
- Closed