Sub domain configuration with Workers questions

Hi @greggwatson,
You don’t have to do anything. The plugin will take care of everything. Just install the plugin on your subdomain. Provide the CF email and API details. Select your root domain and enable page caching (either by using page rule or worker whatever you like) and it’s done.

Does not work correctly. After installing the plugin and using separate workers on both the sub domain and top level domain, the Workers console shows the script is now throwing thousand of errors, when before there was none. And the pages load improperly at random times,

Hi @greggwatson,
Can you share a screenshot of your Cloudflare Worker page so that I can see all the workers you have?

I am currently using worker on both the main and subdomain with absolutely no issues.

Also, have you overwrite the worker code or using the default worker given by the plugin?

After a great deal of testing, the problem appears to be when one of our developers was building a new site in Oxygen builder on a subdomain, and we had Workers on both the sub and parent domains. The original domain was in written in Elementor.

But the problem lies in running your plugin with Cloudflare Workers and Oxygen builder. Oxygen builder loads a page in sort of virtual sandbox and renders it, and the way they handle memory alloc in the browser does not play well with certain caching. Pages appear to save but dont, or they save corrupted, or get overwritten with random portions of Oxygen code.

The easy and simple solution we are testing is..

add the following line to the Prevent the following URls to be cached area of the cache tab in your plugin settings.

/*ct_builder*

Losing a full day of work is no fun, especially when it all looks good and then suddenly becomes corrupted.

For now it appears to be resolved. We will keep you apprised with further testing.