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

Support
#1

I am hosted on wengine multisite and I cannot edit any pages with cornerstone. I am getting this error: A conflict on the front end of your site has prevented the preview from loading.

#2

Check for a plugin conflict and disable any caching including minifications from cloudflare or caching plugins. See if that works.

#3

Hi there @mycustomsoftware,

Thanks for writing in!

Looks like there’s a few issues here.

  • 500 Internal server error being generated by Jetpack, specifically the get request for the open sans font.
  • Cloudflare is being used, please make sure Cornerstone is excluded from caching and that Cloudflare minfiication is disabled
  • SSL mis-configuration. The site is returning http, not https. Make sure that the site URL and WordPress URL are both https and not http. This is the main cause of the issue, as the preview tries to load the site in http as that’s whats set for the address, but the site is configured to load https causing a mixed active content warning.

Thanks!

#4

I am not seeing any ssl misconfigurations.
I disabled jetpack.
I turned off cloudflare routing so it is not caching anything.
Still getting the builder error.

#5

Any help here?

#6

Hello There,

Thanks for updating in! The issue was caused by CORS. Your dashboard is in https and yet your live site is just using http. Please keep in mind that Cornerstone uses the Site URL setting.

You will need to edit your site settings and make sure that it is using https.

Please let us know how it goes.

#7

I updated this via phpmyadmin so that the site url is https. I am still getting the cornerstone error.

#8

Hi @mycustomsoftware

It looks like you have updated Cornerstone, but NOT X Theme. You are using Cornerstone 2.0.6 and X 5.1.0. This might be part of the issue?? Try updating X Theme to 5.1.1 clearing caches and see how you go. You might want to check the PHP version on your server as well. If you can update to Ver 7 or higher.

Best of luck

#9

Manually updating the parent theme worked. Thanks!

1 Like
#10

@mycustomsoftware Glad you sorted things out.

@Bell_Lodge Thank you for chiming in man.

Cheers!

1 Like
#11

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.