Oxygen Builder backend Error message windows – ‘cmplz_banner’

Hi @1baeri,

I need to install Oxygen Builder and have a look. I’ll let you know as soon as possible, regards Aert

Hi Aert,
Thank you for your time!
I did some more tests/checks, and the message only goes away when I deactivate Complainz’s plugin.
I did compare with another website, who is also in Version 6.3.4, and even if general setting are the same, the other website have no message error in the page builder.
In the assistant, down in the Consent > Cookies description (translate from French), I have compared the lists, and I found that “Cookie ? oxygen-componentbuffer ?” is in the list only in the new website (the one with the error message).
The Cookie ? oxygen-componentbuffer ? has a red cross icon and a red synchronize icon also.
Regards,
Eric

Hello @1baeri,

I have installed version 4.0.4 of the Oxygen Builder, as well as the latest version of Complianz Free (6.3.4) on a testing website; but found myself unable to reproduce the described error message.

Could you confirm that you are using the latest version of Oxygen Builder on this site?

If updating to the latest Oxygen version doesn’t seem to make a difference for you, perhaps you could additionally check for other difference(s) between your site where Oxygen doesn’t display this error, and the site where it does. That would provide you with further pointers as to the likely cause of the problem.

Kind regards,
Jarno

Hello Jarnovos,

Thank you for your concern.

All my plugins are updated (WordPress: Version 6.0.3 – Oxygen: Version 4.0.4 – …), and caches have also been cleaned, a few times since my last post.

I did check most of the differences between these 2 sites, but I couldn’t find any big differences.
Only when I deactivate Complianz the error message goes away, but all is working fine on the frontend.

LiteSpeed Cache maybe? But all parameters are the way I’m used to, and if I deactivate it, I still get the error message.

UpdraphtPlus, WordFence and Yoast SEO, were also installed just before I did see the message, but I never had issues with them before.

All other plugins were already installed long before I had this issue (OxyNinja, Meta Box and Grid Builder).

I will keep doing my searching, but if you have an idea… ??

Best Regards,
Eric

Hi @1baeri,

I don’t have any further clues as to what might cause this yet, unfortunately.

I would start by checking if there is any difference between pages on the ‘affected’ site when editing them with the Oxygen Builder; for instance, does this behavior occur on all of the pages, or just some of them?

Probably the best way to find out what this could be related to, would be to narrow this down by removing variables from the equation, until the issue no longer appears with Complianz enabled. Such as disabling/removing elements on Oxygen page(s) affected by this, checking if the behavior persists when other Oxygen-related plugins are disabled, etc.

When we know how to reproduce the behavior, that would allow us to look further into a solution.

Kind regards,
Jarno

Hi Jarnovos,

I will also keep doing my research…

Meanwhile, to don’t see this error message anymore, do you have a code that I can add with WPCodeBox/Code-Snippets, to deactivate Complianz in the backend?

Best Regards,
Eric

Hi @1baeri,

I hope I understood the request correctly, but providing a code snippet to resolve an issue of which we do not know the cause, and that we cannot reproduce, would be rather challenging.

I will do some further testing with Oxygen to see if I manage to trigger it on our end as well, if you do the same, that will hopefully yield the cause of this behavior: and we can proceed from there.

Kind regards,
Jarno

Hi @1baeri,

Are there any further updates regarding this?

Kind regards,
Jarno

Hi @jarnovos,
I’m still with my error message, and I’m sure it’s between Oxygen Builder and Complianz.
I know they are some plugins who can get rid of this message, that can disable specific plugins (e.g. Freesoul Deactivate Plugins), but I don’t like the idea to add many plugins, and hiding problems ??
Anyway, I will update this post, if I found an issue…
Thanks for your time and your advises.
Best Regards,
Eric

Hi @1baeri,

Thank you for the update regarding this.

As we can’t reproduce the issue at this moment and don’t have further pointers as to what causes it, I’ll mark this as resolved for the time being.

Please feel free to reach out to us, either here or by e-mail on support(at)complianz.io, if there are any further leads as to the cause of the behavior; and we’d be glad to have another look at this.

Kind regards,
Jarno

@1baeri did you find a solution? I’m having the same error and it’s preventing me to edit my Oxygen templates.

Here’s the error message in the console.

I love Complianz but can’t keep it if it doen’t do well together with Oxygen.

• This reply was modified 1 year, 7 months ago by MWM.

Hi @mike235,

Complianz contains a list of known URL parameters from page builders, such as ?ct_builder in case of the Oxygen builder, so that the Cookie Blocker doesn’t load inside of these builders. I have tried excluding the other URL parameters locally as well.

But this doesn’t appear to work in the case of Oxygen specifically, which I’m expecting to be related to what is mentioned in this other thread about excluding plugins from loading in the Oxygen builder.

You could try applying these steps to resolve the issue, which seems to have worked for other Oxygen users. Or perhaps their support team might be able to provide guidance on stopping other plugins from loading in their builder.

Kind regards, Jarno

@jarnovos Thanks a lot, I could resolve the issue following the steps you linked.

Hello, Complianz team! I am experiencing the same issue and posted in the Oxygen Facebook group about it. Before I install an additional plugin to treat the symptom, I’m wondering whether perhaps this comment from another Facebook user might help you identify and iron out the underlying issue?

“This is a known issue with Complianz, as with some other plugins:
They load JavaScript that is not ready for multi-instance use.
In Oxygen, JS may load twice (1 x builder, 1 x preview). This is sure a rare environment, but plugin developers should be aware of that…”

Hello again, Complianz team,

In the Oxygen Facebook group, a user posted the following possible solutions:

I have never used Complianz and don’t know the exact code.
However, here are some possible solutions to prevent this error:
a) use var instead of let
b) embed the code in an anonymous function
(function(){
// the current code
})();

Would this help to solve the problem and get rid of the warning?

Best regards,
Matt.