Feature #51844

Fix date-format in edit-view of a record

Added by Stefan Neufeind about 6 years ago. Updated over 1 year ago.

Status:
Accepted
Priority:
Should have
Assignee:
Category:
FormEngine aka TCEforms
Start date:
2013-09-09
Due date:
% Done:

0%

PHP Version:
5.5
Tags:
Complexity:
Sprint Focus:

Description

If you configure the date-format for the BE to show as "d.m.y" it shows correct in the list-view. But edit-view for a record still has the "d-m-y"-format.


Related issues

Related to TYPO3 Core - Bug #49400: Fix date format in BE user module - might be easier than it looks like Closed 2013-06-25
Related to TYPO3 Core - Epic #77562: Misbehaviors with datetime values and timezones Accepted 2012-05-17

History

#1 Updated by Mathias Schreiber almost 5 years ago

  • Category changed from Backend User Interface to FormEngine aka TCEforms
  • Target version set to 7.4 (Backend)

#2 Updated by Susanne Moog over 4 years ago

  • Target version changed from 7.4 (Backend) to 7.5

#3 Updated by Benni Mack about 4 years ago

  • Target version changed from 7.5 to 7 LTS

#4 Updated by Mathias Schreiber about 4 years ago

  • Target version deleted (7 LTS)

#5 Updated by Mathias Schreiber about 4 years ago

  • Target version set to Candidate for patchlevel

#6 Updated by Daniel Goerz about 4 years ago

  • TYPO3 Version changed from 6.1 to 7

#7 Updated by Jo Hasenau almost 4 years ago

  • Status changed from New to Accepted
  • Assignee set to Jo Hasenau
  • TYPO3 Version changed from 7 to 6.2
  • PHP Version set to 5.5

This is already broken in 6.2 - so we should fix it in 6, 7 and master.

#8 Updated by Jo Hasenau almost 4 years ago

  • Status changed from Accepted to Needs Feedback

After taking a look at how the parameters are set and used in several core methods, I think the actual problem IS exactly that global system wide setting of a date format.

IMHO it does not make sense to use that global format for the rendering of date, time and datetime information, when the backend on the other hand offers different locales for the backend users.
As a German user I would expect dd.mm.yy, while the English user might need dd-mm-yy and the US user would like to see mm/dd/yy.

https://en.wikipedia.org/wiki/Date_format_by_country

So the whole concept should be changed to use the default formats of the chosen locale for the backend users, which then could use the global parameter as a fallback.
Maybe even that fallback would not be necessary, since the default would be English anyway.

So we should deprecate that parameter and fix the datetime handling system wide based on backend user locales.

#9 Updated by Jo Hasenau almost 4 years ago

Additionally there might be different formats for same language settings. i.e. for English US, English EN - so it seems useful to introduce a selectable date format that can be set within the backend user settings.

#10 Updated by Alexander Opitz over 3 years ago

  • Tracker changed from Bug to Feature
  • Status changed from Needs Feedback to Accepted
  • Target version changed from Candidate for patchlevel to 8 LTS

Changed to a feature request.

#11 Updated by Riccardo De Contardi almost 3 years ago

  • Target version changed from 8 LTS to 9.0

#12 Updated by Susanne Moog almost 2 years ago

  • Related to Epic #77562: Misbehaviors with datetime values and timezones added

#13 Updated by Susanne Moog almost 2 years ago

  • Target version changed from 9.0 to 9 LTS

#14 Updated by Susanne Moog over 1 year ago

  • Target version changed from 9 LTS to Candidate for Major Version

Also available in: Atom PDF