-
Posts
-
Hi,
There has been a critical error on my website’s homepage ever since the WordPress 6.0 update.
Some important info:
WordPress version 6.0
Active theme: Crio (version 2.15.0)
Current plugin: (version )
PHP version 7.4.25Error Details
=============
An error of type E_ERROR was caused in line 50 of the file /home/username/mywebsite.com/wp-content/themes/crio/inc/boldgrid-theme-framework/includes/kirki/kirki.php. Error message: Uncaught Error: Class ‘Kirki_Controls’ not found in /home/username/mywebsite.com/wp-content/themes/crio/inc/boldgrid-theme-framework/includes/kirki/kirki.php:50
Stack trace:
#0 /home/username/mywebsite.com/wp-content/themes/crio/inc/boldgrid-theme-framework/includes/class-boldgrid-framework.php(227): require_once()
#1 /home/username/mywebsite.com/wp-content/themes/crio/inc/boldgrid-theme-framework/includes/class-boldgrid-framework.php(205): BoldGrid_Framework->load_customizer_files()
#2 /home/username/mywebsite.com/wp-content/themes/crio/inc/boldgrid-theme-framework/includes/class-boldgrid-framework.php(77): BoldGrid_Framework->load_dependencies()
#3 /home/username/mywebsite.com/wp-content/themes/crio/inc/boldgrid-theme-framework/boldgrid-theme-framework.php(54): BoldGrid_Framework->__construct()
#4 /home/username/mywebsite.com/wp-content/themes/crio/functions.php(13): require_once(‘/home/username…’)
#5 /home/username/mywebsite.com/wp-settings.php(566): include(‘/home/username…’)
#6 /home/Hi ApeOneEarth,
Thanks so much for reaching out and thanks for using Crio Pro WordPress theme!
I’m sorry to hear you ran into some problems after updating to WordPress 6.0. We inspected your site and everything looks to be up and running. Crio version 2.1.5.1 was released earlier today but I wasn’t aware of any compatibility issues with WordPress 6.0.
I suggest clearing any cache you have associated with your website (including browser cache and any server side cache), then reactivating your Crio theme.
We tried testing the update in a dev environment with no issues. If you were able to correct this issue we’d really appreciate if could inform us on how you did just we can be prepared if the problem ever arises again.
I hope this helps! Please let us know if there’s anything else that we can answer for you.
Hi Brandon,
I have cleared my own browser cache as well as CDN cache associated with your website. I am not able to clear W3 Total Cache because I cannot access wp-admin as well.
I have tried several googled solutions to no avail:
1. Via FTP rename the folder “plugins” to “plugins.hold”. I cannot access /wp-admin/plugins.php to disable any plugin that is “missing” so I guess I am not able to disable plugins via this method.
2. Via FTP backed up “advanced-cache” and deleted it.
3. Via FTP backed up “.htaccess” and deleted it.End result is when I try to access my homepage or wp-admin pages:
“There has been a critical error on this website. Please check your site admin email inbox for instructions. Learn more about troubleshooting WordPress.”Thank you ApeOnEarth,
I think this is due to an error in W3 Total Cache. I believe the plugin is still trying to serve older outdated code associated with the previous WordPress version. I’ve seen this happen before after a major release. What you want to do is remove and reinstall W3 Total Cache to rebuild your caching structure.
Follow these steps to completely remove W3TC:
– Purge Cache
– Deactivate and Delete Plugin in the dashboard
– Check .htaccess file and remove W3TC configurations (make a backup of the file before deleting)
– W3TC will create many directives in .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”. Ensure that no residual entries are left over in your .htaccess file after deleting the plugin.Delete the following files and folders from your /wp-content directory:
cache folder
w3tc-config folder
object-cache.php (if it exists)
advanced-cache.php (if it exists)
upgrade folder
w3-total-cache folder (if it exists)Delete cached files from your CDN if you are using one
-Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enable the minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.Go to your WordPress dashboard and reinstall W3 Total Cache
I hope this helps!
Hi Brandon,
Unfortunately there’s a major issue for me to follow your instructions. As I mentioned in my earlier posts, I cannot even access WordPress dashboard i.e. wp-admin.
In fact everything (pages/posts/WordPress dashboard) fails to load on the browser now ever since I purged the CDN caches. Every request displays the following error:
“There has been a critical error on this website. Please check your site admin email inbox for instructions. Learn more about troubleshooting WordPress.”I cant even access rollback functionality via Total Upkeep plugin since I cant access the WordPress dashboard.
I am open to methods that do not involve utilising WordPress dashboard and WordPress plugins to solve the problem.
For example, is there any way for me to manually execute a rollback via FTP using Total Upkeep backup files?
Hi Brandon,
Just an update. I got lucky today.
The day started with the same errors as previously reported and I could not access WordPress dashboard.
I did the following steps:
1. Via FTP rename the folder “plugins” to “plugins.hold”
2. Cleared Cloudflare CDN cache and browser cacheI also received a new email from WordPress with a link to access recovery mode and was able to access WordPress dashboard via the embedded link.
It’s worth noting that this was my second such email from them. The link to recovery mode embedded in the first email did not work and also pulled up an error message.
Within recovery mode, the only notification I see that seems of importance was that the WordPress update to 6.0 was not complete. Quite scary actually since this was done automatically and involves core files. It also seems my Crio theme was also not updated to 2.15.1 (was still at 2.15.0) before WordPress 6.0 was initiated automatically.
In recovery mode I switched to the Twenty twenty two theme, exited recovery mode, and executed rollback to before the automated WordPress 6.0 update. That went through successfully with no issues.
So far so good.
Hi ApeOnEarth!
Thanks for the update. I’m happy to hear you were able to regain access to your WordPress site! I suspected a caching issue to be the culprit. I think you should be okay now to update your Crio Pro WordPress theme and BoldGrid Post and Page Builder plugin.
Try updating both while still running TwentyTwenty as your current theme and switch back to Crio once the updates are complete.
Please don’t hesitate to reach back out if you need further assistance with this!
- The topic ‘Critical Error in Crio Theme after WordPress 6.0 update’ is closed to new replies.
