-
Bug
-
Resolution: Fixed
-
Neutral
-
1.3.1
-
-
Empty show more show less
-
Content Mngmnt 16 / Maintenace, Pages Maintenance 1, Pages Maintenance 2
-
3
Upon publishing some content, either in pages app or any content app, the published content on the author instance does not display the correct mgnl:lastModified date or time. Further, the published content on the public instance has the correct mgnl:lastModified value, but this property also gets updated for content that has not been modified (the sibilings).
Steps:
- Open some content app, i.e. Contacts
- Publish a contact
- Observe the mgnl:lastModified property on Author and Public
Actual Results
You will see that the published content in Author has the incorrect mgnl:lastModified value. You will also see that the published content on Public along with other content on the same app, has the mgnl:lastModified value updated.
Expected Results
the mgnl:lastModified property will display the proper date and time for only the content that has been published and no other content would have this property updated.
Other Notes
This is reproduceable in the demo.
Please see screenshots for examples:
Workaround
Set orderSiblings=false https://demo.magnolia-cms.com/.magnolia/admincentral#app:configuration;/modules/publishing-core/config:treeview:
Developments nodes
- why the metadata are updated if siblings are already in correct positions?
- if this really needs to happen, can we unwrap from MgnlPropertySettingNodeWrapper when ordering is in progress*?*
- caused by
-
PUBLISHING-82 Wrong order of nodes after publishing single page
- Closed