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

Support
#1

After updating to X 5.2.2 and Cornerstone 2.1.3 I now get this error every time I try to edit using Cornerstone: “A conflict on the front end of your site has prevented the preview from loading.” This happens on every page, new or existing, across any browser.

Searched Google, forums, took the following steps to try and fix the error:

  • Cleared cache
  • Disabled all plugins, one at a time
  • Updated memory allocation in config.sys

No improvements so far. We have planned a website redesign launch for Monday, would love to take care of this to meet deadline. I am still able to edit in the “wireframe view”.

Any help would be greatly appreciated. Site: wayin.com

Thank you!

#2

Another step we tried:

  • Make sure Wordpress/Site address is set to https (was http)

Did not fix the problem. :frowning: Any advice appreciated as we are nearing our deadline. Thank you!

#3

Any updates please? Our launch date is tomorrow and it is very difficult to work in the wireframe mode with no preview. Ran out of things to try.

Only possible thing that comes to mind:

  • We are running Wordpress 4.6.7, is that supported by the new release of X 5.2.2 and Cornerstone 2.1.3?
#5

Hello @Pau_lWayin,

I am extremely sorry for the delayed response. We are working round the clock to help our customers and clear the tickets. I would like to let you know that we handle tickets using FIFO (First In First Out) principle or from oldest to newest. Now the moment you add a new reply it goes back into the queue and that’s the reason for late reply. However please accept my sincere apology for the delayed response.

Can you please share website login details in a secure note as I would like to see your setup?

Thanks.

1 Like
#6

Thank you so much @Prasant. Yes I did read somewhere not to keep replying and so I will know for next time. :slight_smile: We are still having the same issue.

#7

Hi There,

We need your FTP credentials to investigate this issue further or you can enable WP_DEBUG and let us know, so that we can check.

In the meantime, please update all of your outdated plugins, purge your server cache and test this issue again.

Thanks!

#8

Thank you. Went ahead and updated plugins + cleared cache. This now caused an error 500 on all of our admin pages. One of the plugins to update was W3 cache - wonder if that could have caused it? We have our devops team looking into it.

#9

Hi there,

That is possible. You can try turning on the WP_DEBUG option in the wp-config.php file or the server errors logs to see what is causing the issue.

Hope this helps.

#10

Error 500 is now fixed, now back to the original issue with preview not loading.

We have enabled WP_DEBUG but that added all kinds of notifications at the top of each page, and completely messed up Revolution Slider by stretching the image several times its height. Because we are working with our live site, we had to disable it.

Here is a screenshot example:

Our devops team says we cannot share FTP information with anyone due to contractual issues, and it looks like we cannot enable WP_DEBUG. :frowning: Is there any other way you could help us troubleshoot this problem?

Thank you!

#11

Hi There,

I have investigated this issue further. Since you have fair amount of active plugins, could you please try increasing your PHP max execution time to 300 and see if that helps.

Let us know how it goes.
Thanks!

#12

We have increased the PHP max execution time from 120 to 300. The error is still there, and pops up only after about 20 seconds (changing the execution time didn’t seem to allow the preview more time to load).

We do get a javascript error every time, I tested across multiple pages and it is the same error:

Full page:

Close up:

In addition, we hired a WP developer to come and troubleshoot the problem. He took the entire site currently hosted on AWS and moved it to WP Engine. Login info and SFTP info attached as a secure note. Even after stripping the site of every plugin except for X theme and Cornerstone (even custom fonts), the error still occurs. Here are some of his notes:

This is the exact same server that another X-Theme site is working perfectly on.

All plugins have been deactivated except Cornerstone.

Both the X-Theme and Cornerstone have been deleted and reinstalled.
(The X-Theme has not been validated on this test server!)

wp-config:
define( ‘WP_CACHE’, false );
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );

htaccess:
php_value memory_limit 512M

There are no ModSecurity Rules at WP Engine

All file permissions have been reset to defaults

There is no caching or other performance plugin running.

We have occasional https/https issues on the website.

Please help!

#13

Hi there,

Could you try it again? I disabled the custom script from your global custom javascript. It works on my chrome, but it’s not in firefox. It must be a cache and I cleared everything, but which one is true, so please check it to see what you’re getting.

Thanks!

#14

You are right in that the Cornerstone editor now does work in staging, however still not in production.

In staging, I tried re-enabling the global custom javascript and it is still working … so likely not the issue? I tried disabling both global custom JS and CSS on our production site with no results.

#15

Those errors are coming from combined and minified js files. The common source of that is an optimization plugin. I see you’re using W3 Total Cache which should not be used in WP Engine and you’re using its minifcation feature. That could break your site and because Cornerstone gives you a preview of the front-end, it could not work as well. Your front-end most probably because of it as well. It would be best you hire a professional from W3 Total Cache to configure that plugin correctly.

Thanks.

#16

Christian, I just confirmed we are NOT running W3 Total Cache on WP Engine. We are running it on our production AWS server. Are we to understand that it should be deactivated, or at least the js minification, when we want to edit pages in Cornerstone?

#17

Yes, you need to deactivate minification when working with Cornerstone.

Thanks.

#18

Just wanted to post an update. After an entire month of troubleshooting, trying all of the steps described above, hiring a contract WP developer, getting the best of our internal team to get involved, we were not able to get Cornerstone to work. Same error every time.

Our solution came from a different approach. We started on a new host, WP Engine (moved from AWS). Reinstalled all plugins. Moved over content. Cornerstone worked. There are times when the error occasionally pops up, but a refresh takes care of it. We just launched at wayin.com, a month behind schedule.

This entire experience was too long and too costly. Despite being a huge fan of Cornerstone, this is a tough pill to swallow and I will be looking at other options going forward.

Thank you to those in support for helping us look into the issue!

#19

Hi there @Pau_lWayin,

Glad to hear you’ve now launched and that Cornerstone works correctly on the new host. I am though sorry to hear about how far this put you behind and that despite everyone’s best efforts there just seemed to be something that prevented Cornerstone from working/loading correctly.

As always we are here to help if you do need anything and all the best for you and your business.

Thanks!