document node modification time does not reflect change in document-node's content

[mad99]

Description

When an Editor change some content from a document node, like text, headline or every other nodeType, lastmodificationdatetime of this particular content-element changes.
But lastmodificationdatetime from wrapping Document-node does not change.

A: So at least the <lastmod>-Tag in sitemap.xml is wrong.

Same situation for dimensions-changed content. I guess at the end, when a editor change/add same german content, but english is still untouched, the entry for this document-node in website.com/de/sitemap.xml should have an other <lastmod>-datetime then the entry in website.com/en/sitemap.xml.

B: <lastmod>-Tag in dimensional/translated sitemap.xml is wrong.

But also make it quite impossible to aware of the last-change or if a document-node has some change after a while.

C: Impossible to monitor changes in a document-node at all.

Steps to Reproduce

1. Click on a DocumentNode/page in siteTree-Panel in Backend
2. Notice under Additional info > «Last modification» from the Root-Node in Structure Panel
3. Change some Content > Apply > Publish to live
4. Look under Additional info > «Last modification» from this element
5. Click back to Root-Node in Structure Panel
6. Check under Additional info > «Last modification» from the Root-Node in Structure Panel
7. It is the same date like under 2. point, NOT LIKE Element's «Last modification»-datetime.

Expected behavior

When change one content-element from a document-node, document-node's «Last modification» have to reflect/change to the changed/added Element's «Last modification»-datetime!

Actual behavior

document-node's «Last modification»-datetime does not change when some wrapped child-content change/add. Also document-nodes with dimensions (different languages) does not reflect each dimension-entry for it's own.

Affected Versions

I guess since the beginning of Neos-time: Version 0.1/1.0/ ...

Neos:
3.1.4
Flow:
4.1.4

[kdambekalns]

Huh, old issue, but of course partly valid and still an open issue.

• Valid, because of things like Calculate lastmod in XML sitemap based on document and it's content neos-seo#40 (last modification of a document rendered as a whole)
• Invalid because the node's data should only reflect the node itself (i.e. when changing a childnode, the parent node does in fact not change at all)

[markusguenther]

Stumbled upon the behavior and also expected that if I change a content node and publish them, that the publishing and modification date of the document node will be changed. So this is not just modification time. It is also the last publishing that is not effected.

I mean, technically, the document node has not been published and not modified. But if we don't adjust the node, we should maybe offer a helper to get the information. Although this will cost more than just adjust the values in the store.

[kdambekalns]

I mean, technically, the document node has not been published and not modified.

Right. And I would not change that behaviour!

But if we don't adjust the node, we should maybe offer a helper to get the information.

Ab-so-lutely!