How To Fix WordPress Fatal Error Easily without Coding

·

WordPress is so popular that several WordPress Developers and company have created plugins for all purposes. You can literally achieve anything with WordPress and due to this the most irritating error appears on your WordPress site.

Known as the Fatal Error.

So, how to fix WordPress Fatal Error the easy way.

This is what made WordPress so popular, but with this comes the notorious “WordPress Fatal Error”.

how to fix the wordpress fatal error

[adinserter block=”1″]

Fatal Error is an error where the WordPress stops working completely due to an error which was caused in a plugin or theme. This error is mostly due to a conflict between a theme or plugin with WordPress.

In WordPress, WooCommerce is also used by several website owners to run an eCommerce website on WordPress.

WooCommerce also depends on plugins for its extra functionality. This sometimes makes the store owner face weird problems like Fatal Error or Maximum Execution Time Error.

fix fatal error in wordpress

[adinserter block=”1″]

If you are facing Maximum Execution Time Exceeded WordPress Error, then we have a detailed post on How To Fix Fatal Error Maximum Execution Time Exceeded WordPress Error.

Disclosure: I may receive affiliate compensation for some of the links below at no cost to you if you decide to purchase a paid plan. You can read our affiliate disclosure in our privacy policy.

Video on How To Fix WordPress Fatal Error

The method that we are sharing is easy but you need to have paitence. In 90% cases this method solves the Fatal Error WordPress and Fatal Error WooCommerce problem.

The method doesn’t require you to have any technical knowledge or any programming skills.

So, I hope you have some time to go through the tutorial and fixing the Fatal error problem.

So Lets get started ????.

How To Fix Fatal Error WordPress?

So, lets get started first with debugging.

Case 1 – The 90% Cases

If you have recently installed or updated any plugin or theme. Then in most of the cases the problem is with that particular plugin or theme.

So let’s assume that the problem was in a plugin called – “Niraj the Blogger“. I know, there’s no plugin by that name and Name is like a Movie.

Case 2 – The Unknown

But what If you don’t know why you are facing the WordPress Fatal Error. Whether its a Plugin or theme.

Then, what can you do?

Solution – Fixing the fatal error

Whether you know why the fatal error has occurred or you don’t have even 1% Idea why it happened.

Here is what you need to do to find the fatal Error.

  1. Login in to your Hosting Panel / cPanel.
  2. Then go to File Manager in your Hosting Panel.
  3. Navigate to the WordPress Folder.
  4. Find error.log / debug.log file.
  5. You can find this file in Root Folder / WP-Content Folder.
  6. Open the error.log file and check for the latest error with date and time given in the error log.
  7. The error log records the file path where the error was triggered.
  8. Now you can easily find the theme or plugin that caused this error.
  9. The error log will contain the file path – “/home/yourusername/public_html/wp-content/plugins/niraj-the-blogger/plugin-file.php“.
  10. This is the plugin, you just need to deactivate the plugin to get your WordPress back to Normal.

Deactivating the plugin without the admin panel is very easy. Now since you are already logged in to your cPanel and you are currently in your WordPress root directory.

Now you need to navigate to WordPress Root Folder -> WP-Content -> Plugins and rename the particular plugin folder. Like “niraj-the-blogger ” to something like “BACKUP-niraj-the-blogger“.

Now login to your WordPress Admin section and visit the WP_Admin -> Plugins. You will find an error notice that the plugin has been deactivated.

Now, check whether the Fatal Error has been fixed or not. In most cases it has been fixed and you will be able to get access to the wp-admin.

Note: If the particular folder method doesn’t work, then it means the error is in another plugin. To fix it, rename the plugins folder to plugins2. The folder is located in WordPress root -> WP-Contents.

[adinserter block=”1″]

How To Fix Fatal Error WooCommerce?

Fixing WooCommerce Errors are a little different. Although using the WordPress fatal error method you can fix it. But this sometimes don’t work on WooCommerce.

Or what if you just want to fix the WooCommerce error which the rest of your website and blog to work like normal.

Then, this is what you will do to fix the WooCommerce Fatal error.

  1. Login to cPanel -> File Manager.
  2. Navigate to WordPress Root Folder -> WP-contents -> PLugins
  3. Rename the WooCommerce folder to “BACKUP-woocommerce”.
  4. Check the fatal error. It should have been fixed.

By deactivating the WooCommerce, most of the WooCommerce plugins will stop working. Which will also stop the plugin to work which is causing the Fatal error.

But wait, the fatal error has not been fixed.

Now you need to find the culprit, oh I mean the Plugin that is causing the fatal error.

Here is what you need to do to find the plugin.

  1. Login to WP-Admin
  2. Go to WP-Admin -> Plugins -> Installed Plugins.
  3. Deactivate all the plugins that are related with woocommerce.
  4. Now go back to your cPanel and rename the “BACKUP-woocommer” plugin to “woocommerce”.
  5. Activate the woocommerce from your WP-admin.
  6. Now you need to find the Culprit plugin ????️.
  7. To find it, start activating the plugins related to woocommerce. One-by-one.
  8. You will find that while doing it one-by-one. You will encounter the Fatal error.
  9. Now you know the plugin name.
  10. Go to cPanel -> File Manager -> WordPress Root -> WP-Contents -> Plugins and delete the particular plugin folder.
  11. Note: Delete the plugin folder that caused the error, not the Plugins folder.

Try logging in back to your WP-Admin. The error has been fixed.

Avoid that plugin as it is resulting a fatal error. If you have purchased this plugin. Then contact the plugin developer and ask them to check for the error.

They may come up with a solution to make that plugin work without throwing a fatal error.

[adinserter block=”1″]

How To Fix Fatal Error using Database Method? ????️

Fixing using the database method is totally different when it comes to process it but the way WordPress processes it is totally same like the above methods.

Let me explain How?

When we rename any particular plugin folder to a different name, the WordPress database will treat that plugin as deactivated.

Because all active plugins are saved into database in an array. The array contains the filepath of the plugins. Since now the filepath has been changed, wordpress will not find the plugin in that filepath which is saved in the database.

So, the WordPress system will trigger an error popup that only admin can see.

The Database method is also the same, here we will delete the filepath of the plugin. So that will make the plugin deactivated.

Basically it’s the same method. 2 + 3 = 5 or 3 + 2 = 5. So if you are comfortable with the database method, I have given the complete tutorial below.

Note: Database method is a risky way, since you will be interacting with the WordPress Database directly. If you did any thing wrong, your entire WordPress may stop working.

  1. Login to your cPanel.
  2. Search for phpMyAdmin and click on it.
  3. This will open your database.
  4. Now Click on your database name on the left.
    [image]
  5. select “wp_options”.
    [image]
  6. Search for “active_plugins”.
    [image]
  7. Click on edit button. This will open a section, copy everything from “option_value” and save it to a notepad.
  8. Now delete the content inside “option_value” and save it.
  9. By doing this, it will deactivate the plugins and your WordPress will be back to normal.
  10. Incase you have a problem in your Theme, then you need to search for “template” and “stylesheet”.
  11. Now repeat the step 7 and 8. This will deactivate the current theme and switch to the default theme.

So this is how the database method works. You can fix the WordPress fatal error using this method, but you need to be little careful while doing it.

[adinserter block=”1″]

Get Professional Help? ????

If you are overwhelmed with all this methods and don’t know how to to do it. Then you must visit GloriousThemes.com.

GloriousThemes is a WordPress Product company and the best thing I like is that they also provide WordPress Services.

You can easily hire them for any WordPress bugs and Error Fixing for as low as $30. They provide you 100% Satisfaction or Money return Guarantee. They also have 24/7 WordPress Management Service where you focus on your work, while they maintain your websites.

Visit Gloriousthemes.com/services

Conclusion

I hope this article has helped you to fix fatal Error on your WordPress website. If you have any queries, you can comment below or contact us.

Fatal Errors are the most troublesome Errors in WordPress and WooCommerce. This error is sometimes so notorious that it happens on on front-end. Which means the WP-Admin will keep working while the frontend is dead or sometimes vice-versa.

We love the simple technique of folder renaming that allows you to simply debug the error and fix it easily.

You can also subscribe to our YouTube and Like and Follow us on FacebookTwitter and Instagram.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *

