[MAGNOLIA-2737] Inconsistent date formatter. Created: 20/May/09  Updated: 04/Aug/15  Resolved: 04/Aug/15

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 4.0.1, 3.6.5
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Danilo Ghirardelli Assignee: Philipp Bärfuss
Resolution: Outdated Votes: 0
Labels: admininterface, date, format, formatter
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-876 Date: store using UTC, format using t... Closed
is related to MAGNOLIA-2285 Date format used in trees should be c... 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   

It seems that each module has its own formatting style, and with many modules it starts to be a little confusing.
To see an example of what I'm saying, go to the online Magnolia demo, and you'll see:

  • In Website panel dates are like "09-02-02, 11:43"
  • In Data Module panel -> type are "12/5/07 5:40 PM"
  • In Data Module panel -> config are "09-04-02, 12:13"
  • In Inbox panel are "5/20/09 1:11 AM"
  • In Security are "2007-04-19, 10:20"

And so on, with differences inside the same module. And this is just with the english default locale, I don't know if changing system locale or user language will get thing even worse.

There should be a single point in which should be possible to set the formatting style. A good candidate in the config repository would be the server/i18n/system/languages path, in which we can set the appropriate format for each language.

It was also suggested that AbstractTreeConfiguration should provide convenience method for date formating so that all the extending classes can just use it and use one format only instead of each of them doing it differently.



 Comments   
Comment by Danilo Ghirardelli [ 20/May/09 ]

I think it should be linked to MAGNOLIA-2285 and MAGNOLIA-876

Comment by Michael Mühlebach [ 04/Aug/15 ]

We're closing this issue as outdated as it was reported for 4.4.x or earlier versions which are no longer supported. Don't hesitate to reopen or create a new ticket in case this is still relevant and you'll experience it on 4.5.x or later versions.

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