Jennifer
Forum Replies Created
-
UPDATE:
Found it. The issue comes from the “Block scripts” option in CookieAdmin settings. When I disable it, the Live Builder works perfectly again.
So the blank editor is caused by that specific feature, not by the consent banner loading itself.Hi Vardan
Just to clarify: I tested with the Pro version deactivated and the free version only active. The blank editor issue is already there with the free version alone. Adding Pro on top does not change anything.
Also, to be precise about the bug: it is not the consent banner showing up inside the editor — the entire Live Builder page is blank. The editor does not load at all.
Thanks,
JenniferHi Vardan,
Here are the two PHP errors currently logged on the site.
Error 1 — cookieadmin-pro/includes/enduser.php, line 325
PHP Warning: Undefined array key "clarity_consent"The plugin is trying to read a
clarity_consentkey from an array before it is defined. Microsoft Clarity is not installed on this site, so that key never exists. This warning fires on every single frontend request.Error 2 — cookieadmin/includes/admin/scan.php, line 412
PHP Warning: Trying to access array offset on intThe scan function is treating an integer as an array at that line.
Regarding the Avada Live Builder issue: both warnings fire on every request, including AJAX calls. The Live Builder relies entirely on clean AJAX responses, and PHP warnings output before the JSON response can break the builder completely.
JenniferForum: Plugins
In reply to: [Compliance by Hu-manity.co] New update breaks WordPressSame issue here. I tried deleting and reinstalling the plugin from scratch but the fatal error is still there.
The file includes/react-admin-ajax.php is just not included in the package at all. So the class Cookie_Notice_React_Admin_Ajax never loads and WordPress crashes on every page load.
Looks like the current release has a missing file. Please push a fix.
I was successful .. I deleted the code generated by your extension in my .htaccess file then deactivate the extension and reactivate and it works … very disappointed with the little effort provided by support. I give the answer for other users because this problem is mentioned several times on the internet
I am using a hosting: O2switch with several different domain names. They are all independent. Each domain name has its own database and its own ftp folder . they have the same configuration: wordpress + theme avada.
Plugin Works, I can login
https://avis-produits.comPlugin Don’t work, I can’t login
https://webooste.comExactly …
Hello,
Same server, same configuration, same WordPress theme. That’s why I don’t understand.
When I go to the developer console I get a 403 error on the redirect page I created.