The reason for the error should be visible in the error log. You can find it in your hosting area. If necessary, the support of your hosting can help you.
Alternatively, you could also enable debugging in WordPress. How to do this is described here: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ – also here the support of your hosting can help you if necessary to edit the file accordingly.
In both cases you should be able to see what the cause is in the logfile.
Hello @understandingielts
Since only the Spanish website shows the critical error, a plugin or theme on that install is the likely cause of it. To find it, turn on error logging. In Bluehost’s File Manager (or via SFTP), open the Spanish site’s own wp-config.phpusually in public_html/spanish/ add these lines:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', true);
More details here: https://learn.wordpress.org/tutorial/debugging-in-wordpress/
Reload the login page, then open wp-content/debug.log in that same folder. The last fatal error line will point to the plugin or theme responsible. Rename its folder inside wp-content/plugins or wp-content/themes to deactivate it, and you should be able to log in again. Since you use Elementor, check whether Elementor or Elementor Pro (or an add-on) is the one named.
If it still doesn’t work, Bluehost support can check the server error logs and help you with this critical error.
Hi @understandingielts, since your English site works fine and only the Spanish one shows the critical error, the problem is almost certainly inside the Spanish install itself, so I would compare the two installs rather than treating the whole account as broken.
A few things I would check, in this order:
- Look for the fatal error email first. WordPress sends it to the admin email address set in the Spanish site’s Settings > General, which can be a different inbox from the English site. Check that inbox and the spam folder. The email names the plugin or theme and the exact line that caused the fatal error, and that tells you where to look first.
- Check the PHP version of the Spanish directory. In Bluehost’s MultiPHP Manager, a subdirectory can run a different PHP version from the main site. If the Spanish install is on a newer or older PHP version than the English one, a plugin or theme that only the Spanish site uses can fail on it. Set the /spanish/ directory to the same PHP version as the main site and try logging in again.
- Compare the plugins. The Spanish site probably has at least one plugin the English site does not, for example a translation or multilingual plugin. Rename that plugin’s folder first in public_html/spanish/wp-content/plugins, then try wp-admin again. If it loads, you have found it.
- If you still need the error itself, open the error log in your Bluehost panel and look for entries with /spanish/ in the path around the time you tried to log in. That gives you the same fatal error text as the email.
Let us know what the email says or which PHP versions the two installs are on. That will narrow it down quickly.
I can access the links you mentioned without any problems. They have different content and look perfectly fine to me. Please check them again on your end, and if they still don’t work, try clearing your browser cache first.
I tested the links and all of them are loading fine and check here: https://snipboard.io/IzkHwh.jpg
I think you might see a broken layout due to Elementor prodeactivated but you may upgraded and activated it now.
If you still continue facing the issue, purge cache from BlueHost or test in different browser/device.
Thank you all so much. In the end, while Blue Host was helping with the Spanish version, they may have accidentally deleted something in the English version. Thankfully they were able to load a backup and now everything is working again.
That critical error means something on the Spanish install is crashing, most likely a plugin. Since it’s a separate install, it can break even if the English one works fine.
First, check the admin email for that site. WordPress sends an email with the exact error and a recovery mode link that lets you log in.
If you don’t have it, use the Bluehost file manager or FTP and rename the plugins folder inside wp-content to something like plugins-off. That disables all plugins and normally lets you log in again. Then rename it back and reactivate one by one until the error returns. The last one is the culprit. I’d check Elementor first if it happens around editing.
There’s also an error_log file in the site’s folder that tells you exactly which plugin and line is failing.