-
Bug
-
Resolution: Fixed
-
Neutral
-
6.2.22
-
None
-
None
-
-
Empty show more show less
-
Nucleus 19, Nucleus 20
-
2
Steps to reproduce
- On a content-app include a composite field
- Create an item and check the lastModifiedDate
- Edit the item and change some field within the compositeField
- Check the lastModifiedDate is not updated
- Change any other field outside the compositeField
- Check the lastModifiedDate is updated
Expected results
The lastModifiedDate is updated
Actual results
The lastModifiedDate is not updated
Workaround
Do not use mgnl:content (but any type inherited from it instead) as node type of content items.
Since the mgnl:content is used by default if not provided, therefore explicitly defined another nodeType under model of contentType would be a solution. see: https://docs.magnolia-cms.com/product-docs/6.2/Modules/List-of-modules/Content-Types-module/Content-type-definition/Content-type-Model-definition.html
your-content-type.yaml
datasource:
...
model:
//any nodeType excepts mgnl:content, e.g: mgnl:contentNode, mgnl:category
nodeType: mgnl:category
...
Development notes
N/A
Acceptance criteria
- caused by
-
MAGNOLIA-8125 Status color is not changed after modifying submodel data
- Closed
1.
|
Implementation | Completed | Jaromir Sarf | |
2.
|
Code review | Completed | Roman Kovařík | |
3.
|
PreintQA | Completed | Fernando Cherchi | |
4.
|
QA | Completed | Fernando Cherchi |