I am having the same issue. I couldn’t find in the menu where to roll back to the previous version of the plugin, so I restored the website itself with a backup I created.
Same for me, Datepicker not working. Rolling back to the previous version seems the only solution right now.
@mreichardt1992 How did you perform the rollback?
@lwillisjhls UpdraftPlus Backup Plugin
same here… does anyone have a copy of the last version or know where I can download?
Same issues with the latest version of the plugin. Locations fields are not working and not showing in wp-admin.
Rolling the plugin back didn’t work for me.
Hi Everyone,
I’m sorry for the delayed reply. It seems that none of our support staff has been on the forums in the past few days and have completely missed these issues and failed to bump it up to the developers. I’m going to investigate the lack of reply/support, however firstly I’m going to figure out this datepicker issue and make sure it’s resolved immediately!
Please bear with me… just know that I’m on the case now 🙂
I’ve just updated the dev version to 5.9.11.2 which I’m pretty sure will fix this issue.
You can upgrade via your dashboards with a few extra clicks as per these instructions, we should also follow up with a stable update within 24 hours.
The problem seems to have been a recent timepicker library change we made, the one we previously used isn’t maintained anymore and due to WP changing jQuery versions to 3.5 it uses some deprecated code that’d cause problems. However, Divi, ACF and probably other plugins use timepickers too with the same function names but different libraries which caused conflicts.
We’ve changed the library function names entirely so they’re unique and shouldn’t cause further issues with conflicts in this way.
If the issue remains, please let me know!
Thanks Marcus! I had also a problem with the locations field not working. Is this repaired also in this new version?
@folmolen I’ve just tested 5.9.11 with the conflicting plugins and yes, I do see the location field having issues as well (it uses JS, so part of the same problem). The new update should fix this too.
