[MAGNOLIA-3445] the fact that the modification date falls back on the creation date is not respected in the tree view Created: 03/Dec/10  Updated: 20/Feb/15  Resolved: 03/Dec/10

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: None
Fix Version/s: 4.4.1

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-3442 modification date is null for content... 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)

 Description   

Since MAGNOLIA-3442 the MetaData.getModificationDate() falls back on getCreationDate() the implementation of MetaDataUtil.getPropertyValueString(Content, String, String) hides this as it doesn't use this methods.



 Comments   
Comment by Philipp Bärfuss [ 03/Dec/10 ]

test are failing

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