[MAGNOLIA-8514] Modified date is not updated after changing any field in compositeField Created: 03/Aug/22 Updated: 10/Oct/22 Resolved: 04/Oct/22 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 6.2.22 |
| Fix Version/s: | 6.3.0, 6.2.25 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Carlos Cantalapiedra | Assignee: | Jaromir Sarf |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
|||||||||||||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||||||||||||
| Template: |
|
|||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
|||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
|||||||||||||||||||||||||
| Bug DoR: |
[X]*
Steps to reproduce, expected, and actual results filled
[X]*
Affected version filled
|
|||||||||||||||||||||||||
| Date of First Response: | ||||||||||||||||||||||||||
| Epic Link: | Nucleus Quality Maintenance | |||||||||||||||||||||||||
| Sprint: | Nucleus 19, Nucleus 20 | |||||||||||||||||||||||||
| Story Points: | 2 | |||||||||||||||||||||||||
| Team: | ||||||||||||||||||||||||||
| Description |
Steps to reproduce
Expected resultsThe lastModifiedDate is updated Actual resultsThe lastModifiedDate is not updated WorkaroundDo 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 notesN/A |
| Comments |
| Comment by Roman Kovařík [ 04/Aug/22 ] |
The reason is, the mgnl:content (which is the type of tour items) is considered to be a legacy folder node types (use e.g. in the config workspace) thus it's state is not updated with child modifications, see info.magnolia.jcr.wrapper.MgnlPropertySettingContentDecorator.ChangeLastUpdateDateOp#resolveNodesToModify mgnl:category works fine. |
| Comment by David Lopez [ 31/Aug/22 ] |
Discussion 31/08/2022Above comments are more the supporting steps for "steps to reproduce", in which scenario it happens and in which not. Unfortunately we provide node type mgnl:contentNode as default so we cannot say that we don't support it, hence we would need to discover the possible fix. |
| Comment by Roman Kovařík [ 07/Sep/22 ] |
|
Discovery: MgnlPropertySettingContentDecorator#isFolder needs to hardcode a check for a workspace(s) like
|