Hello @joeroyhud @adammish @pderas @mhighley @phoenixmagoo
I have some info for you, partially triggered by phoenixMagoo.
The date_dafault_timezone_set
function should not be used any more as per WP recommendation. See the ‘Not recommended’ section here:
Date/Time component improvements in WordPress 5.3
We will be removing that from our code as well, though it is only used in edge cases for recurring events.
Other plugins / themes however might be using that function, so it can cause this issue on the site. Probably the best way moving forward would be doing a full conflict test and determining which plugin is causing this.
Here’s a link to our conflict testing guide:
https://theeventscalendar.com/knowledgebase/testing-for-conflicts/
Once the responsible plugin / theme is found, then disabling that plugin and notifying the plugin / theme devs to check / update their code is the way to go.
Alternative / workaround until this gets fixed by the respective parties is to roll back to WP 5.2.4.
Hope this helps.
Andras