Diagnose: A conflict on the front end of your site has prevented the preview from loading

Hi Team,

This is the 4 times I get this error in two weeks. As you may know it prevent the article to be edited and since it is not possible to duplicate it, so its bit like the article is lost.

I currently have two pages that shows the problem. I did not installed any plugin recently, I were able to edit the pages and I something make the error appears. I had both the dashboard edit page open and in same time the cornerstone editor open on the same page.

How can I proceed to find / fix the error myself ?

Thank you very much for your kind help.

Hi there @arquier,

Thanks for writing in!

What type of setup do you have, i.e, are you using any caching plugins? How about a content delivery network, such as Cloudflare, Max CDN or similar?

Caching plugins can have an effect on the page builder and so can cloudflare if the correct page rules aren’t added. Do you happen to have any custom Javascript entered perhaps?

You should ideally just have the one page open, i.e, the front-end page, as editing in the wp-admin would result in a loss of the content anyway.

Thanks!

Ok. I understood. A colaborator updated X this afternoon without telling me. uhhhh

We are now running version 5.1.1 since this afternoon and now editing parameters like padding / borders / margin in the new fashioned sections / row / column doesn’t update the page (classic old elements work well).

I would need support please. Can you check our website ?

Should we update to 5.2.0 ? I don’t especially need new features of the new version . However I need something stable, maybe we should downgrade to the Stability 4.6.4 release right ?

Hi

It would seems that actually it was a cornerstone update, not the X update that created the problem.

I copied old cornerstone plugin files from a backup and everything works fine like before.

Is the last version of cornerstone compatible with X 5.1.1 or does it work only with X 5.2.0 ?

For now I stick with old cornestone

did you get the problem fixed? The same thing happened to me.

Update:
I did the following and then went back to Cornerstone and it works.

When you get the error. Exit cornerstone and navigate to the page you want to work on. Then hover over the X and click on “Theme Options”
After that, go back to the page and click “Edit Page.” Cornerstone loads fine.

Something happens by clicking on “Theme Options” that clears up the conflict.

Hope it works for you guys. I just tried it on two pages and doing this works each time.

1 Like

Hey Guys,

Please be advised that Cornerstone 2.0.6 works with X theme 5.1.1. If you already have X 5.2.0, please deactivate Cornerstone 2.0.6 and delete it completely. The newer version bundled in X 5.2.0 will be automatically gets installed when you go to X > Overview.

By the way, several hours ago, we have release a patch which would be X Theme 5.2.1 and Cornerstone 2.1.1. It is already available in automatic updates so please update to this latest version. Please check out the changelog for more information what is included and has been fixed in this release. You can check it out here:
https://theme.co/changelog/

After you have updated to the latest version, if you have installed CloudFlare or any caching plugin, please clear your caches before testing your site.

Please let us know how it goes.

OMFG, I think that fixed it.
Thank you very much.

You’re more than welcome, glad we could help.

Cheers!

I still have this problem after updating to 5.2.0 even now in 5.2.2. I’ve reinstalled Wordpress, reinstalled X 5.2.2 after deleting Cornerstone, same result.

My problem may be linked to Duplicate Post (Version 3.2) or the Save as Template option in Cornerstone cause my site is available in FR and EN.

Need help!

Hi there,

It’s probably related to content and it has a conflicting element, HTML, or characters that triggers Service unavailable or 403 Forbidden. Would you mind creating a new thread about this and provide your login credentials in a secure note?

About the duplicate plugin, you’ll have to contact the plugin author as it may only duplicating the post itself and not the data. And the builder is dependent on that data.

Thanks!