• geniusdivision

• in reply to: Date Picker fields in Repeaters gone wrong after WP 5.3 update
• November 21, 2019 at 10:54 pm

After all of this, I found a rogue instance of date_default_timezone_set("Europe/London"); in one of our plugin files.

When I have removed this everything is back to normal. Thanks for your help @elliot, this can be considered closed for me now.

• geniusdivision

• in reply to: Date Picker fields in Repeaters gone wrong after WP 5.3 update
• November 21, 2019 at 9:53 pm

Just to further update — I will figure this out 😃

@elliot — I think I’ve narrowed the issue down to something to do with Bedrock.

A default install of WordPress with the default theme displays the date correctly from the datepicker field.

I’m now going to install a default version of Bedrock with a default theme and see what this returns.

• geniusdivision

• in reply to: Date Picker fields in Repeaters gone wrong after WP 5.3 update
• November 21, 2019 at 9:29 pm

@elliot — unfortunately this hasn’t fixed it.

I can replicate the issue with this process:

1. Save a date in the backend of 2nd May 2020.
2. Save the post.
3. When the date is reviewed in the backend and the frontend the date is now displaying May 1st 2020.
4. When I reviewed the data in the database it’s saved correctly as May 1st 2020.

Here’s a quick video: https://www.dropbox.com/s/n7d3b1iyhyc7scd/1.%20Setting%20Date.mov?dl=0

It may help to know that we use https://roots.io/bedrock/ as a boilerplate for a better WordPress structure, but all our WordPress themes are built from scratch.

I tried changing the WordPress theme to a default one and I still experienced the same issue.

Happy to open up a new support ticket if this doesn’t help!

• geniusdivision

• in reply to: Date Picker fields in Repeaters gone wrong after WP 5.3 update
• November 21, 2019 at 12:46 am

It displays: November 18, 2019 8:30 am

• geniusdivision

• in reply to: Date Picker fields in Repeaters gone wrong after WP 5.3 update
• November 20, 2019 at 4:22 am

We don’t use date_default_timezone_set() in our themes and are experiencing this issue.

When I try to set a date to 2nd May 2020 it saves the value correctly in the database, but displays it incorrectly (a day behind) in both the admin screen and the front end of the site as per Elliot’s explanation.

• geniusdivision

• in reply to: Time Field and WP 5.3
• November 19, 2019 at 1:32 am

I’m having this exact same issue and I was hoping to find a solution here.

When I set a date for 2nd May 2020 and hit save it resets the date to 1st May.