[MAGNOLIA-1548] admin central: mod. date is rendered or set wrongly Created: 23/May/07  Updated: 23/Jan/13  Resolved: 29/May/07

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 3.0.2
Fix Version/s: 3.0.3, 3.1 M2

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

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:

 Comments   
Comment by sebastian.frick [ 25/May/07 ]

i can see this behaviour on 3.0.1 too.

Comment by Rainer Blumenthal [ 29/May/07 ]

i was just looking at this problem, and figured out that, the "modificationDate" is set correctly
( --> if you just get it via "getModificationDate" and put it out - everything is fine)

so the error seems to occur during the render-process - the backend-data is OK

can u plz tell me where i can start searching for the error!?

Comment by Philipp Bracher [ 29/May/07 ]

do not use the utc timezone!

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