3.8.1 Plugin broken since latest update

Hey @chartist1848 thanks for the kind words and sorry that this is causing an issue! Our team will look at it shortly. Can you please send us a screenshot of the error and also let us know the URL of your site and any additional plugins that you’re using that might cause conflicts? Feel free to shoot an email to [email protected] for additional details too.

I can concur that the plugin broke on our site as well.

• This reply was modified 1 year, 4 months ago by protoolreviews. Reason: typo

Same – upgraded to 3.8.1 & the calendar is broken.

Thanks for letting us know @tbat and @protoolreviews. We will roll back this change by tonight and troubleshoot more before pushing the security fix.

Just wanted to chime in an say that the plugin is malfunctioning for me as well, and I’m getting the same message (“An error occurred while loading the calendar: undefined”).

Thank you for staying on top of this, @marketingfire. This is such a great plugin — I’ve been using it for years.

Hi all! I can’t replicate the issue on my end. I had the new version freshly installed on my website, though.

We’ve made some important updates to the JS files. However, due to caching, these changes may not take effect immediately. To ensure everything works smoothly, we recommend following these steps:

1. Deactivate and delete the Editorial Calendar plugin.
2. Clear both your website and hosting cache thoroughly.
3. Finally, reinstall the latest version of the plugin.

This process will ensure that the updated JS files are properly implemented.

Thanks, and please let me know how it goes.

Tried your three steps – but still the same error: An error occurred while loading the calendar: undefined

Could you give me a list of your active plugins?

We just released 3.8.2 that should fix the undefined issues.

That fixed it for us. Thank you so much for your quick help!

Thank you, @mej!

Thanks for responding and apologies for not replying to your previous message earlier. Can confirm the most recent update has fixed the issue. Thanks!