Page History
...
Devstatus |
---|
...
|
...
|
...
| ||
Solved by using Solution C |
Officialdocu | ||||
---|---|---|---|---|
| ||||
Changing the node types
A) Change node type definition
...
B) Add mixins dynamically
Code Block |
---|
Index: /Users/philipp/checkout/magnolia/magnolia-core/src/main/java/info/magnolia/cms/core/DefaultContent.java
===================================================================
--- /Users/philipp/checkout/magnolia/magnolia-core/src/main/java/info/magnolia/cms/core/DefaultContent.java (revision 14777)
+++ /Users/philipp/checkout/magnolia/magnolia-core/src/main/java/info/magnolia/cms/core/DefaultContent.java (working copy)
@@ -168,7 +168,12 @@
this.setRootNode(rootNode);
this.node = this.rootNode.addNode(this.path, contentType);
this.setAccessManager(manager);
- this.addMixin(ItemType.MIX_VERSIONABLE);
+ if(this.getItemType().equals(ItemType.CONTENT)){
+ this.addMixin(ItemType.MIX_VERSIONABLE);
+ }
+ else{
+ this.addMixin(ItemType.MIX_REFERENCEABLE);
+ }
// add mix:lockable as default for all nodes created using this manager
// for version 3.5 we cannot change node type definitions because of compatibility reasons
// MAGNOLIA-1518
|
...
A) remove all version related properties
B) keep mix:versionable for contentNode
C) remove all version related properties
Possible approaches
- import, call update tasks, export
- xml based cleanup code / script
Update
For that we must write some test
Overview
Content Tools