Backend no longer accessible.
Problem on multisite. Fortunately noticed on the test page. Recovery takes a long time. Hope it works.
After so long an update with such consequences is more than annoying. Hope to see a correction soon.
greeting
Dag
Hi @OlKR17,
Thanks for reaching out. We fixed a fatal PHP error that happened if you updated Cornerstone to 5.0.2 and didn’t update X, but I’m not sure that’s the same thing you’re seeing here.
I’m not aware of any multisite specific errors. Without knowing more about the specific error message, regretfully there isn’t much we can do until the problem reoccurs and we can take a closer look.
You enable WP_DEBUG in wp-config.php like this:
define('WP_DEBUG', true);
That will cause any fatal PHP errors to output additional error information.
I got the same error, all my site crash, i try contacting my hosting provider, deactivating all plugins, and the error only dissapear when i deactivate X theme, what can we do?
Seeing the same thing on my site after updating, my host said:
The PHP fatal is singling out the theme now. Those can be tough to troubleshoot since it can’t be deactivated like a plugin.
PHP Fatal error: Cannot declare class X_View_Router, because the name is already in use in /www/logoglo_687/public/wp-content/themes/x/framework/functions/frontend/view-routing.php on line 73
The theme developer may be able to offer a quick fix, otherwise perhaps a backup restore would be the best way to get the site back.
Join the club!! All is fine if you roll back to previous version of Cornerstone.
More bug testing needs to take place before updates are rolled out - this appears to be a conflict with Wordpress as thats what has shut my clients sites down.
1 Like
Hi everyone,
When updating, please make sure you update both X and Cornerstone to the latest version. Older versions of X won’t work with the new version of Cornerstone (and vice versa).
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.