Fix Critical Error

  • Resolved meganstockman

    (@meganstockman)


    1 month ago

    I have experienced a critical error several times across several attempts to fix. Hosting site support said it was from plugins. We have pulled down all plugins on 3 different support sessions. Each time, the critical error goes away when there are no plugins activated. The first plugin affected was woo commerce. They said it wasn’t them, and pointed me back to host support. The second time, we reactivated all plugins and it was still woo, so Woo commerce was deactivated and deleted. The Critical errors continue with a random popup that wants me to log back in within a few minutes of logging in to start work. Hosting support contacted again. This time no plugins were affected. Error could not be re-created through the hosting site support. They pulled down all the plugins, and Popup stopped while plugins were down but came back within a few minutes of activating plug ins. Rank Math then gave a critical error, that was fixed in the database. Popup and critical error messages continue no matter if rank math is active or not. This pop up appears on several different pages, both during editing and starting from a blank page. My Login credentials are not recognized and correct captcha answer is marked as incorrect. Last night, the pop up continued and website failed to publish updates on 3 separate attempts. Small error notice in the editor “Looks like something went wrong, please try again later.”

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Moderator James Huff

    (@macmanx)

    Reactivating all plugins isn’t a useful way to determine which plugin is causing the problem, it only determines that any of them could be the problem.

    Try manually resetting your plugins again (no Dashboard access required).

    If that resolves the issue, login and reactivate each one individually until you find the one pluigin causing the problem.

    Thread Starter meganstockman

    (@meganstockman)

    We have deactivated them all and pulled them back up 1 by 1 on 3 different sessions to see which plugin is causing the error. On this last attempt, the error continued to pop up while all plugins were deactivated. Support was able to establish it was no longer a plugin causing the error because they were all deactivated and the error persisted. We could not recreate the error for a specific plugin, and the error remained while all plugins were inactive. I logged out and logged back in and the error persists, and now it gives me no option but to leave my session and start over. I can navigate the dashboard for a few minutes once I login, but the error pops up again after a few minutes. If I make to a page and try to change something, it will not publish the changes. There is now a new error that states “looks like something went wrong, try again later.”

    Tolga

    (@cybepe)

    When troubleshooting WordPress, you have plenty of options. Here’s what I would do:

    For self-hosted WordPress (usually located through cPanel > File Manager > public_html > you’ll see a file called error_log (that’s the first place to check for issues when its persistent).

    If you’ve made changes (plugin or theme updates AND have a backup) revert back till you identify issues.

    WordPress also has built in DEBUG feature which can be helpful, its located in wp-config.php (first download a backup, then, right click edit)

    You will see this code:

    define(‘WP_DEBUG’, false); //simply change it to define(‘WP_DEBUG’, TRUE);

    You can learn more about other methods that may suit your needs here:

    https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/

    Thread Starter meganstockman

    (@meganstockman)

    I followed the instructions for step 1 to debug, and my website crashed from the backend and is no longer visible to the public on the front. The crash was instant as soon as I saved the changes on the debug line. My username and password are no longer recognized, and my host support cannot see my login credentials.

    Moderator James Huff

    (@macmanx)

    Hm, that shouldn’t have happened.

    Does it come back if you change define(‘WP_DEBUG’, TRUE); back to define(‘WP_DEBUG’, false); ?

    Tolga

    (@cybepe)

    Seems like a serious issue if debug isn’t working (never seen that before). The only way to troubleshoot this then is to get a hold of the error log through which you will see exactly which errors occurred. Look for a file on your server OR tell your web hosting company to send you the error log (share it with us here). This file will show you what caused an error (plugin, theme, or something else). Without this information I’m afraid it will be almost impossible to inform you of a solution.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.