-
Task
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Replace MetaData subnode by mixing.
see http://wiki.magnolia-cms.com/display/DEV/Concept+-+MetaData+as+mixin
- is causing
-
MGNLDAM-26 DAM workspace should use mgnl:lastModified as modification date not jcr:lastModified
- Closed
-
MGNLUI-169 MetaData as mixin: Adapt JcrContainers and configurations
- Closed
-
MGNLDAM-18 Adapt to metadata as mixin
- Closed
-
MAGNOLIA-4665 Create migration tool for converting metadata to mixins in bootstrap files
- Closed
-
MGNLSTK-1024 Update STK for metadata changes
- Closed
- is duplicated by
-
MAGNOLIA-3051 Ideas for improvements: drop the metadata node
- Closed
- is related to
-
MGNLUI-256 Pages app should use modification date from mixin
- Closed
-
MAGNOLIA-4741 Update task for converting MetaData to mixins
- Closed
-
MGNLACTIVATION-1 Re-apply changes required for MetaData as mixin
- Closed
-
MGNLDAM-27 Add mixins to mgnl:asset node type
- Closed
-
MGNLDATA-161 Update Data module for metadata changes
- Closed
-
MGNLUI-194 Add mixins to node type definitions mgnl:contact and mgnl:systemMessage
- Closed
-
MGNLUI-210 Use custom MarkNodeAsDeletedCommand until adminInterface is replaced
- Closed
-
MAGNOLIA-4651 Create proper types hosting constants and utils for our jcr nodeTypes and their properties
- Closed
-
MAGNOLIA-4681 MetaData nodes should be removed if emptied during import
- Closed
-
MAGNOLIA-4683 TemplatingFunctions should support retrieving properties from new mixins
- Closed
-
MAGNOLIA-4699 Complete our mixins with mgnl:title & mgnl:mimeType
- Closed
-
MGNLUI-167 MetaData as mixins: adapt columnFormatter and JcrNewNodeAdapter
- Closed