WordPress and error messages: Unfortunately, sometimes a couple too well known. From time to time errors creep in during operation - especially when updates are being carried out or new plugins are being used. Even when editing CSS and PHP files of the theme, it can quickly and unintentionally happen that WordPress no longer works as it should.

Over the years, typical mistakes have emerged that have been encountered by almost every WP admin. In many cases they can be fixed with a few clicks. In this article, we will gladly reveal which clicks are involved.

A quick word in advance: Backups help with disasters

It goes without saying: Proper website maintenance also means that backups are always available. If a disaster occurs that cannot be fixed quickly, then up-to-date backups are worth their weight in gold. After all, backups are made for just such cases - and that is when everything is running smoothly, not when it is already too late.

Syntax error fix in WordPress

A syntax error usually occurs when you try to add code snippets in WordPress - and accidentally miss something or the code has an incorrect syntax. This leads to a PHP parse error. WordPress or the server on which WP is installed will display a message like

Parse error - syntax error, unexpected $end in /html/website/wp-content/themes/my-theme/functions.php on line 158

In plain text: Something was found in the given PHP file, which simply does not belong there. In many cases this "something" was simply created by omitting something else before. Mostly it is a missing bracket or an unexpected character in the code. If the missing bracket is reinserted and the file is saved, the page often runs without problems again.

Internal Fix Server Error with WordPress

One of the most common errors is the Internal Server Error, sometimes also described as 500 Internal Server Error This error usually occurs when something is wrong, but the server is not in is able to identify the exact cause of the problem. Since the error message unfortunately does not specify where to look for the error, everything remains somewhat mysterious. It's up to you to figure out exactly what the problem is.

Typical sources of error are in the configuration file .htaccesswhich is located in the root directory of the server. Straight in Combination with your own permalinks can cause problems. Often it is enough to reset the permalinks to the WP standard.

If an Internal Server Error occurs more often, the memory limit for PHP on the server should be increased, if possible. WordPress sometimes needs a lot of memory, but providers of shared hosting sometimes don't give enough memory to their customers by default.

Error at Fixing the establishment of a database connection

Another classic is the "error in building a Database Connection" (or Error Establishing a Database Connection). WordPress finds - for whatever reason - no more access to the database, in which displays all information e.g. about entries and pages of the WP installation are located. The error can occur during operation or directly at Installation.

A simple solution is to use the data stored in the wp-config.php stored access data to the database, so this is exactly the one here:

define('DB_NAME', 'database_name');
define('DB_USER', 'database_username');
define('DB_PASSWORD', 'database_password');
define('DB_HOST', '');

entries can now be corrected and the file wp-config.php can be saved. The front end of the WP Web page should then work. If not, then the database may be corrupted and must be repaired. This can be done via the tool phpMyAdmin.

If the solutions suggested above do not work, the database server may be temporarily unavailable.

Error 404 on individual contributions or pages

A rather curious error occurs when individual posts or pages of the WP installation show an error 404 instead of the desired content. Often the start page and the backend is affected by this error not affected. In this case it is almost always Error with the permalinks.

Here it is often enough to select the tab for Permalinks and save the settings again. If it comes then still results in error 404, then the configuration file .htaccess in the root directory of the WP installation can be taken.

A standard .htaccess with permalinks enabled under WordPress looks like this:

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule /index.php [L]

# END WordPress

Sometimes it can also happen that the file does not have the necessary rights to do what it should. The permissions should be set to 640 - or temporarily set to 660. The error 404 for individual posts should then disappear.

👉 In the following article you will learn how to direct a 404 error to your homepage.

White Fix Screen of Death

As the "White Screen of Death," an entirely white page described. The website itself has virtually disappeared, a more or less helpful error message does not exist either - but the backend is often still attainable.

Most of the time the error is caused by a script has exhausted the PHP memory limit. But it can also be due to a Pass configuration of the server. It is also possible that a "white screen of death" threatens only on certain subpages. Here helps to increase the memory limit for PHP.

In any case, it is worth looking directly into the backend area of the WP installation. WordPress offers help here and informs you if a plugin or theme causes "too many" errors. In this case the culprit is found quickly. It can also be worthwhile to deactivate all plugins at once and then reactivate them one by one.

Sidebar slides under the contents

