[MAGNOLIA-3442] modification date is null for content that was not modified after creation Created: 03/Dec/10  Updated: 01/Jul/13  Resolved: 03/Dec/10

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.4
Fix Version/s: 4.4.1

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relation
is related to MGNLRES-31 set the creation date/modification da... Closed
is related to MAGNOLIA-3445 the fact that the modification date f... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

thus causing need for extra handling in templates and other code that needs to display mod date. The default value should be creation date instead since the act of creation is a modification of the content itself.



 Comments   
Comment by Tobias Mattsson [ 03/Dec/10 ]

MetaData.getModificationDate will now return the creation date if no modification date is set. The modification date is not set when the node is created. This avoids bloating the repository with the downside that queries will need to test for modification date being null.

Generated at Mon Feb 12 03:46:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.