Problems with Oxygen Builder

Hi @greggwatson,
Can you confirm you are using the latest version of the plugin? ALso on that page do a right-click anywhere and go to View Page Source and search for the thing that is showing already declared. That is supposed to be shown once not twice. As you did not share your site URL can’t check it on my own.

Of course i have the latest plugin installed. The problem is inside the Oxygen editor windows, in the editor viewport. I cant send you a url, because you would need to be editing pages. The problem is, when that error message is displayed, the Oxygen builder does not properly save your work correctly. I also saw other users having the same problem and reporting it on Oxygen forums only to be told it is a problem with the way your caching plugin and how it does not truly disable the wordpress backend.

And when I talk about Oxygen not rendering the page correctly, I am referring to how Oxygen renders pages in the builder side, not on the user front end.

it is a problem with the way your caching plugin and how it does not truly disable the wordpress backend.

– DOn’t understand what you mean by that. If you are talking about the cache buster, try enabling the worker mode as worker mode doesn’t use any cache buster and see if that works.

We always use Worker mode. and have the paid Workers bundl. That does not work. But have tested this extensively with both modes. Does not work, errors appear in the Oxygen builder window. If you see that error, you work will not save correctly even though it appears to. Only solution we have found is to disable your plugin during development and re-enable when editing is done. That sucks.

Hi @greggwatson,
Honestly man I don’t know how this problem can happen as it is impossible to happen. The error screenshot you have shared, says the error is coming because it’s a Syntax Error as swcfpc_toolbar_cache_status_tries is already declared. That’s what the error message says.

But if you go to the /wp-content/plugins/wp-cloudflare-super-page-cache/assets/js/backend.js you will see at the top it says:

let swcfpc_toolbar_cache_status_tries = 0;

That’s the only place it’s been declared and then in the rest of the case, it has been used. As it is declared with let and not const, it can be reassigned as many times as a developer wants without throwing any error.

So, the error message you are getting makes no sense.

Sorry if it doesn’t make sense to you, but the errors are there nonetheless. I simply showed you a screen shot of the errors that occur every time you open the Oxygen page builder on the backend to edit a page or template. On different sites, servers etc, the problem is always the same.

Making sense or not, this is what happens when you use Workers.

Your plugin does not have these errors when its setup to NOT use Workers.

If you want I can setup an extra domain with Oxygen builder and your caching plugin, setup to use Workers, and you can work with it and see if you can identify or fix the problem.

You said “Honestly man I don’t know how this problem can happen as it is impossible

to happen.”

Well the error message does happen and when this error occurs it corrupts the Oxygen builder page.

So it can’t be impossible if it happens and I have screenshots to prove it.

Your plugin does not have these errors when its setup to NOT use Workers.

Workers run on Cloudflare, not on the site. If you use worker mode or page rule mode, the codes in your site remain exactly the same. Are you using the default worker code that comes with this plugin?

Of course, default worker code(if it was my code or from their template I would not be writing this. And of course all plugins are always up to date. This problem makes saving in Oxygen less stable. Sometimes it works fine, but sometimes you lose all your work. Like I said before, happy to setup an extra domain with Oxygen and Wp Cloudflare super page cache, and config it for worker mode, this is very easy to duplicate.

I have eliminated all plugins, this issue only happens with Oxygen Builder. I have tested every other builder out there. Its an issue with the way Oxygen renders the output in the browser as a iframe, and therein lies the problem, the iframe rendering. Now there are some fixes for this on other builders and certain plugin in WP CF super cache, ie. if you use the Prevent the following URls to be cached setting;

`/*ao_noptirocket*
/*jetpack=comms*
/*kinsta-monitor*
*ao_speedup_cachebuster*
/*removed_item*
/my-account*
/wc-api/*
/edd-api/*
/wp-json*

but any and all combinations of these with Oxygen dont work either
/?ct_template/*
/?ct_builder=true&ct_inner=true*

etc…

I have been writing code since the 70’s,,, trust me when I say the issue is in this plugin, it works fine without worker mode, but then you have the irritating addon to your admin urls.. and we use the enhanced Worker package, as we get better speed and higher usage limits, so it would be nice to have this fixed. But since this plugin was taken over by Optimole, there has been little to no support and NO updates.. So you have to wonder

The thing I am super curious about is how the worker mode can cause this issue cause when you enable the worker mode, it doesn’t add any extra code to the front end, just the worker code gets added to the CF.

Without having a proper reproduction steps it’s hard to see. Can you create a screen record showing how to reproduce the issue on a blank wpp install, then I will follow the same steps on a test site to reproduce the issue on my end and then I can dig further.

The issue is probably that Oxygen makes AJAX requests that don’t have the ?swcfpc=1 query so the requests fail. Am I right?

– If you are using the worker mode then there is no swcfpc=1 but it seems the problem is in the worker mode.

As I said people please provide a screengrab of how to reproduce the problem so that we can install the plugin on a blank test site and replicate the issue.

Hey guys,
I have run some through test and was unable to reproduce the issue. Check my testing screen recording: https://www.screencast.com/t/UdDk2HlG3

Let me know if I missed something