Update to Cornerstone 5.0.1 breaks website

I was able to restore from backup and am live again but upgrading to Cornerstone 5.0.1 breaks the site, error below:

WordPress version 5.6
Current theme: X – Child Theme (version 1.0.0)
Current plugin: (version )
PHP version 7.3.25

Error Details

An error of type E_ERROR was caused in line 73 of the file /home/customer/www/proteammn.com/public_html/wp-content/themes/x/framework/functions/frontend/view-routing.php. Error message: Cannot declare class X_View_Router, because the name is already in use

Hi,
We are experiencing the same issue and needed to rollback Cornerstone version. We use X theme for this website. Rollback removed fatal error but at some point we will need to update this plugin. Can you give some feedback on this?

Thanks.

Hi,
Theme update to the latest version resolved fatal error with cornerstone. First theme update and then cornerstone update. Maybe this help someone else.

Take care.

1 Like

I did update the theme, then cornerstone, site is not working something to do with. navigation bar

I am getting a fatal error after updating Cornerstone and the site wont load at all. Disabling Cornerstone fixed it for now and I’ll try rolling back.

Hello, just for information I have the same problem on all my sites with the X theme. I updated the theme then Cornerstone, this breaks my sites. By replacing the old Cornerstone plugin folder (in FTP) everything is back in order

Update also breaking my site. Xmlrpc related somehow.

Same here, site broke, the menu is broken as well as cornerstone. In at least one page that I found everything is blank. I am rolling back to the older version. I am assuming they know there is an issue. For me the issue was with the new cornerstone update. I updated only the theme and that appears to be working. Im using theme x.

Same here - fatal error related to X theme & Cornerstone.

Hi @welliott,

Thanks for sharing the info about the error message, and I’m sorry you’re having issues updated. The error means the X_View_Router class is getting declared twice. The class is in both X and Cornerstone, but there’s a gate preventing Cornerstone from declaring it unless X is not the active theme. Somehow Cornerstone doesn’t know X is active. I’m not sure why this is happening, but will do some testing to see if I can reproduce it.

Meanwhile, try this.

  • Delete Cornerstone
  • Update X to the latest version on automatic updates
  • After X is updated, use the link in the dashboard to automatically install Cornerstone. It will be at the latest version

@mariarise, glad to hear you got things worked out. Thanks for letting us know!

@LucyKeile @cranium1 @declic57 @JayRozanski @Bark201 @Gingerfizz_Marketing @Bark201 Please try the steps above, and if that doesn’t work open your own thread so we can investigate each matter individually.

We know there have been some errors during updates but haven’t identified a root cause so it’s more helpful to see the problem in action before a site gets rolled back and we don’t have a way to investigate. We’ve been beta testing for the past few months, but inevitably when the release goes to automatic updates we run into some issues like this. With a complex ecosystem like WordPress, there are so many other variables and we can’t account for them all in testing. The good news is most of these issues are quick and easy to correct once we can identify them.

This solved the problem for me. Now I see a new update available for Cornersone.
Should I update or better not?
Thanks.

Hi guys,

Thanks for all the help on this. The described method solved the problem for me partially - WooCommerce is not working at all. Whenever I click on WooCommerce related pages or product pages, I get the message:

“The page you are looking for is no longer here, or never existed in the first place (bummer). You can try searching for what you are looking for using the form below. If that still doesn’t provide the results you are looking for, you can always start over from the home page.”

Can someone please assist?

Thanks and stay safe,

Oliver

Hi everyone,

We were able to confirm a fatal error that was happening if you updated Cornerstone but left X on the older version. We were able to make a change in Cornerstone 5.0.2 that prevents the error from happening when the older version of X is active but would still advise updating both to the latest version.

@oliverkovecses, I’m not sure what would be going on there but if you wouldn’t mind opening a new topic to discuss this we would be happy to help you there. Thanks!

I updated X before cornerstone and website still broke before rolling back, I noticed you have released updates since, I will try updating again later and see how it goes.

Sounds good @Bark201

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