The behavior strongly suggests a consent/script conflict rather than an error within the calendar itself.
The key point is this: the calendar works as long as “Marketing / Third Party” is disabled. As soon as you enable this category, it disappears. Normally, you would expect the opposite. That is why I suspect that enabling “Marketing” triggers the loading of an additional ES script or another third-party service that conflicts with the calendar already running.
Services like Google, GTM, Meta, etc., only become active when “Marketing” is enabled, potentially altering the DOM, consent state, or script execution order.
The quickest way to test this in Chrome is as follows:
Open the page with “Marketing” disabled → Calendar is visible.
Press F12 → Clear the console.
Enable “Marketing.”
Check if a red error appears at that exact moment.
Then open the Network tab and filter for:
elfsight, platform, core.service
Please try to follow the Sina’s advice and let us know if it helped. If the issue still persists, please send me a link to the page where the Event Calendar is installed. I’ll be happy to check it for you
thanks for your valuable feedback. I tried what you explained, but to be honest I’m not that much of an IT expert to understand what this means or how to handle the problem.
@Sina, thank you for taking a closer look at this. The error shown in the screenshot is actually related to the AI Chatbot widget installed on the same page. The Event Calendar still has available views, so this issue seems to have a different cause.
@user9767, thank you very much for sharing the link and additional details! I’ve passed this information along to our developers so they can investigate further. I’ll get back to you as soon as I have an update from them.
Our devs check things and the issue occurs because of the conflict with powr io. To fix it, please add the code below right before the widget’s installation code on your website: