In computing, a fatal error or fatal exception error is an error that causes a program to abort and may therefore return the user to the operating system. When this happens, data that the program was processing may be lost. A fatal error is usually distinguished from a fatal system error (colloquially referred to by the error message it produces as a “blue screen of death”). A fatal error occurs typically in any of the following cases: In some systems, such as Mac OS X and Microsoft Windows, a fatal error causes the operating system to create a log entry or to save an image (core dump) of the process.
If you are testing something new, there is always chance to break things, that's why you should always have a fail-safe system. Thing is sometime situation could be a bit different. I decide to test “WP-Rocket”, so disabled W3 Total Cache. I will write a separate article about my experience with “WP-Rocket”. Soon, when I decide to revert back to W3 Total Cache, I started to get weird errors, here I will explain how I solved it.
I wrote about W3 Total Cache 0.9.2.7 issue, which caused few issues including MaxCDN custom domain name not working. Frederick, the plugin author was fast enough to release updated version 0.9.2.8, but it caused a Fatal error like below, and here I will show a quick workaround to fix the issue.
Fatal error: Uncaught exception 'FileOperationException' with message '<strong>/public_html/wp-content/w3tc-config/master.php</strong> could not be created, please run following command:<br /><ul><li><strong style="color: #f00;">chmod 777 /public_html/wp-content/cache/tmp</strong></li><li><strong style="color: #f00;">chmod 777 /public_html/wp-content/w3tc-config</strong></li>' in /public_html/wp-content/plugins/w3-total-cache/inc/functions/activation.php:127 Stack trace: #0 /public_html/wp-content/plugins/w3-total-cache/lib/W3/ConfigWriter.php(159): w3_throw_on_write_error('/...', Array) #1 /public_html/wp-content/plugins/w3-total-cache/lib/W3/Config.php(71): W3_ConfigWriter->save() #2 /public_html/wp-content/plugins/w3-total-cache/lib/W3/CloudFlare.php(174): W3_Config->save() #3 /public_html/wp-content/plugins/w3-total-cache/lib/W3/Plugin/CloudFlare.php(52): W3_CloudFlare->update_ip_ranges() #4 /h in /public_html/wp-content/plugins/w3-total-cache/inc/functions/activation.php on line 127
This is a very common Error if you have a big site in WordPress. Mostly site with huge post count suffers in this error. It could occur while posting new or editing any existing post. I also had this error while creating large sitemap, doing some batch function. You will see any empty screen with the message below –
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 80 bytes) in /home/*****/public_html/wp-includes/wp-db.php on line 958
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 80 bytes) in /home/*****/public_html/wp-includes/wp-setting.php on line 958
It occurs as WordPress tries to access more memory then its allowed to by “Server PHP configuration” or “WordPress Setting”. Increasing Memory will solve it. Here is solution for all user, who have shared hosting or dedicated or VPS, just FTP access to server will be enough.