{"id":112660,"date":"2013-04-10T11:30:33","date_gmt":"2013-04-10T15:30:33","guid":{"rendered":"http:\/\/wpmu.org\/?p=112660"},"modified":"2013-04-10T18:05:48","modified_gmt":"2013-04-10T22:05:48","slug":"common-wordpress-problems-and-their-solutions","status":"publish","type":"post","link":"https:\/\/wpmudev.com\/blog\/common-wordpress-problems-and-their-solutions\/","title":{"rendered":"Most Common WordPress Problems and Their Solutions"},"content":{"rendered":"

WordPress is stable software and operates without issues most of the time. However, at times, things may go a little haywire, and your WP website can refuse to function normally.<\/p>\n

Have you ever encountered a white screen after adding some new themes or plugins? Maybe you were just updating your WordPress website and that update now refuses to finish, and your website is in eternal maintenance mode? What about internal server and database connection errors?<\/p>\n

If you have encountered any of the above problems and are looking for the solution to them, you have come to the right place. In this article, we shall be taking a look at some of the most common WordPress problems and ways in which we can solve them.\u00a0<\/strong><\/p>\n

\n
\n
\n
\"Post<\/div>\n<\/div>\n<\/div>\n<\/div>\n

500 Internal Server Error<\/h2>\n

What<\/h3>\n

Your site was working fine, and then, when you wake up the next day, this is what you find:<\/p>\n

\"Post
500 Internal Server Error<\/figcaption><\/figure>\n

Why<\/h3>\n

The most common cause of a 500 Internal Server Error message is a corrupt .htaccess file. Additional causes can be a conflicting plugin or theme, or even a corrupt WordPress installation.<\/p>\n

Sometimes, PHP memory limits may also cause a 500 Internal Server Error. The easiest way to figure out where the problem lies is to check your website’s error_log (many shared web hosts often do not enable full error logging, though). To find out more, you can enable WP_DEBUG and check for error logs. Open up your wp-config.php file, and locate the following line of code:<\/p>\n

define('WP_DEBUG', false);<\/code><\/p>\n

And change it to:<\/p>\n

define('WP_DEBUG', true);<\/code><\/p>\n

The Solution<\/h3>\n

Since the most likely cause behind the error is a corrupt .htaccess file, let us tackle this one first.<\/p>\n

You will need FTP access on your server. Navigate to the root directory of your WordPress installation, and locate the .htaccess<\/code> file. Rename the file to, let us say, something like .htaccess_old<\/code><\/p>\n

\n
\n
\"Post<\/div>\n<\/div>\n<\/div>\n

Now reload your website. If it works, congratulations! You can now generate a new .htaccess file simply by navigating to Settings>Permalinks<\/strong> in your WP admin panel and re-saving the settings.<\/p>\n

You can also try deactivating your plugins and themes because sometimes a 500 Internal Server Error can be caused by a faulty plugin or theme as well. Alternatively, you can try increasing your PHP Memory Limit to ensure that the memory limit is not the cause of the error. You can find detailed instructions regarding memory limits on the WordPress Codex<\/a>.<\/p>\n

If all else fails, you will need to grab a fresh copy of WordPress from the official site, and then re-upload the wp-admin<\/code> and wp-includes<\/code> directories.<\/p>\n

White Screen of Death<\/h2>\n

What<\/h3>\n

As the name suggests, a White Screen of Death means when you access your website, you see nothing but a blank page.<\/p>\n

\n
\n
\"The
The White Screen Of Death – Nothing to see here, folks!<\/figcaption><\/figure>\n<\/div>\n<\/div>\n

Why<\/h3>\n

There can be multiple reasons behind a WSOD, the most common ones being compatibility issues with a plugin or a theme. Of course, the \u201cincompatibility\u201d itself can have multiple faces: a plugin may have a conflict with another plugin, or a plugin may not be compatible with the latest version of WP. Similarly, a theme may also experience compatibility issues with WordPress after an update.<\/p>\n

The Solution<\/h3>\n
\"Post
Plugins and Themes Folders in WP Install Directory<\/figcaption><\/figure>\n

The easiest solution is to first isolate your plugins\u2019 directory. To do so, navigate to the root of your WP installation via FTP (assuming you cannot, at all, access your website and all you get is a WSOD), and then head to \/wp-content. Locate the folder named \u201cplugins\u201d and rename it (let us say, \u201cplugins_old\u201d). Create a new folder named “plugins”.<\/p>\n

This will isolate all your plugins, and if your website works fine, then yes, one of your plugins is at fault. Do not open your plugins page at this point, else you may end up deactivating all your plugins.<\/p>\n

Once you have verified that one of the plugins is behind the WSOD, you can copy individual plugin files from “plugins_old” to plugins”, one by one, to check which one is causing the WSOD.<\/p>\n

For themes, the procedure is even simpler. Navigate to \/wp-content\/themes, and then rename the folder of the active theme. Next, open up your WP admin panel, and head to the Themes page. This will cause WP to fall-back to the default theme (Twenty “something”, depending on your WP installation version). You can find a detailed step-by-step analysis here<\/a>.<\/p>\n

If you have a tool like WP Reset<\/a> installed, the solution is even more straightforward. Just load the Emergency Recovery Script (a part of the plugin that works autonomously), and turn off the plugins & themes until you find the one that caused obstacles. Once you get to log back into your site, you will have a restore point (snapshot) ready. So, all you need is a few seconds to restore it and it will undo changes to your website caused by the bad update.<\/p>\n

Maintenance Mode Error<\/h2>\n

What<\/h3>\n

This error:<\/p>\n

\n
\"Post<\/div>\n<\/div>\n

Why<\/h3>\n

Each time you update WordPress to a newer version, it makes a temporary .maintenance file. The problem occurs when the .maintenance file is not removed properly after the upgrade (in many cases, this happens when the upgrade process itself fails to complete successfully).<\/p>\n

The Solution<\/h3>\n

You will need to login to your WP root directory via FTP. Once you’ve logged in, locate the .maintenance<\/code> file and delete it. This will resolve the error.<\/p>\n

If, however, you are experiencing difficulties with the automatic update, the solutions are different, and James Dunn has a guide to help you out<\/a>.<\/p>\n

Error Establishing A Database Connection<\/h2>\n

What<\/h3>\n
\n
\"Post<\/div>\n<\/div>\n

If you get the above error when you try to access your website, it means WordPress is experiencing a problem when trying to access the database.<\/p>\n

Why<\/h3>\n

The direct cause can be an issue with the wp-config.php<\/code> file — most likely, details related to your database have been entered incorrectly.<\/p>\n

However, most of the time, database connection errors occur due to a problem that can be solved only by your web host (especially if you are on a shared hosting server). Most shared web hosting providers keep limits on databases, and if your database crosses the allotted quota, you can receive a connection error. Plus, database connection errors also occur if your web server is down.<\/p>\n

Lastly, sometimes a hacked website can also result in database connection issues.<\/p>\n

The Solution<\/h3>\n

First up, the wp-config.php file. Locate the file using FTP, and open it. You can then go through it to ensure that database details are correct (database name, username, password, and database host).<\/p>\n

If you think your website has been hacked or compromised, you will have to work towards cleaning it up. You can use Sucuri SiteCheck<\/a> to ensure that your website is clean — more details about securing a WP website can be found in this article<\/a>. WordPress Codex also has an FAQ<\/a> to help you out.<\/p>\n

Lastly, if your web server is down or if your database has reached the allotted quota, you will obviously need to get in touch with your web hosting provider.<\/p>\n

Connection Timed Out<\/h2>\n

What<\/h3>\n

An error that you receive from an overloaded server (or a badly configured server).<\/p>\n

Why<\/h3>\n

It generally happens when the website\u2019s server is too overloaded and is unable to complete your browser\u2019s request. Nothing puts it more eloquently than the WordPress Codex<\/a>:<\/p>\n

\n

The Connection Timed Out error appears when your website is trying to do more than your server can manage.<\/p>\n<\/blockquote>\n

The Solution<\/h3>\n

The first step is to deactivate your plugins. If this cures the problem, try re-activating them one by one to see which plugin is causing the issue. Alternatively, if it is a problem related to your current theme, activate the default WP theme.<\/p>\n

You can also increase your PHP memory limit using the wp-config.php file. Open the file, and add the following line of code to it:<\/p>\n

define('WP_MEMORY_LIMIT', '64M');<\/code><\/p>\n

This will increase the memory limit to 64 MB. You should note, however, that if you are on a shared web host, you may not be allowed to increase your memory limit beyond a certain point. In this case, you will need to contact your web host to increase the memory limit for you. Also, bear in mind that many shared hosting providers keep the PHP memory limit as low as 8 MB.<\/p>\n

Lastly, if you have access to your php.ini file, you can also consider increasing the maximum execution time<\/a>.<\/p>\n

Error 145<\/h2>\n

What<\/h3>\n

You get a message like “MySQL error code 145.”<\/p>\n

Why<\/h3>\n

Error 145 means that your WordPress database is damaged or corrupted.<\/p>\n

The Solution<\/h3>\n

The easiest way to repair your WP database is using phpMyAdmin.<\/p>\n

Once you login to phpMyAdmin, choose your WP database. You will then need to select the checkboxes next to the tables that you wish to repair. Once selected, you can choose the \u201cRepair Table\u201d option from the drop-down menu right below the list of tables.<\/p>\n

\"Post
Repairing Tables Using phpMyAdmin<\/figcaption><\/figure>\n

Note:<\/strong> Always create a backup of your database before making changes to it.<\/p>\n

Error 28<\/h2>\n

What<\/h3>\n

Error 28 is more of a MySQL error and is not related to WordPress. Even Drupal, Joomla! or other CMS’ websites can experience it.<\/p>\n

Why<\/h3>\n

Error 28 can occur if the cache on your web server is full or if you have too many files in your \/tmp directory.<\/p>\n

The Solution<\/h3>\n

If you can, then try to empty your \/tmp directory. Alternatively, you should contact your web host to help you resolve the cache related issues.<\/p>\n

Warning: Cannot Modify Header Information — Headers Already Sent<\/h2>\n

What<\/h3>\n

Sometimes, you may encounter an error that goes along the lines of: \"Warning: Cannot modify header information -- headers already sent by (output started at \/path-to-something-directory\/some-config-file:xyz )\"<\/code>.<\/p>\n

Why<\/h3>\n

This error is caused by the unrequired spaces in the mentioned WordPress file (generally, it is the wp-config.php<\/code> file). Naturally, you will need to edit the concerned file to remove the unnecessary whitespaces<\/a>.<\/p>\n

The Solution<\/h3>\n
\"Post
Remove Extra Spaces From wp-config.php File<\/figcaption><\/figure>\n

Download the file that is mentioned in the error (say, wp-config.php). Open it using an editor of your choice, and then ensure that there are no spaces either before <?php<\/code> or after ?><\/code> tags. Overall, the first letters of the file should be <?php<\/code> and the last letters should be ?><\/code> (with absolutely no spaces between \u2018?\u2019 and \u2018<\u2019 or \u2018>\u2019 either).<\/p>\n

As already mentioned, most of the time this error happens due to spaces in the wp-config.php file. It can be some other file too, though — just read the error carefully because it specifies the file name and the path to the concerned file.<\/p>\n

Warning: File_Get_Contents<\/h2>\n

What<\/h3>\n

An error such as this one:<\/p>\n

Warning: file_get_contents (http:\/\/www.url.com\/url) [function:file-get-contents]: failed to open stream on line xyz<\/code><\/p>\n

Why<\/h3>\n

Most of the time, such errors occur because your web host has strict security settings in the PHP configuration (\u201csecurity\u201d not as in to prevent hacks, but to prevent overuse of server resources, etc.).<\/p>\n

The Solution<\/h3>\n

If you have access to the php.ini<\/code> file, you can resolve the error yourself. Open the file, and locate the following line:<\/p>\n

allow_url_fopen = Off<\/code><\/p>\n

Now change the \u201coff\u201d value to \u201con\u201d, as follows:<\/p>\n

allow_url_fopen = On<\/code><\/p>\n

If you do not have access to your php.ini file, you will need to contact your web hosting provider and ask them to enable allow_url_fopen<\/code>. Also, if this error is followed by a message such as “failed to open stream: no such file or directory in…”,\u00a0<\/strong>it can mean that the mentioned file is either missing or not readable (look for it in the specified path, and if you find it, check its file permissions).<\/p>\n

There you have it — solutions to the most common WordPress errors! Got an error message or a solution of your own that I missed? Share it in the comments below!<\/p>\n

Photo: vector warning sign<\/a> from BigStock<\/p>\n","protected":false},"excerpt":{"rendered":"

Looking for solutions to WP problems? Worried by database connection nightmares? Read on to find out how to cure some common WordPress ailments.<\/p>\n","protected":false},"author":152321,"featured_media":112768,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"blog_reading_time":"","wds_primary_category":0,"wds_primary_tutorials_categories":0,"footnotes":""},"categories":[235,263],"tags":[1004],"tutorials_categories":[],"class_list":["post-112660","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-misc","category-tutorials","tag-database"],"_links":{"self":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/posts\/112660","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/users\/152321"}],"replies":[{"embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/comments?post=112660"}],"version-history":[{"count":8,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/posts\/112660\/revisions"}],"predecessor-version":[{"id":189594,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/posts\/112660\/revisions\/189594"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/media\/112768"}],"wp:attachment":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/media?parent=112660"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/categories?post=112660"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/tags?post=112660"},{"taxonomy":"tutorials_categories","embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/tutorials_categories?post=112660"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}