• After installing a theme, this error showed up:
    There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.

    I have cleared cache and cookies and still the same.

    The error appeared last Friday.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Moderator bcworkz

    (@bcworkz)

    Doesn’t the email tell you what the actual error was? What was actual the error then? If it’s not in the email or you didn’t get the email, check your server;s error log for the actual error message.

    Once the error is known, the next step is to deactivate the theme or plugin responsible. This can be done without accessing the WP admin area by using FTP to rename the directory of the module responsible for the error. You should then be able to log into your site again. You may then restore the proper directory name, but do not re-activate the related module. Seek assistance through the dedicated support channel of the problem module to help you resolve the error.

    Sometimes the error message is too vague to identify a specific module. To regain basic functionality, via FTP, rename your current theme’s directory and also rename the /plugins/ directory to deactivate all plugins. After logging in, restore the proper directory names. Then install and activate the Health Check & Troubleshooting plugin. Activate the plugin’s Troubleshooting mode. Use its troubleshooting admin bar item to selectively activate the various modules in order to identify the source of the error.

    Also don’t forget of enabling the debugging in WordPress, that feature’s gonna provide you with useful and helpful information about any issues.

    You can enable the debugging via FTP. Any error/warning messages you’ve got, post them in this thread for could help you out better.

    Moderator bcworkz

    (@bcworkz)

    Enabling debugging is a good tip. Adding to that thought: for production sites, you shouldn’t leave debugging turned on for extended periods of time. Being able to see error messages not only helps you get to the root of the problem, it also can help hackers better exploit any vulnerability they might be trying to exploit.

    https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/

    Yes, but he can just disable the displaying of warnings/errors on screen and let only the debugging via logs enabled. That way they could check the logs out via FTP.

    Thread Starter jhoennaceson

    (@jhoennaceson)

    we didn’t receive any email about the error

    website is created in GoDaddy and we can only see phpmyadmin

    the error still persist, pls help

    Thread Starter jhoennaceson

    (@jhoennaceson)

    I have read this:

    Use phpMyAdmin to deactivate all plugins.

    1. In the table wp_options, under the option_name column (field) find the active_plugins row
    2. Change the option_value field to: a:0:{}

    but there’s no active plugins appearing on the list

    Moderator threadi

    (@threadi)

    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://wordpress.org/support/article/debugging-in-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.

Viewing 7 replies - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.