I have searched the 7.0.3 documentation, as well as the forums, and am still struggling to understand what is happening to my content. Let me first describe my problem:
When I look at content in my system, specifically content items that are going to be published as pages (we call them Topics), Nearly ALL of them have the same last modified date. When I look at certain (simple) resources that are used by these topics, some of the resources have the same last modified date, but most have last modified dates that look correct. After reading this thread it seems that the relationships between the content may be causing this, and frankly, we have a LOT of interconnected content, which seems to make things add up. It seems that the main body of my content is now an interconnected “bramble” and the last updated date will basically reflect the last time that “something” was updated, while the “endpoints” of my content will actually show true updated dates.
This is annoying but has not been critical in the past since we didn’t used to take any action based on that date, but now we are working on a new site with new content, (which happens to link back to the original site) which allows users to receive update emails notifying them of content changes. This now becomes a problem since the date in the database is changing even when the content is not.
So that’s a long way of getting to my question: How do I show a true “last modified” date that reflects the status of the individual content piece without regard to other related content?
One idea I have right now is to just create a new “last modified” field and use pre-processing on the content type to update it on save. Any reason this wouldn’t work? What other solutions are out there?