?

Steps to reproduce the issue

  1. Create a custom date field for users
  2. Change DATE_FORMAT_CALENDAR_DATE language string to "%d-%m-%Y"
  3. Edit user profile
  4. Set custom field to 06-06-2006
  5. Save user profile

Expected result

Field value is expected to be 06-06-2006

Actual result

Field value is 20-06-2006

System information (as much as possible)

PHP7.1, Joomla 3.8.5

Additional comments

Changing the date format of custom field via DATE_FORMAT_CALENDAR_DATE to the dutch format (dd-mm-yyyy) results in incorrect dates after saving.

E.g. 06-06-2006 results in 20-06-2006

avatar internetdienstennederland internetdienstennederland - open - 22 May 2018
avatar joomla-cms-bot joomla-cms-bot - labeled - 22 May 2018
avatar franz-wohlkoenig
franz-wohlkoenig - comment - 22 May 2018

@internetdienstennederland can you please update to latest Version (3.8.7) and test Issue again?

Hint: For Today next Version 3.8.8 is announced.

avatar franz-wohlkoenig franz-wohlkoenig - change - 22 May 2018
Status New Information Required
avatar internetdienstennederland
internetdienstennederland - comment - 22 May 2018

It was fixed by changing all the DATE_FORMAT_* language strings. It is unsure with one actually solved the issue.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/20526.

avatar Bakual
Bakual - comment - 22 May 2018

The strings in question are the following

DATE_FORMAT_CALENDAR_DATE="%Y-%m-%d"
DATE_FORMAT_CALENDAR_DATETIME="%Y-%m-%d %H:%M:%S"
DATE_FORMAT_FILTER_DATE="Y-m-d"
DATE_FORMAT_FILTER_DATETIME="Y-m-d H:i:s"

It is mandatory that the CALENDAR one matches the FILTER one. They need to refer to the same format, but with different notations. Otherwise it is expected to fail.

I'm closing this issue since it apparently worked once the corresponding string was changed as well.

avatar Bakual Bakual - change - 22 May 2018
Status Information Required Closed
Closed_Date 0000-00-00 00:00:00 2018-05-22 12:13:58
Closed_By Bakual
avatar Bakual Bakual - close - 22 May 2018

Add a Comment

Login with GitHub to post a comment