Yes, I can change the return value and make it work.
However, I’ve used the third party datetime-picker for a lot of functionality during recent years. Its not only for displaying a date and time on a website. Its for schedule import and export of business systems, apis, woocommerce integrations, integrations with booking systems, etc. All these projects will need to be re-tested.
How about disable the new core functionality for datetime-picker if the third party datetime-picker exists?
Yes, I know.
After update to 5.3.9.1 the fields defaults back to this:
Display format: 16/06/2016 10:00 am
Return format: 16/06/2016 10:00 am
Hi Elliot,
Both on the front end and when entering a value.
Date Format is yymmdd
Time Format is HH:mm
Save as timestamp? no
Get field as timestamp? no
I’ve tried with one of my development websites and I still have a problem with 24h time. It should display as 15:30, but it displays as 16 3:3. Isn’t there a way to just implement them side by side? So that I don’t need to modify the code on 30+ project that is using this third party datetime picker?
I’ll create a new support ticket later tonight if I find the time.
I’ve written a lot of functionality based on the acf-field-date-time-picker plugin. Yesterday, I tried to update by first disabling third-party plugin, but it does not work. On this particular website, posts are deleted after a specific date and time. This just deleted 600+ posts and I had to restore from backup. The client wasn’t happy.
On another website, I updated and tried to re-save the posts (26 different posts with opening times, vacations, special opening times etc). They all returned the current timestamp. Restore from backup once again.
So, it’s just not a solution to remove the third party acf-field-date-time-picker and update acf pro. It breaks the previous functionality.
I got the same problem. I had to upload an old version of ACF Pro to a lot of clients websites. This also breaks the functionality, even after I disabled the acf-field-date-time-picker plugin.
The new function should be implemented using a different function name since it’s not working in the same way, allowing both date/time-pickers to be enabled.
