Complianz causing issues with TinyMCE in DIVIs visual builder

Hi @koyani,

I just tried on our set-up without issues, and I don’t really know how Complianz would affect the loading of CSS files. I think there might be another error on the back-end that might cause this.

Would you be able to install WP Debugging, set WP Debug to true. Then try to open the text module. If it doesn’t load correctly, please see if you can copy/paste the debug log, maybe we can find something.

regards Aert

Hi @aahulsebos,
thank you for your reply. I installed WP Debugging, but it didn’t write anything in the log when I got the error messages again.
Maybe we can ignore the problem with the loading of the CSS files for now. It doesn’t seem to cause any issues apart from the annoying error message. I think it might just be an indirect symptom of the text editor in Divi not loading correctly or very slowly whenever Complianz is active. It takes >20 seconds (in contrast to almost instantly without Complianz active).
Also when I switch to the plain text view before the TinyMCE editor could load and then back to the visual view the editor doesn’t load at all. This also only happens whenever Complianz is active.

I further also noticed that some images in sliders don’t show up inside the Divi builder. That also only happens when Complianz is active.

Could Complianz somehow be deactivated automatically whenever the Divi builder is used?

Best regards,
koyani

Hi @koyani,

There are some things we can try, but it’s hard to pinpoint this without reproducing the issue.

The first thing could be the cookie scan, to shut it off completely and check if this helps you can add this line to your wp-config.php

define('CMPLZ_DO_NOT_SCAN', true);

PS: Besides script errors via debugging, could you also check any console errors in your browser?

Let me know,
regards Aert

Hi @aahulsebos
thank you again for your help! Checking the console errors was a great tip (should have done that sooner ?? ).

And good news for you: the culprit is a different plugin (named “Sticky Menu (or Anything) on Scroll”). That causes loads of repeating errors.

There is one error in connection to Complianz as well in the console:

POST https://buergerstiftung-muenchen.de/wp-admin/admin-ajax.php?type=errors&nonce=1b5406357c&action=cmplz_store_console_errors net::ERR_INSUFFICIENT_RESOURCES
window.onerror @ ?et_fb=1&PageSpeed=off:118
error (async)
(anonymous) @ ?et_fb=1&PageSpeed=off:109

What’s up with that? Am I correct to assume that as soon as I fix the error with the other plugin, this one won’t happen anymore?

Many thanks!
Best regards,
koyani

Hi @aahulsebos
so, after fixing the problem with my other plugin, the error mentioned in my comment above doesn’t happen anymore.
Thank you very much again.
Regards
koyani

Hi @koyani,

The error in Complianz is related to the error from the other plugin, Complianz will register the error as it might break consent management. We created a small improvement in handling these errors; https://github.com/Really-Simple-Plugins/complianz-gdpr

regards Aert

Hi @aahulsebos,

thank you for the explanation. Great to hear about the improvement for the error handling. Thank you for the great support and the awesome plugin!

Best regards
koyani

Hi @koyani

Great to hear that your issue is resolved! Could you tell us what you think of the plugin or the support by casting your Review here? We’d love to hear your feedback!