Website crashes after any content update

Hi,
Recently my site has been crashing after any edit when using the page builder. Here’s the error it displays:

Fatal error: Cannot declare class TCO_Coalescence, because the name is already in use in …/wp-content/themes/pro/cornerstone/includes/vendor/coalescence/class-coalescence.php on line 6
There has been a critical error on your website.

I had a very similar error a few months ago, and I was able to fix it by following the suggestions from this post.

Unfortunately this error doesn’t appear to be fixable using the same strategy, as it’s now coming from a theme file rather than the plugin.

Any help would be greatly appreciated, thanks.

Hello @jamierzwa,

Thanks for writing in! Did this error occurred after you have updated the Pro theme? Please make sure that the Cornerstone plugin is not active. If nothing is helping, provide us access to your site so that we can check your settings. Please create a secure note with the following info:
– Link to your site
– WordPress Admin username / password

To know how to create a secure note, please check this out: https://theme.co/apex/forum/t/how-to-get-support/288

Regards.

Thanks for the reply,

Cornerstone is not active and the theme has not been updated before this error began happening. That being said, updating the theme on a staging site appears to break the editor completely.

Hi @jamierzwa,

Thank you for the credentials, but I don’t see the error on your live and staging site. I’ll tell you what is the common cause of that error though, the common cause of that issue is if you have installed and activate the Cornerstone with PRO. In PRO the Cornerstone (a.k.a Content Builder) is built-in so having Cornerstone plugin on PRO is redundant, please delete the Cornerstone from your PRO site.

Another thing that can cause that error is an outdated version of WPML (more details here), but I don’t see WPML installed on your site, so it’s possible that another plugin is causing that error. Please testing 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.

Last thing, I see that you have multiple caching features on your site (Autoptimize, Speed Up, and WP Super Cache), if you dont mind, please CLEAR and DEACTIVATE these plugins for a while to make sure the site is serving all the latest updated files and not an old cached file that can cause the error.

Let us know how it goes!

Sorry about that, I’ve attached a new private note with a new staging site that has the error. This error happened after deactivating unneeded plugins as well as all caching plugins.

Hi @jamierzwa,

Thank you for the credentials. I am able to see the error.

Please login through FTP then go to wp-content/plugins then rename the cornerstone directory that is in there.

Doing this would automatically disable Cornerstone and you should be able to access the site.

Once you access the site and it is back live, you can go back to the ftp files and delete the cornerstone directory. Go back to the wordpress dashboard and Cornerstone should be reinstalled. In case it is not, you can install it from the X page.

Hi Lely,

As mentioned in my original post, I have tried this fix and it didn’t work. Plus, the previous response from friech suggested that I delete Cornerstone, so the plugin no longer exists on the staging site either way.

Hello @jamierzwa,

I have logged in and went ahead to update your Pro theme to 3.1.2. The error is no longer displaying and your homepage is showing.

Please check your site now.

Thanks for clearing up the error, but updating the theme breaks the editor completely. I get an endless loading loop.

Hello @jamierzwa,

As it turns out, Async JavaScript plugin was causing the issue. I have disabled it temporarily and I can edit a page.

Please check your site now.

Looks like that did it! I appreciate it.

We are happy to assist you with this.

Cheers!

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