Post CLoudflare & Cache "A conflict on the front end of the site has prevented a preview from loading"

[Alexander_Harmsen_Co]

Using X without a problem for years on a number of sites. Started getting symptoms after setting up W3 cache and Cloudflare. When we first got error message we followed all advice on the old forum … deinstal plugins … purge cache …etc. Contacted support when this didn’t work. Support said the problem was the minify seting on W3 … it should be off. Things worked again for 3 days. Then it stopped being possible to delete items, columns, rows …etc. The delete confirmation buttons (grey and red) showed up but it was not possible to click them. Then the “A conflict…” error message came back. Support said everything works fine on their end. Am running windows 10 pro and tried emptying the caches in all browsers + restarting router. No luck … error persists on Edge, Chrome, Opera, and Firefox. Am at my wits end.

PS it IS possible to preview the pages in cornerstone … the error occurs after pressing ‘edit’.

PSS Themco support asked me to post this thread so that other support could see it too.

[Joao]

Hi There,

Please refer to:

https://xthemetips.com/using-cloudflare-rocket-loader-with-x-pro-and-x5/928/

Hope it helps!

[Alexander_Harmsen_Co]

Thanks Joao,

Already done from the start. That is NOT the problem.

Implimented page rules:
domain.com/x/
domain/?cornerstone*

domain being a placeholder of course.

[Joao]

Hey There,

Would you mind providing us with login credentials so we can take a closer look? Please provide following information:

Set it as Secure Note

• Link to your site
• WordPress Admin username / password
• FTP credentials

All the best!

[christopher]

Hi there,

Thank you for providing the login information of your website. I checked and added a new page called Test Page. I did add an element and changed that many times. I clicked on exit to the dashboard and used the page list Edit With Cornerstone option. All of those options are working correctly.

This shows that the problem should be specific to a page you are working on. Would you please kindly try it yourself and check the Test Page created?

If this is happening to your created pages kindly try to clone the page and remove the elements one by one to be able to find the culprit.

Thank you.

[Alexander_Harmsen_Co]

Thank you Christopher,

I don’t know what you did but now everything is back to normal. Did you change any settings? Perhaps it was pausing Cloudflare that worked. There were no issues before cloudflare. Do you have any ideas on how avoid this happening again with cloudflare activated. Or, is it perhaps better to simply avoid Cloudflare when running X with cornerstone?

Anyway … thanks a lot.

Warm regards from Konstanz Germany

[lely]

Hi Alexander,

You’re welcome!
We did not edit any settings. The page rules for Cloudflare should prevent it from working and taking effect when using Cornerstone builder. That means cloudflare should work on your frontend but not when using the builder. Just note that after implementing the page rules, it is best to clear cache before checking again.