Another common problem - which is particularly common for beginners - is the sidebar, which suddenly appears below the actual content, although it has no place there. You may know this problem if you use html code to build a page - one missing character, one html section too many - and it can "shoot up" your page.

Sometimes when adding or editing code snippets to their site, users inadvertently forget to close a div tag or add an additional closing div, which can cause the theme's layout to get confused. Another common cause is the use of a "disproportionate" width in CSS, or not deleting a float properly.

So: Close all divs correctly and the sidebar becomes a sidebar again.

pictures upload not possible: fix upload error

If pictures cannot be uploaded (anymore) via the upload function of WordPress, this can have various reasons. Some are caused by the pictures themselves, others by the server where WordPress is installed.

It should first be checked whether the image format is supported by WordPress at all (JPGs, GIFs, PNGs and SVGs) Here especially in the last few years, it happens again and again that WEBP files but this format is still not supported by WordPress is supported - but plugins can solve this problem.

If it's the server, then maybe the physical Memory space overfilled. This can happen especially when only one small web hosting package was chosen.

But it is also possible that the wp-content folder does not have the necessary rights to allow the upload of files. Here, 755 is required, while the files themselves have permissions of 644. This should be checked and adjusted if necessary, then in many cases it will work again with the upload of pictures.

Another cause can be the actual file size. Restricts your Hoster or a setting the max upload size will cause WordPress to give an error message here if your file exceeds this size.

WordPress login: Fix permanent redirects

When logging in to the WP page it can sometimes happen that the login page keeps trying to redirect the user - and to simply fails. What sounds simple can actually have serious consequences. There will be consequences: Users will no longer be able to log on.

Here you can set Cookies could be the source of the error. It is therefore advisable to delete the cookies for the domain without further ado and to start the login again afterwards. If this does not help, the .htaccess file in the root directory of the installation can be deleted. In this case WordPress forgets the settings for Permalinks. They must then be reconfigured.

Sometimes it can also be useful to add the following two lines to the wp-config file

define('WP_HOME', 'http://example.com');
define('WP_SITEURL', 'http://example.com');

This makes it clear to WordPress that both settings are the same values. Please note that the settings in the backend cannot be changed manually. Only when the two lines are deleted will the settings appear again in the backend.

403 Forbidden Error

Access denied? The "403 Forbidden Error" says just that off. Various reasons can be responsible for the fact that access to the homepage or a subpage remains prohibited - even if it is the user has admin rights.

Often it is a plugin, which is responsible for this error message is responsible. This is either incorrectly configured or can be corrected with existing security precautions on the server. At the latter case, it is worth looking for an alternative to the plugin.

Possibly a broken .htaccess file is also the reason for the "403 Forbidden Error". Here you can delete the broken file and then generate the permalinks (and thus a new .htaccess) in the backend.

ERR_TOO_MANY_REDIRECTS: Fix too many redirects

Unfortunately, the classic ERR_TOO_MANY_REDIRECTS also continues to drift his nuisance. Here there are redirects, which sometimes refer to themselves which leads to an unsightly endless loop.

Much like the problem of the login redirections, it may be helpful to check the configuration file wp-config.php set the "WordPress Address (URL)" and "Website Address (URL)".

If that doesn't work, read our Special articles on the topic: WordPress error "ERR_TOO_MANY_REDIRECTS": This is the easy way to fix it.

Unfortunately, the classic ERR_TOO_MANY_REDIRECTS also continues to drift his nuisance. Here there are redirects, which sometimes refer to themselves which leads to an unsightly endless loop.

Much like the problem of the login redirections, it may be helpful to check the configuration file wp-config.php set the "WordPress Address (URL)" and "Website Address (URL)".

If this does not lead to success, then read our special article on the subject: WordPress error "ERR_TOO_MANY_REDIRECTS": This is how it can easily be fixed.

Conclusion: 10 typical WordPress errors - and how you can easily fix them

WordPress has been around for several years - here it is it is only understandable that some error messages appear again and again. Some can be avoided simply by waiting for a proper hosting package is set. Also the economical use of plugins preserves site operators from many a pitfall.

Of course, it is also clear that not every mistake is the end of the world. Do the tips and tricks listed here help no further, then a backup must be imported.

About Christian

My name is Christian and I am co-founder of the platform fastWP. Here in the magazine I am responsible for the more "technical" topics but I like to write about SEO, which has been my passion for over 10 years now.

Leave a Comment

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