We just discovered that the date field enters the wrong date - a day earlier - when the pop-up calendar date is clicked on. We discovered it trying to enter November 12th when clicking in the pop-up calendar, but it entered November 11th into the field.
The client had clicked “localized” and I was able to replicate the issue when doing the same, but clicking “Fixed” and using the calendar to enter the date it did not happen.
We are both in the New York time zone, so I don’t know what the difference is. Does it think it is compensating for the end of daylight savings? (doubt that - a whole day????)
Here is what it says about Fixed vs. Localized in the docs:
Date
The Date field allows for quick entry of dates via the publish form. When the field has focus, a date-picker appears in the form of a calendar where you can select a day to enter into the field.
Field Options
Localized or Fixed?
On the publish form, along with a field to enter a date, you will also see an option to select whether you want the date localized or fixed:
Localized: A date that is localized will be translated into the logged-in member’s current timezone. For instance, if you enter a date of 10/21/2015 4:29 PM and you’re in Pacific Daylight Time, a member in Eastern Daylight Time will see the date as 10/21/2015 7:29 PM. Or, for logged out members, the date will be localized on the front-end according to the site’s configured timezone.
Fixed: A fixed date will NOT be localized to a member’s timezone, or the site’s configured timezone. The date will appear as it does in the control panel everywhere by all members.
So, being off by an entire day does not seem to be in the cards, but there you are.
Any insight on how I can avoid this would be welcome! 😊
Terry
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.