{"id":21826,"date":"2020-02-18T12:00:41","date_gmt":"2020-02-18T17:00:41","guid":{"rendered":"https:\/\/webdevstudios.com\/?p=21826"},"modified":"2024-04-15T11:57:50","modified_gmt":"2024-04-15T15:57:50","slug":"fix-wordpress-errors","status":"publish","type":"post","link":"https:\/\/webdevstudios.com\/2020\/02\/18\/fix-wordpress-errors\/","title":{"rendered":"How to Fix These 5 Common WordPress Errors"},"content":{"rendered":"

Do these sound familiar? White screen of death. Locked out of the admin. 404 not found. 500 internal server error. I could go on and on, but these are some of the most common errors and issues you will encounter when dealing with a WordPress website. So, if you are close to pulling your hair out or hiding somewhere thinking and hoping that maybe tomorrow everything will be fixed, and all is going to be right in the world again, don\u2019t worry. You are not alone. It is not the end<\/em>. WordPress is a stable platform, but there is nothing out of the ordinary about encountering issues. Keep reading to learn how to fix common WordPress errors (without going bald).<\/p>\n

\"\"<\/p>\n

WordPress has a huge 35% share of the internet pie. More often than not, the issue you\u2019re having has been documented somewhere with a fix added in for good measure.<\/p>\n

Outlined below are five of the most common WordPress errors and issues and how to fix them in the easiest<\/em> possible way. There will be minimal hand-holding here; you will need to figure out how to get to where you need to go to make changes.<\/p>\n

Most of the fixes described below will require you to have some PHP knowledge, knowledge of the WordPress Admin, and an understanding of how to use your hosting platform’s tools. But mostly, you’ll just need common sense and the ability to follow instructions to a T.<\/p>\n

Issue 1: Locked Out of WordPress Admin<\/strong><\/h2>\n

Scenario:<\/strong> You forgot your password and you don’t have access to the recovery email address.<\/em><\/p>\n

Fix:<\/strong> The easiest way to fix this WordPress error is to do it via PHPMyAdmin using a SQL statement.<\/p>\n

Log into your hosting’s admin panel, then open phpMyAdmin. Select your WordPress Database from the left column, then select the SQL tab and add the following code. Make sure that you\u2019ve changed `new_pasword`<\/em> and `your_username.`<\/em><\/p>\n

UPDATE `wp_users` SET `user_pass` = MD5( 'new_password<\/em><\/strong>' ) WHERE `wp_users`.`user_login` = \"your_username<\/em><\/strong>\";<\/code><\/p>\n

\"\"<\/p>\n

However, if you want to create a new admin user, you can drop this instead (make sure to change the values to the right ones).<\/p>\n

INSERT INTO `databasename<\/strong>`.`wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES ('4<\/strong>', 'username<\/strong>', MD5('password<\/strong>'), 'Your Name',<\/strong> 'email@email.com<\/strong>', 'http:\/\/www.website.com\/can-be-blank<\/strong>', '2011-06-07 00:00:00<\/strong>', '', '0', 'Your Name<\/strong>');
\n<\/code><\/p>\n

INSERT INTO `databasename<\/strong>`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, '4<\/strong>', 'wp_capabilities', 'a:1:{s:13:\"administrator\";s:1:\"1\";}');
\n<\/code><\/p>\n

INSERT INTO `databasename<\/strong>`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, '4<\/strong>', 'wp_user_level', '10');<\/code><\/p>\n

 <\/p>\n

Issue 2: Maintenance Mode Error<\/strong><\/h2>\n

Scenario:\u00a0<\/strong>You updated your theme and\/or plugin and somehow it did not go through the whole process and now you’re stuck in Maintenance Mode.<\/em><\/p>\n

Fix:\u00a0<\/strong>There are a lot of fixes to this, but if you need your website up and running in the shortest time possible, you will need to access your website files and you can do that via FTP, your host’s File Manager, or by using an SSH connection. You will need to delete just one file that sits right at the root of your website files -> .maintenance<\/strong><\/em><\/p>\n

FTP<\/strong><\/h3>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

File Manager<\/strong><\/h3>\n

\"\"<\/p>\n

\"\"<\/p>\n

SSH Connection<\/strong><\/p>\n

Connect via SSH to your server. Navigate to your website’s root folder and type the following code:<\/p>\n

rm .maintenance<\/code><\/p>\n

Issue 3: HTTP Image Upload Error<\/strong><\/h2>\n

Scenario:<\/strong>\u00a0You could not upload and have the same issue with any image you try to upload no matter the file size. You went through the basic troubleshooting: disabled plugins, default theme, but nothing works. All you can see is a generic HTTP error.<\/strong> There is no explanation, just that you can’t upload anything. It is not a glitch nor a plugin conflict. What else can you do?<\/em><\/p>\n

\"\"<\/p>\n

Fix:\u00a0<\/strong>There are three fixes to this WordPress error that you can try:<\/p>\n

Increase Memory Limit<\/strong><\/h3>\n

Edit your wp-config.php<\/strong> file, found at the root of your WordPress site. Add the following right above where it says:\u00a0\/*\u00a0That’s\u00a0all,\u00a0stop\u00a0editing!\u00a0Happy\u00a0blogging.\u00a0*\/<\/em><\/p>\n

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

 <\/p>\n

Shared Hosting? Use the .htaccess Hack<\/strong><\/h3>\n

Imagick(ImageMagick)<\/strong> is one of the two modules WordPress uses to handle images. And shared hosting usually limits Imagick’s ability to use multiple threads. To fix this error, edit your .htaccess\u00a0<\/strong>file and add the code below right at the top of your .htaccess.<\/p>\n

MAGICK_THREAD_LIMIT 1<\/code><\/p>\n

 <\/p>\n

Ditch Imagick and Use GD Library Instead<\/strong><\/h3>\n

Command<\/del> Tell WordPress to use the GD Library\u00a0<\/strong>to handle images by adding the code below to your theme’s\u00a0functions.php\u00a0<\/strong>file.<\/p>\n

wp-content -> themes -> your-theme ->\u00a0functions.php<\/strong><\/em><\/p>\n

function wds_default_image_library( $editors ) {
\n$gd_editor = 'WP_Image_Editor_GD';
\n$editors = array_diff( $editors, array( $gd_editor ) );
\narray_unshift( $editors, $gd_editor );
\nreturn $editors;
\n}
\nadd_filter( 'wp_image_editors', 'wds_default_image_library' );
\n<\/code><\/p>\n

Issue 4: <\/strong>404 Not Found Error<\/strong><\/h2>\n

Scenario:\u00a0<\/strong>Out of nowhere, a page on your website is no longer accessible and serving you NOTHING. Nada. Zilch. You might have enabled or disabled a plugin, maybe changed a theme. You’ve already cleared your cache and you know you have the right URL.<\/em><\/p>\n

Fix:\u00a0<\/strong>The first thing you can try is to reset your\u00a0WordPress permalinks. <\/strong>You can just click the\u00a0Save Changes\u00a0<\/strong>button and that will reset your permalinks without you changing anything. But, I usually do the extra step of setting it to Plain<\/strong> first and then save. Go check on the post or page to see if it works. If it does, put it back to Post name\u00a0<\/strong>or whatever your chosen permalinks setting is.<\/p>\n

WordPress Dashboard -> Settings -> Permalinks<\/strong><\/em><\/p>\n

\"\"<\/p>\n

One extra step to try, if just resetting won’t work, is to rename your current .htaccess<\/strong> to something else. The .htaccess file sits right at the root of your WordPress files. You can then create another .htaccess file and copy the default one below for versions 3.5 and up. If you are running a WordPress Multisite<\/a> or version 3.4 and below, check this WordPress Support article<\/a>\u00a0for the .htaccess to use.<\/p>\n

# BEGIN WordPress
\n<\/code><\/p>\n

RewriteEngine On
\nRewriteBase \/
\nRewriteRule ^index.php$ - [L]
\nRewriteCond %{REQUEST_FILENAME} !-f
\nRewriteCond %{REQUEST_FILENAME} !-d
\nRewriteRule . \/index.php [L]
\n<\/code><\/p>\n

# END WordPress<\/code><\/code><\/code><\/p>\n

After doing that, go through the process of resetting your permalinks again to see if it works. If it does not, change to a default theme. If it works, then the issue is with your theme.<\/p>\n

Issue 5: <\/strong>500 Internal Server Error<\/strong><\/h2>\n

Scenario:\u00a0<\/strong>This is another generic error that does not exactly tell you what’s wrong with your website. All you know is that your website is currently NOT WORKING.<\/em><\/p>\n

Fix:\u00a0<\/strong>If you can access your WordPress admin start at step 1. If not, start at step 3.<\/p>\n

    \n
  1. Disable plugins.<\/strong> Did it work?\n