Cloudflare disable Rocket Loader question

Hi all,
I have seen your forum post at https://forum.tagdiv.com/topic/can-no-longer-change-custom-title-in-flex-block/ where you discuss the correct setting for Cloudflare. We disabled the Rocket Loader but the tagDiv editor still did not recognise and save layout changes to content. We also cleared cache. The test site is now back under maintenance mode, and editing is restored.

Here’s more info:
We just did a live test and Cloudflare engaged. We have the Pro version of Cloudflare, and have installed the Cloudflare plugin.
When live, we found that Tagdiv no longer fired the “Content Successfully saved” notification after clicking the Save button when editing layout in the Tagdiv editor. We have not had this problem prior to this test, and it saves fine on ending the test, and cutting out Cloudflare
The WordPress editor saved content and it showed on the site.
At one point, a new page seemed to edit and save fine, so there some contrary indicators. This needs further testing. But changes to the layout of the home page did not fire “Content Successfully saved” on clicking the save button at any point, using two different computers, but I didn’t try logging in to a different browser.
We then went to the Cloudflare plugin and clicked on the “Apply Recommended Cloudflare Settings for WordPress” button.
This had no effect, so we then searched the tagdiv forum and saw the advice to disable Rocket Loader. We went to the Cloudflare site and saw that Rocket Loader had been disabled at the time that we clicked the “Apply Recommended Cloudflare Settings for WordPress” button.

We will do another live test on Tuesday, where we will disable the Cloudlfare plugin to make quite sure it is the source of the problem (I’m confident it is), and check the other issues. Also Rocket Loader will be disabled from the start.

So my question is – I guess it is possible that some cache somewhere was holding old info re Rocket Loader.
or – is there any other advice you can offer?
Many thanks for all the marvellous help and informative forums.

Hi, many thanks. we looked at this again this morning, and were unable to resolve it.

The screenshot shows editing in the TagDiv Composer. We cleared the console and hit the Save button, and screenshot the result:
issue with saving content

Hope this helps.

Just to emphasise that while working on this theme, this issue only occurs when we swap to using cloudflare to do the DNS – even when the cloudflare plugin is disabled. All browsers show the same inability to save content under these conditions.

Rocket Loader was disabled before starting the latest test.

• This reply was modified 4 years by PeteMason.

Sorry, clarification, it occurs when Cloudflare is ***proxying*** the http requests.

When cloudflare is just doing the DNS, everything is fine.

The issue seems to be limited to the home page.

With cloudflare proxied for our test site, the console error in my screenshot still shows but only on the home page. But all other pages I’ve edited in TagDiv so far have saved content. I thought I had seen this issue on other pages at least intermittantly, but I can’t reproduce it.

Thanks for your help.

This is now fixed.

I rebuilt the home page from scratch, following from your team’s comments that some code/elements may have caused this error, and it did not re-occur.

I did use the same elements entirely, so there was clearly some corruption present, which was only brought out when the page was proxied in Cloudflare somehow. (Switching off the proxy stopped the issue, but that was not wanted.)

Thanks again.

Cheers
Pete