Common Errors In WordPress

91. Common errors in WordPress.

If you are facing a WordPress error message or white screen, don’t panic! Someone will have faced the same message before and it can easily be solved.

I’ll try to list the most common WordPress errors experienced by WordPress users in this article, and provide a starting point for fixing them.

Both PHP errors and database errors can display as a white screen, a blank screen with no information, commonly known in the WordPress community as the WordPress White Screen of Death (WSOD).

Before resorting to desperate measures, there are a number of reasons for the WordPress white screen of death:

  • Plugin is causing compatibility issues. If you can access the Administration Screens try to deactivate all of your Plugins and then reactivate them one by one. If you can’t access your Screens, log in to your website via FTP. Locate the folder wp-content/plugins and rename the Plugin folder plugins_old. This will deactivate all of your Plugins.
  • Your Theme may be causing the problem. This is especially possble if you are experiencing the white screen of death after you have just activated a new Theme, or created a New Site in a WordPress Network. Just log in to the WordPress Administration Screens and activate the default WordPress Twenty Fifteen Theme. If you are unable to access your Administration Screens, access your website via FTP and navigate to the /wp-content/themes/ Rename the folder for the active Theme.

There may be a number of reasons for an Internal Server Error. Here are some things you can do to solve it:

  • The most likely issue is a corrupted .htaccess Log in to your site root using FTP and rename your .htaccess file to .htaccess_old. Try to load your site to see if this has solved your problem. If it works, make sure to visit Settings > Permalinks and reset your permalinks. This will generate a new .htaccess file for you.
  • Try to deactivate all of your Plugins to see if it is a Plugin issue. If you can’t access your WordPress Administration Screens, deactivate your Plugins via FTP by following these instructions.
  • Switch the Theme to the WordPress Twenty Fifteen Theme to eliminate any Theme-related problems.
  • Increase the PHP Memory limit
  • Try re-uploading the wp-admin and wp-includes folders from a fresh install of WordPress.

If you your page is featuring the message “Error Establishing Database Connection,” this means that there is a problem with the connection to your database and there could be a number of reasons for this. Here are possible reasons and solutions:

  1. Incorrect wp-config.php Information

“Error establishing a database connection” is usually caused by an error in your wp-config.php file. You should access your site in your FTP client. Open wp-config.php and ensure that the following are correct:

  • Database name
  • Username
  • Database password
  • Database host
  1. Problems with Your Web Host

Next step is to contact your web host. The following hosting issues may be causing the problem:

  • Your database has met its quota and has been shut down.
  • The server is down.
  • Contact your hosting provider to see if either of these issues is causing your problem.
  1. Compromised Website

If you have checked wp-config.php for errors, and confirmed with your host for hosting issues, possibly your site has been hacked.

You should scan your site with Sucuri SiteCheck to ensure that it hasn’t been compromised.

  1. Failed Auto-Upgrade

There may be situations when the WordPress auto-update feature fails. Symptoms are:

  • A blank white screen and no information.
  • A warning that the update failed.
  • A PHP error message.

The WordPress automatic upgrade feature may fail due to a glitch in the connection with the main WordPress files, a problem with your Internet connection during upgrade, or incorrect File Permissions.

  1. Connection Timed Out

“The connection timed out” error appears when your website is trying to do more than your server is able to manage. It is mostly common on shared hosting where your memory limit is restricted. Here are some things you can try:

  • Deactivate all Plugins. If deactivating all the WordPress Plugins on your site resolves the issue, reactivate them one-by-one to see which plugin is causing the problem. If you are unable to access your Administration Screens, read about how to manually deactivate your plugins.
  • Switch to the default WordPress Twenty Fifteen Theme. This must rule out any Theme-related problems.
  • Increase your memory limit in wp-config.php. If you are on shared hosting you may have to ask your hosting provider to increase your memory limit for you.
  • Increase the maximum execution time in your php.ini file. This is not a WordPress core file so if you are not sure how to edit it, contact your hosting provider to ask them to increase your maximum execution time. See instructions for increasing maximum execution time.
  1. Maintenance Mode Following Upgrade

When WordPress updates, it automatically installs a .maintenance file. Following upgrade, you may receive a message that says “Briefly unavailable for scheduled maintenance. Please check back in a minute.” The maintenance file may not have been removed properly.

To remove this message you should do the following:

  • Log in to your website using your FTP program
  • Delete the .maintenance file, which will be found in your site root.
  1. You Make Changes and Nothing Happens

If you make changes to your website and you do not see the changes in your browser, you may need to clear your browser cache. Your browser stores information about the websites which you visit. This makes it faster to load websites when you visit them since the browser just has to reload information already stored on your computer, rather than downloading it again.

If you make a change to a website and the browser does not think it is significant, it will simply load the data from your cache, and you won’t be able to see your changes. To fix the problem, just empty your browser cache or close the tab and reopen the link.

For more error types and their solutions, you may look up in the WordPress Codex, guys!

I hope this article was helpful for you!

Share this!

One Comment

  1. most things cover. If you can’t find it here check on Google, as WPkicker says someone, somewhere will have had the same problem

Leave a Comment

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