Complianz is not disabled in Oxygen Page Builder

Hi @oshika35

I installed Oxygen and Complianz on my testing environment and I can disable Complianz without problems.

It may be a problem caused by the cache. For the pages privately published maybe the assets are not served by the cache, but for the public pages, the assets may be served by the cache, and the old cache still includes the scripts of Complianz.

I suggest you clear all kinds of cache that you have: server cache, caching plugin cache, browser cache, CDN cache if any, and then try again.

• This reply was modified 2 years, 9 months ago by Jose.

Hello @giuse

Thank you for your answer,

Unfortunately I already tried all of that, I’m using litespeed so I totally disabled litespeed and cleared the cache. I also logged into cPanel and disabled LiteSpeed LsCache there too. I don’t use a CDN so nothing to try there too. I cleared my browser’s cache too to see if it could help.

This issue is quite frustrating, the only thing that works is disabling Complianz.

I’ll continue to investigate and report here if I can find the solution, if I’m unable to solve it I’ll mark the thread as resolved.

You are welcome! I totally understand your feeling.

I would also try this:

– Visit the page where you have problems adding a parameter to the URL, e.g. https://your-domain.com/your-page/?ct_builder=true&dfsdfs=fsdfsd. By doing that you may bypass the cache. I know you cleared all the cache, but you would not be the first one in history who believes to have cleared all the cache, but it wasn’t so
– Disable all plugins, not only Complianz, in the Outer Editor, Inner Editor, Loading Editor. This is to be sure that other plugins are not loading the script of Complianz.
– In your backend go to Plugins => Must-Use. Check which mu-plugin you have there. FDP and Editor Cleanup For Oxygen add the following mu-plugins: freesoul deactivate plugins [fdp], and oxygen editor speedup [oes]. The other mu-plugins will not be disabled by FDP and Editor Cleanup For Oxygen. If you find some other mu-plugins, add this line of code immediately after the first comments:

if( isset( $_REQUEST['ct_builder'] ) ) return;

This will ensure that those mu-plugins don’t cause the problem.

– Open the file wp-content/plugins/complianz-gdpr/commplianz-gdpr.php and add the same line of code immediately after the first comments.
That line of code ensures that Complianz doesn’t run in the Oxygen editor. If you still have the issue it means it’s still caused even if the plugin is disabled. In this case, you should focus on the cache or factors that are out of Complianz.
In the code of Compliannz after adding that code you should have something like this:

if( isset( $_REQUEST['ct_builder'] ) ) return;
defined( 'ABSPATH' ) or die( "you do not have access to this page!" );
define( 'cmplz_free', true );

I hope it helps.

• This reply was modified 2 years, 9 months ago by Jose.
• This reply was modified 2 years, 9 months ago by Jose.

Thanks a lot for your detailed answer!

I was finally able to find the culprit! After following your recommandations. I disabled all the plugins and then searched the one causing the issue, it was OXYULTIMATE WOO in the Editor Loading Cleanup.

Well now, I can’t really disable it, because it’s providing e-commerce widgets and disabling it would cause issues in the editor. But at least now I can contact the plugin author and let him know about this conflict.

I’m quite new on wordpress forum so I wonder if I should post a reply in the original thread too?

Perfect! I’m happy that you found the guilty plugin.
Are you sure you can’t disable it in the Editor Loading Cleanup? You would disable it only while the editor loads, if you keep it active in the Inner Editor, it will provide the WooCommerce widgets.

As I know there are no rules that say you have to reply to the original thread. It’s your decision. If you do it you may help other users who read that thread. People who read that thread in the future would know that OXYULTIMATE WOO may give conflicts with Oxygen.

So, I will close this thread.

@oshika35

Thanks!

Unfortunately after testing it a bit more, yes I’m sure I can’t. The widgets are not loaded in the editor. But at this point I’ll contact the plugin’s author

Hi @oshika35

thank you for the update. Now you are nearer the solution. Probably the plugin’s author will find the final solution.