Browser / Ad blocker compatibility

Hello,

Thank you for your token of appreciation!

Booking Activities is compatible with all browsers, adblockers, antiviruses…, otherwise, its a bug. I have also tried your site with all the browsers and all the devices I have, and it looked fine. You will need to ask your customers more information about their environment until you do reproduce the error.

You can ask them the following:

• Browser and its version (Chrome, Firefox, Edge, Internet explorer, Opera, Safari…)
• Operating system and its version (Android, iOS, Windows, OS X, linux…)
• If they have an error in their browser’s console:

1. Open the browser’s console
2. Refresh the page where the calendar should appear
3. See if an error appears in the console

• If the calendar appears in the source code:

1. Open the browser’s inspector (usually F12)
2. Search for “.fc-view-container” in the html code (CTRL+F). Double check that the search is made in the page source code, not in the page itself.
3. See if the calendar appears in source code

Tell me if you find something.
Regards,
Yoan Cutillas

Hello,

Booking Activities has no relation to facebook. This error is triggered even when the calendar is properly display, then it is not related to our problem.

The error related to the calendar is the following
“Error occurs while trying to reload booking system. You are not allowed to do this.”

Can you reproduce this error each time you visit the page?
It is triggered when the nonce is not verified, or, in backend only, when the user doesn’t have the right to manage this calendar.

First, let’s double check that the problem comes from the nonce. Can you add this code to your (child) theme’s functions.php:
add_filter( 'bookacti_bypass_template_managers_check', function() { return true; } );
And tell me if it works?

Regards,
Yoan Cutillas

Hello Laura,

Actually, that is not what I expected.
If you cannot reproduce the error for sure, there is great chances that this code didn’t solve your problem.

I have removed the unecessary nonce that may have caused this issue in the new 1.5.2 version.

Can you update to 1.5.2 and remove the code I have provided you.
Then, let me know if the error occurs again.

Regards,
Yoan Cutillas