6 Comments

  1. Hi, can you help me with this. My website crashed and it says:

    Fatal error: Uncaught Error: Failed opening required ‘/home/www/sollerodtrafikskole.dk//wp-content/plugins/call-now-button/call-now-button-work.php’ (include_path=’.:/php/includes:/usr/share/php’) in /home/www/sollerodtrafikskole.dk/wp-load.php:20 Stack trace: #0 /home/www/sollerodtrafikskole.dk/wp-blog-header.php(13): require_once() #1 /home/www/sollerodtrafikskole.dk/index.php(17): require(‘/home/www/solle…’) #2 {main} thrown in /home/www/sollerodtrafikskole.dk/wp-load.php on line 20

    I disabled all the plugins and disabled theme and nothing changed. 🙁

    Is there anything else that can cause this problem?

    1. Niraj Kashyap says:

      Login to cPanel -> File Manager.
      Navigate to WordPress Root Folder -> WP-contents -> PLugins
      Rename the “call-now-button” to something else, like ‘a-backup-call-now-button’.

      That should fix it.

  2. ARNEODO CEDRIC says:

    Bonjour,

    Dans un premier temps je souhaitais vous remercier pour cet article. Je n’arrive pas à résoudre mon problème malgré votre article. Pouvez-vous m’aider ? Puis-je vous envoyer mon message d’erreur et les informations nécessaires ?

    Je vous remercie d’avance.

    Très belle soirée.

    Cédric

    TRANSLATED….
    Hello,

    First of all, I wanted to thank you for this article. I can’t solve my problem despite your article. Can you help me ? Can I send you my error message and the necessary information?

    I thank you in advance.

    Wonderful evening.

    Cedric

  3. ARNEODO CEDRIC says:

    Voici mon message d’erreur quand je souhaite me connecter sur mon admin :

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 65536 bytes) in /homepages/27/d864402407/htdocs/wp-content/plugins/google-site-kit/includes/Modules/Analytics.php on line 1329

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 65536 bytes) in Unknown on line 0

    Voici le message d’error log :

    2022-01-18T21:05:02+00:00 CRITICAL Allowed memory size of 134217728 bytes exhausted (tried to allocate 10485760 bytes) dans /homepages/27/d864402407/htdocs/wp-content/plugins/elementor/core/files/uploads-manager.php à la ligne 148

    2022-01-18T21:06:37+00:00 CRITICAL Allowed memory size of 134217728 bytes exhausted (tried to allocate 10485760 bytes) dans /homepages/27/d864402407/htdocs/wp-content/plugins/elementor/core/role-manager/role-manager.php à la ligne 194

    2022-01-18T21:30:13+00:00 CRITICAL Allowed memory size of 134217728 bytes exhausted (tried to allocate 10485760 bytes) dans /homepages/27/d864402407/htdocs/wp-content/plugins/elementor/core/files/uploads-manager.php à la ligne 577

    Merci d’avance pour votre aide.

    Cédric

    TRANSLATED
    Here is my error message when I want to connect to my admin:

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 65536 bytes) in /homepages/27/d864402407/htdocs/wp-content/plugins/google-site-kit/includes/Modules/Analytics.php on line 1329

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 65536 bytes) in Unknown on line 0

    Here is the error log message:

    2022-01-18T21:05:02+00:00 CRITICAL Allowed memory size of 134217728 bytes exhausted (tried to allocate 10485760 bytes) in /homepages/27/d864402407/htdocs/wp-content/plugins/elementor/core/files/ uploads-manager.php at line 148

    2022-01-18T21:06:37+00:00 CRITICAL Allowed memory size of 134217728 bytes exhausted (tried to allocate 10485760 bytes) in /homepages/27/d864402407/htdocs/wp-content/plugins/elementor/core/role- manager/role-manager.php at line 194

    2022-01-18T21:30:13+00:00 CRITICAL Allowed memory size of 134217728 bytes exhausted (tried to allocate 10485760 bytes) in /homepages/27/d864402407/htdocs/wp-content/plugins/elementor/core/files/ uploads-manager.php at line 577

    Thank you in advance for your help.

    Cedric

  4. Cornelius says:

    Hi, can you help me with this. My website crashed and getting error ;;; Plz help….

    null to parameter #1 ($string) of type string is deprecated in /home/u6269337033/domains/curastexdmedihealth.com/public_html/hindicurastexmedihealth/wp-includes/formatting.php on line 2772