What if I could tell you that many of your common WordPress errors can be fixed with just a few clicks? This article will teach you how to solve the nine most common WordPress issues with step-by-step instructions.
This article will cover many errors, from “internal server error” to “images not uploading” and many more. The main tools required for the solutions would be an FTP client and a text editor. However, you need to follow a few steps for most errors.
That said, let’s get started.
- WordPress Parse or Syntax Error
Syntax error generally occurs when trying to add code snippets on WordPress. If the code has incorrect syntax or unexpectedly makes a typo, you’ll most likely overcome this error. The notice that usually occurs is:
Parse error- syntax error, unexpected $end in /public_html/site1/wp-content/themes/my-theme/functions.php on line 278
To fix the WordPress parse or syntax error, you need to ensure the code you’re writing is correct. Missing out even a bracket, character, or symbol can result an error. We recommend searching for that particular code on Google and double-checking to ensure you know the correct code.
- Internal Server Error:
Among the component WordPress errors is the internal server error. It occurs when there’s a particular problem with the database or your WordPress editor, but the server can’t seem to identify the problem.
The error usually occurs as:
- Internal Server Error
- Or, 500 Internal Server Error
To fix the internal server error, you may have to figure out its cause (an error) on your own. You can try the following things to identify the problem and fix that to overcome this error:
- Check for Corrupt .htaccess file
- Increase the PHP memory limit
- Deactivate all plugins
- Re-uploaded core files
- Contact your hosting support
- Error Establishing a Database Connection
You may see this error when trying to access your WordPress website at times. As it suggests, you see this error when your website cannot connect to the database.
The core causes of this error are:
- Incorrect entering/modification of database credentials.
- Corrupted database.
- Unresponsive database.
Anyway, incorrect credentials are the primary cause of this error. Check out the following things to overcome this error:
- Check your WordPress database credentials
- Check your database host information
- Repair WordPress database
- Check if your database server is down
If it doesn’t help, you can try these methods:
- Reboot your web server
- Contact your managed WordPress hosting company
- Update your WordPress site URL
- WordPress White Screen of Death
It is yet another everyday WordPress error users face. It usually occurs in the form of a plain white screen. Unfortunately, there is no error message when it occurs—leaving you puzzled & not knowing what to fix.
The leading cause of this error is the PHP memory limit exhausted by a script. The error will be caught if a WordPress plugin or theme has caused it. You can fix the error using WordPress recovery mode.
Furthermore, a server configuration could also result in a WordPress white screen of death. Also, note that it’s possible that you only see this error on specific sections on your website.
- WordPress Sidebar Below Content
This error is common among beginners. In this error, the website’s sidebar appears below the content instead of appearing next to the content. The cause of this error, as you might have assumed, is the theme that the person is using.
For instance, if you unexpectedly forget to add an extra closing div or close an HTML div tag, it could disturb the entire theme layout. Moreover, other causes of this error include incorrect width in the CSS site editor and not specifying float property.
You can follow these tips to overcome this error on your WordPress site:
- Restore an older version of your WordPress theme (Or undo recent changes to your WordPress theme).
- Deactivate all the WordPress plugins temporarily.
- Use the W3C Validator tool to find an unclosed div element.
- Find the CSS that could be moving the sidebar below the content.
- Lastly, clear your WordPress cache.
- WordPress Login Page Refreshing and Redirecting Issue
Generally, an attempt to log into your WordPress editor redirects you back to the WordPress login page. This error is not that common. However, you may still face it while logging into your WordPress editor.
Here are the leading causes of this error:
- Incorrect values for site URL
- Incorrect values for home URL
- Poor permalink settings on WordPress
- Redirects setup in the .htaccess file.
Take the following steps to overcome this issue:
- Clear cookies (it’ll resolve login issues)
- Update WordPress URL settings
- Delete the “.Htaccess” file in WordPress
- Deactivate all WordPress plugins
- Revert to your default WordPress theme
- Render-Blocking JavaScript And CSS
Render-blocking resources are considered errors related to CSS and JavaScript files in most cases. For example, leading the important CSS at the top is mandatory to display the content with the required style correctly. So browser calls every CSS and JavaScript file in a queue.
If any queue is stuck or files are broken, your website will not appear on the user screen, resulting in render-blocking JavaScript and CSS. If the script is too large, then it will cause a delay in the website’s page load time on your visitor’s screen.
You can remove this error by applying Defer and Async procedures. You can visit this article for more details.
- WordPress Images Not Uploading
This error occurs when you upload an image to WordPress editor to insert in a post. You may notice that images from your WordPress media files are all wiped away. So, the images in the WordPress library appear broken.
This issue can have many causes, but incorrect file permissions are the most common. So, to fix the error, you’ll have to change the file permissions.
However, it’ll require you to use an FTP client. You can use this program to change file permissions by changing the subdirectories. The recommended directory permission is 744. You can also go for 755 alternatively.
- Sorry, This File Type Is Not Permitted For Security Reasons
WordPress, by default, does not support all file formats that users upload due to security reasons and pop-up an error msg “Sorry, this file type is not permitted.”
Like when you are uploading an image with AVIF format from the WordPress admin, it will display an error of File Type is Not Permitted because WordPress does not support AVIF file format by default.
There are different methods to remove this error. You can remove this error using wp-config.php, footer.php or plugin. For more details, please visit this article.
- Locked Out of the WordPress Admin Area
Forgetting your WordPress credentials is normal. But, it can lead to this error where you’re logged out of the WordPress admin area and can’t sign in.
To overcome this issue, you need to access the database connected to your website and find the table “wp_users table.”
Once you access the table, find your username in the user_login column, click edit, and you’ll be able to write a new password. However, make sure to save the changes as you input a new password.
Not using the new credentials, you’ll be able to log back into your WordPress site.
Note: The table can have a different prefix in the name if you change that during the installation.
- 404 Errors and Missing Images on WordPress
It’s not uncommon that you come across a website and realize that a particular webpage is giving off the 404 error. It seems even weirder when you realize that the other website pages are working fine.
The main reason for this error is faulty rewrite rules that you can fix quickly. First of all, re-save your permalink structure under Settings > Permalinks. It will clear up the .htaccess file and generally resolves the error.
However, if it doesn’t work, you may have to overcome the issue manually. In the roots directory, look out for .htaccess file and add the following code:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
That’s all, it might get the issue solved.
- The Link You Followed Has Expired
During file, image, themes, and plugins, sometimes the WordPress backend through an error “The link you followed has expired”. The error does not show any description, so it’s difficult to resolve it for beginners. The error was caused due to different reasons like the file size exceeding the allowed limit, the file taking too much time to upload the file then allowed and the Incompatible Php version.
You can resolve this error with the help of the below code files.
- Edit Functions.php file
- Edit .htaccess file
- Edit PHP.Ini file
- Update PHP Version
Here is the step-by-step article on how to resolve the error “The Link You Followed Has Expired.”
Final Words
We hope this article helped you resolve your WordPress errors and find practical solutions for them. Is there any other WordPress error you’re facing? If yes, comment below, and we’ll consider including that too in this guide.
Until next time, cheers!