Datepicker / Timezone inconsistencies

[tomgross]

BUG/PROBLEM REPORT (OR OTHER COMMON ISSUE)

There are several datepicker / timezone inconsistencies in Plone 5.1b3 (espacially in folder_contents)

1. • [ ] The datetime localization is not respected in the folder contents version of the datepicker. It IS respected on the edit page.
2. • [ ] Timezone offset is not handled, if browser TZ is not UTC and date is changed in folder_contents. It is correctly handled on edit page.

As a fix for 2. I trieds etting a custom timezone. I set a custom timezone in the resource registry {"date": {"selectYears": 200}, "time": {"interval": 5 }, "timezone": {"data": [{"id":"Europe/Berlin","text":"Europe/Berlin"}]}} like documented in the mockup build.

This fixed the timezone issue in folder_contents BUT lead to following even more severe issue:

3. • [ ] Datepicker is no longer displayed if timezone is set in datepicker options and it is impossible to change the date.

The JavaScript console shows an ugly traceback:

What I did:

For 2.

• Check if you system is not set to UTC timezone.
• Change the effective date to any value.
• Time should be the same is set but shown and saved with offset to UTC.

For 3.

• Configure timezone in @@resource-registy datepicker pattern options
• Change effective date of a page in folder contents
• Try to edit effective date in edit mode of a page.

What I expect to happen:

• Consistent handling of timezones in folder_contents, edit and view pages and listings
• Ability to set custom timezones and keep the consistent handling of timezones.

What actually happened:

• Timezone handling is inconsistent and setting a custom timezone does not work.

What version of Plone/ Addons I am using:

Plone 5.1b3 (minimalplone5)

[jensens]

still applies in RC1 (coredev of today)

[jensens]

see also #1298

[jensens]

I close the issue, because it addresses a Plone version that is no longer supported. If you think this is wrong please reopen the issue and assign a matching milestone.