How to solve the most common WordPress errors

Although WordPress is the most widespread CMS, it is not perfect and it is not free of errors … If we add to this the huge ecosystem of plugins, themes and configurations that could have the servers where it is installed, we run the risk of encountering some problem, but If you follow our recommendations, you will surely come out of it.

The feared “white screen of death”

One of the mistakes that we can find in WordPress is that the page appears blank, without showing absolutely nothing. It is what many know as “white screen of death”. The causes can be very varied, but among the main solutions that allow us to tackle this problem, we can:

  • Activate display_errors , either through the server control panel or in the PHP file, display_errors = on; .
  • Assign a higher value to memory_limit .
  • Activate the Debug mode , editing the wp-config.php file and adding the define line (‘WP_DEBUG’, true); .
  • Disable plugins. Via FTP, we can rename the entire folder / wp-content / plugins  or rename each of the plugins’ folders. To enable them again, we do the reverse step.
  • Deactivate the theme. Simply rename the active theme folder and examine the code. If the theme folder does not exist, the best option is to return to the default theme of the Administration.
    To reactivate the theme. We add a new theme from the WordPress Administration or manually, via FTP, in the wp-content / themes folder . In the wp-config file , you must add the define line (‘WP_DEFAULT_THEME’, ‘folder-theme’); and do the same in the DB in the table wp_options . In  template / Styles / current_theme .

Connection error with the BBDD

Sometimes our content manager can throw errors with the database that feeds it. One of the possible solutions is to configure the accesses correctly through wp-config.php :

// ** MySQL settings. Request this information from your web hosting provider. ** //
 / ** The name of your WordPress database * /
 define ('DB_NAME', 'name-bbdd');
 / ** Your MySQL username * /
 define ('DB_USER', 'user');
 / ** Your MySQL password * /
 define ('DB_PASSWORD', 'password');
 / ** MySQL host (it is very likely that you do not need to change it) * /
 define ('DB_HOST', 'localhost');

Error 500 Internal Server Error

It can be an unidentified error, the .htaccess is wrong or the memory_limit.   Again, we can address the problem with different solutions:

  • The solution is to rename and regenerate .htaccess . To do this, connect via FTP with the option to show the hidden files and rename the .htaccess file . Next, go to the WordPress administration and go to settings> permanent links> Save Changes . This will generate a new .htaccess .
  • Enable DEBUG
  • Disable plugins and / or themes.

404 Error Not Found

In this case, there may be problems with the .htaccess , missing files or failing the Custom Post Type (here we recommend you check the articles on these custom WordPress entries ).
Among the possible solutions, we can access the WordPress administration, go to settings> permanent links> Save Changes .

Error 403 You are not allowed

This message is due to restrictions or permissions, something that we can solve in different ways:

  • Generate from as we have seen before the .htaccess.
  • Use FTP to assign the permissions: 644 (General) and 755 (write).

Memory_limit | Time Out

This is a web server configuration problem. In order to solve it:

  • In the control panel of the server changes the parameters of memory_limit = 128M; and max_execution_time = 60;
  • In the file wp-config.php edit the line corresponding to define (‘WP_MEMORY_LIMIT’, ‘128M’) ;.

Warning | Notice

Actually, it is a warning, not an error. To prevent it from reappearing, we can:

  • Optimize the web page.
  • Ignore the message To do this, disable DEBUG / display_errors.

Syntax / Fatal Error

This error is displayed when there are code errors. The solution is to review the code or undo changes that we have made in this.

Are you sure you want to do this?

This message tells us that there may be an error in the configuration, in the theme or in the plugin. Among the possible solutions:

  • Increase the values ​​of upload_max_filesize and post_max_size.
  • Disable Plugins and / or Themes.

Warning: Cannot modify header information – headers and sent by …

It is an error that WordPress throws when there is an error in the code or that there are headers after the page. The solutions go through:

  • Disable the errors are displayed.
  • Space review Before <php and after ?>.
  • Review the file path.

Briefly unavailable for scheduled maintenance. Check back in a minute.

The update may have failed. The solution may be to delete or rename the file that has been generated .maintenance .

Leave a Reply