[MAGNOLIA-7415] Versioning and publication for different nodetypes using CT module Created: 20/Nov/18 Updated: 28/Dec/18 |
|
| Status: | Accepted |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.7.1 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Viet Nguyen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||
| Description |
|
Given a set of custom node-types: [bulletin] > mgnl:content [contentBlock] > mgnl:contentNode where bulletins may contain 0...n contentBlocks (similar to mgnl:page vs. mgnl:component, or mgnl:composition vs. mgnl:block). When publishing, by default, content-nodes (contentBlocks) are not published with their parent content (bulletin). The configuration point to include custom nodetypes into publication process is "itemTypes" under the activation command. Include custom nodetypes using comma separated format without space. From the restoreAllChildren action, one can set the flag RestorePreviousVersionCommand#parentNodeTypeOnly (in addition to #itemTypes), to false—which is otherwise to 'true' by default. See /modules/pages/apps/pages/subApps/browser/actions/restorePreviousVersion@parentNodeTypeOnly Then it works with these itemTypes: mgnl:contentNode,mgnl:metaData,mgnl:resource,contentBlock — We need to recollect the rationale why parentNodeTypeOnly is true by default, and whether mgnl:contentNode could be present in itemTypes by default. (cc rkovarik)
|