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

Support
#1

Hello,
When attempting to edit a page in Cornerstone, i get the error “A conflict on the front end of your site has prevented the preview from loading.” We have:
X theme 5.2.2
Cornerstone 2.1.3
PHP 5.6

We have a child theme. I don’t think we have any custom code (there is nothing in “custom” and “additional CSS” in the customizer). We don’t have any caching or security plugins. I deactivated all plugins except Cornerstone, and on Settings>General I changed Wordpress Address and Site Address to https. I am still getting the error. Do you have any other suggestions?
Thank you.

#2

Solved - deleting Cornerstone and allowing it to re-install seems to have done the trick.

#3

Hi @Waypointhealth,

Happy to hear that you have fixed the problem.

Feel free to ask us again.

Thanks.

#4

Hi @nico the “A conflict on the front end of your site has prevented the preview from loading” is back.

In addition to the info from my original post, it might be helpful to know I am using a staging site, which is on a password-protected subdomain of our production site.

Can you help me understand what kind of conflict Cornerstone might have?
Thank you.

#5

It’s working again. i am not sure what is causing or fixing the error.

#6

Glad it’s sorted it out. It must have been just the cache. If it happens again, try the following solutions:

  1. Ensure everything is up to date according to our version compatibility list at https://theme.co/apex/forum/t/troubleshooting-version-compatibility/195. Please follow the best practices when updating your theme and plugins. See https://theme.co/apex/forum/t/setup-updating-your-themes-and-plugins/62 for more details.

  2. Clear all caches including browser cache then deactivate your caching plugins and other optimization plugins.

  3. If you’re using a CDN, please clear the CDN’s cache and disable optimization services.

  4. Test for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.

  5. Remove custom CSS, Javascript and templates.

  6. Contact your host to increase your allocated memory or do it yourself by adding this code in your wp-config.php

define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

Thanks.

#7

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