-
Improvement
-
Resolution: Fixed
-
Critical
-
3.5.4
-
None
-
None
Every node in magnolia gets the mix:versionable assigned no matter if the node is foreseen to be versioned or not (mgnl:contentNode, mgnl:metaData, ..). This slows down the saving process of created nodes a lot (about factor 4).
As we only version pages the mixin is needed on pages only.
The steps involved in the process would be:
- change info.magnolia.cms.core.DefaultContent.DefaultContent(Node, String, String, AccessManager)
- use mix:referencable (otherwise the activation mechanism is broken)
- change default nodetype definitions
- remove mixin from metaData
- add mixin to content (but not contentNode)
- update task for existing content
- use a proper nodetype for dms documents (not mgnl:contentNode)
Acceptance criteria
- is related to
-
MGNLTOOLS-9 update: content migration for mix:versionable
- Closed