-
Bug
-
Resolution: Fixed
-
Minor
-
1.1
-
None
-
None
Sometimes using blossom this log appears:
WARN info.magnolia.module.admininterface.DialogHandlerManager.onRegister(DialogHandlerManager.java:95) Dialog definitions should be of type contentNode but [/modules/blossom/dialogs/autodetected] is of type content.
The problem is that DefaultBlossomParagraphRegistry calls RepositoryUtils.createEmptyConfigNode(PARAGRAPHS_PATH), and that method creates a node of type content, but now dialog nodes are required to be of contentNode type. Maybe it would be better to call that method to create all the required parent contents and only then create the last contentNode.
Acceptance criteria