Anonymous User 20287723
(@anonymized-20287723)
Hi Sinead,
If you do not have access to your WordPress admin backend, you have quite a few options, here are a few:
1. Switch to a default theme like twentytwentythree by changing the database wp-options table “current_theme” row… or ask your hosting provider for help doing that. More here: https://www.bluehost.com/help/article/changing-wordpress-themes-from-the-database
2. Switch back to a default theme by renaming your Jarida theme to something like “~jarida” in your wp-content/themes/ folder, using FTP/SSH. This assumes you have a default WP theme like twentytwentythree sitting in your themes/ folder for WP to fall back on. Most people do. https://www.wp-tweaks.com/manually-switch-a-wordpress-theme-via-ftp/#step-2-manually-switch-the-wordpress-theme
3. Revert to a backed up version of your site (from before you updated WordPress and things broke) using your hosting cPanel or FTP/SSH, or ask your hosting provider for help doing that.
Some hosting providers are really understanding, saavy, and helpful about these things. If they don’t want to help you, I highly recommend hiring the help of a WP developer.
Can anyone assist re solving this problem
Sagehen’s advice may help you to restore your site now (if it’s broken).
But it doesn’t address the root cause of your problem: your Jarida theme is generating the error — it seems to be incompatible with the latest version of WordPress. You need to address that root problem, unless you want to remain stuck with the old (and potentially vulnerable) version of WordPress forever.
If you haven’t updated your theme in a while, it’s quite likely the developer has already released a new version that addresses this issue. Jarida is a commercial theme, so you’ll need to get in touch with the vendor you purchased the theme from to receive such an update.
Good luck!
Thread Starter
sdaly
(@sdaly)
Thanks very much for your assistance. Much appreciated.
