Have you ever faced any kind of WordPress error? Do you know how to fix wordpress errors that cause you to fall dow?
WordPress is one of the best platforms on the ‘net. That doesn’t mean it’s perfect. We’ll walk you through some its most common quirks, and how to fix them.
There’s a reason WordPress is one of the most popular content management systems in the world. Not only is it incredibly easy for a novice to pick up and use, it’s also extremely flexible – and powerful, besides. Using the platform’s built-in plugin API, you can configure it to do just about anything, from E-Commerce to mobile development to user-driven content.
Of course, WordPress isn’t perfect – no platform is. In spite of its power and flexibility, it still has a few irritating quirks you will likely encounter at one point or another. If you don’t know how to deal with them, they can be immensely frustrating – migraine-inducing, even. Don’t be too stressed – if you know what you’re doing, they’re usually pretty easy to fix.
Let’s go over a few of the more common wordpress errors you’re bound to encounter.
Five Most Common WordPress Errors And Their Solution:
Below are the five most common wordPress errors that often happen and face by wordpress users:
Error #1: The Dreaded White Screen Of Death
We’ll start with one of the nastier errors – the WSOD (White Screen Of Death). This one is probably the most difficult to fix, simply because you aren’t presented with an error message of any kind – your blog simply refuses to load. More often than not, this extends to the admin control panel as well as the blog itself – meaning you might not even be able to access your log files (though if you can, this should always be your first step).
Step One: Clear Your Cache
If the WSOD is isolated to specific areas of your site, then the problem is likely tied to your cache – meaning that if you clear it, the issue should resolve itself.
Step Two: Check Your Plugins
There are a number of issues which could potentially bring about a WSOD, though it’s most commonly tied to a misbehaving or misconfigured plugin or theme. For that reason, the most common fix involves locating and renaming your plugins folder through FTP. If your website works once you do so, then congratulations – you’ve figured out the cause of your problem.
Now you get to test each individual plugin to determine which one was misbehaving.
Step Three: Get Rid Of Your Theme
If the FTP fix doesn’t work, then the problem could be tied to your theme. Again, use FTP to delete or rename the Theme’s folder, and see if your website loads. If you’re still having problems, you’re going to have to move to the next step.
Step Four: Contact Your Host
If none of the above fixes works, then it’s time to contact your web host’s support department and see if you can find out what the problem is. Chances are, it’s not tied directly to your blog – it’s tied to your server.
Error #2: Permanently Unavailable For Scheduled Maintenance
Usually, this is an error, which manifests if you lose connectivity while performing an update on your blog or one of your plugins. Should this occur, any attempts to access your blog – whether through the frontend or the backend – will present you with the message that your site is “Briefly unavailable for scheduled maintenance. Check back in a minute.”
Step One: Make Sure Your Site Is Updated
Thankfully, the fix for this issue is incredibly simple – at least, more so than the fix for the White Screen of Death. The first thing you’ll want to do is manually update your WordPress site through the root folder. Simply download the latest files from WordPress.org, and use an FTP client to upload them.
Step Two: Delete your .maintenance File
Once that’s done, delete your .maintenance file – your site should be working as intended once again.
Recommend to read: Five Quick Tips to Improve WordPress Security
Error #3: 500 Internal Server Error
500 Internal Server Error is a general message returned when there’s something wrong, but the problem cannot be accurately identified. Thankfully, the only thing that stops this one from being another White Screen of Death is the fact that – most of the time – your error logs should give you a decent idea of what is gone wrong. There can be a multitude of issues behind an internal server error, and only through consistent testing one can determine the solution.
Step One: Check Your Error Log
The first thing you should do here is have a look at your installation’s log file – this’ll give you a pretty good idea of what went wrong, and help you out where troubleshooting is concerned. To do this, simply login to cPanel and look at the error log section for the busted domain. You can also view the file server side at /usr/local/apache/logs/error_log.
Step Two: Delete Your .htaccess File
Now, although there can be a number of different culprits, this one’s most commonly the result of a corrupt .htaccess file – which generally means that the first thing you should do is either delete or rename the file through FTP. If that doesn’t get your blog working again, things are going to get a little more complicated…
Step Three: Start Testing Your Plugins And Themes
Unfortunately, if your previous two steps fail to fix your problem, the next thing you’ll have to do is test each individual plugin (along with your theme) to see if it might somehow be tied to your woes. The process is basically identical to what we laid out in the section on the WSOD.
Step Four: Re-Upload The WordPress Core Files
If nothing seems to work, I’ve some bad news for you – your WordPress installation is probably corrupt. Don’t worry – the fix is a lot easier than you’d expect. Simply grab the necessary files from WordPress.org, and re-upload both the wp-admin and wp-includes directories.
Error #4: Cannot Modify Header Information: Headers Already Sent
Usually, this issue’s tied to a misconfiguration in the wp-config.php file(or another, similar file). As such, if you encounter this glitch, simply download and open up whatever file is mentioned in the error, and check the code for any unnecessary spaces or line breaks.
Once you’ve fixed the problem, re-upload the file, and you should be done.
Error #5: A Site That’s Slower Than Molasses
Last, but certainly not least, we’ve got what may well be the most frustrating problem of all – a WordPress site that chugs and trudges along, yet still functions (if you’re willing to wait until you die of old age to access it). At least with a site that doesn’t work, your users know right away that they can’t do anything with it.
This kind of wordpress errors could be caused by a whole host of different problems – but usually, it’s the result of a poorly-configured plugin, improperly-uploaded images, or an issue with your web host.
Step One: Host Your Images Internally
This one is basically what it sounds like – host your images through your own site. There’s a good chance that hosting them externally could be causing slow performance, as other sites might not be as fast as yours.
Step Two: Install A Performance Monitoring Plugin
Thankfully, testing out your plugins in this case isn’t as painstaking as it is with your other issues – simply install a performance monitor like P3, and it should point you to whatever’s causing your site to chug in no time at all (that is, assuming the problem is plugin-related).
Step Three: Install Performance-Enhancing Tools
Step Four: Contact Your Host
Last, but certainly not least…how’s your bandwidth? Check with your host to see that you haven’t gone over your limits – and to make sure that, if you’re on a shared hosting account, your fellow clients aren’t dragging your site down.
Every Platform Has Its Quirks
Don’t let the fact that WordPress has a few quirks turn you off of using the platform – it’s still one of the best content management and blogging tools on the web. There are problems with every tool and platform out there, after all. Through this trick, anyone can easily fix the wordpress errors when they arise.
What kinda errors you’ve faced? Plus, how helpful this post is for you to fix wordpress errors instantly?
Latest posts by Rachel Gillevet (see all)
- Fixing The Five Most Common WordPress Errors You’ll Encounter - December 15, 2014