The 10 Most Common WordPress Issues With Their Solutions

The 10 Most Common WordPress Issues With Their Solutions – There is no doubt that WordPress is one of the best platforms for building your website, but even the most experienced users have to deal with some common WordPress issues that shock them.

If you’re a beginner, facing these problems is often pretty scary. WordPress errors can seem complicated, overly technical, and you would possibly not know where to start out in resolving them.

We understand your irritation!

Everyone has needed to start somewhere, so we’ve put together the 10 most common WordPress issues with their solutions to resolve them.

So we will learn the methods to solve the 10 most common WordPress issues with their solutions in this article.

Backup Your Site before Fixing WordPress Errors

Before learning the 10 most common WordPress issues with their solutions, there’s one thing you ought to always do.

Back up your website!

You should always make an entire backup of your WordPress site before making any changes and have a daily backup schedule. This is often so if you can’t fully resolve your issues, you’ll have a full working copy of your site able to restore.

There are many backup plugins you’ll use to make a restore point for WordPress. You’ll even create a manual WordPress backup if you’d prefer.

10 Most Common WordPress Issues With Their Solutions

With a backup of your site, let’s check out the 10 most common WordPress issues with their solutions you’ll be facing.

1. WordPress Stuck in Maintenance Mode

WordPress Stuck in Maintenance Mode - sitepoint

WordPress Stuck in Maintenance Mode – sitepoint

Sometimes when you’re making changes to your website, you’ll see a message almost like the one above saying your site is undergoing care.

WordPress can get stuck in maintenance mode during a WordPress update or when you’re updating a bunch of plugins or themes.

If WordPress is interrupted during this process, it doesn’t have the prospect to require your site out of maintenance leading to locking down your site and making it unavailable.

WordPress automatically puts your site into maintenance mode during updates, so your visitors don’t see a broken version of your website. But when it’s stuck in maintenance mode, you and your visitors won’t be ready to access it anyway.

To solve this problem, install the CMP plugin, set up the maintenance page, and enable and turn off the maintenance page when required.

2. Facebook and Instagram oEmbeds Breaking Issue

Since October 24th, 2020, you’ll have noticed that any Facebook or Instagram content you post in WordPress using the standard oEmbed or Embed Blocks feature is suddenly broken.

This is right down to a change in Facebook’s API. The API is significant for both the block and classic WordPress editor, normally allowing you to embed social content, images, and other media directly into your posts and pages.

Now, Facebook requires developers to register an app and use a client token to retrieve data from their Graph API for oEmbed content.

Since this isn’t a scalable solution for the core WordPress team, they decided to get rid of Facebook and Instagram oEmbeds, in favor of using WordPress plugins as a solution.

As a result, any Facebook or Instagram oEmbeds not work and can appear like this:

Facebook and Instagram oEmbeds Breaking Issue - site point

Facebook and Instagram oEmbeds Breaking Issue – site point

That is unless you employ a WordPress plugin to require over from where oEmbeds left off.

The easiest thanks to fixing the oEmbed issue is with Smash Balloon’s social media feed plugins.

They have individual plugins for

Since Smash Balloon has got to register an API key to make custom feeds for Facebook and Instagram, you won’t need any extra authentication to revive your embeds. Plus, you won’t need to undergo the complicated process of making your own app.

3. WordPress Memory Exhausted Error

WordPress Memory Exhausted Error - sitepoint

WordPress Memory Exhausted Error – sitepoint

If you see an error similar to the one above that says the WordPress Memory is exhausted, it could be down to a script or WordPress plugin that’s exhausting the default memory size limit.

The error usually displays a message like the one below:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2348617 bytes) in /home/username/public_html/site1/wp-includes/plugin.php online.

You can easily fix this memory issue by increasing the PHP memory limit in WordPress.

To do this, FTP into your website and locate the wp-config.php file, which you’ll find in your site’s root folder.

WordPress Memory Exhausted Error – site point

WordPress Memory Exhausted Error – site point

Then copy and paste the subsequent code into your wp-config.php file before the road that says, ‘That’s all, stop editing!’

define( ‘WP_MEMORY_LIMIT’, ‘256M’ );

What this code does is inform WordPress to extend the PHP memory limit to 256MB.

Save your changes and upload the file back to your server. The error should now disappear once you visit your site.

4. Connection Timed out Error in WordPress

Connection Timed out Error in WordPress - sitepoint

Connection Timed out Error in WordPress – sitepoint

If you see the “ERR_CONNECTION_TIMED_OUT” error in WordPress, it always means your website is trying to try to quite it can manage all directly and is pretty common if your site is on shared hosting.

Some of the leading causes of this problem are resource-hungry plugins, issues together with your theme functions, and PHP memory exhaustion.

You can begin troubleshooting this issue by deactivating your plugins one by one then trying to access your website after each deactivation. You would possibly find that one of your plugins is causing the error.

Another possible solution is increasing your memory limits in PHP and WordPress using the steps we outlined earlier within the article.

If none of that works, it’s an honest idea to contact your hosting provider to ascertain if they assist.

5. Error Establishing a Database Connection in WordPress

The error establishing a database connection problem suggests that your site can’t connect to your database.

Error Establishing a Database Connection in WordPress - site point

Error Establishing a Database Connection in WordPress – site point

This can happen when you’ve modified or entered your database details incorrectly, such as:

  • Your database host.
  • Database username.
  • Database password.

Alternatively, your database might be unresponsive or corrupted.

To fix this common WordPress issue, you ought to first see if you get an equivalent error on your website’s front and rear (wp-admin).

If you get a special error on the wp-admin page of your website, like “One or more database tables are unavailable. The database may have to be repaired”, you would like to repair your database.

Repairing your database is pretty simple. FTP into your website and add the subsequent line of code into your wp-config.php file just before the ‘That’s all, stop editing!’ line:

define(‘WP_ALLOW_REPAIR’, true);

Now save the changes, re-upload the file to your server.

Error Establishing a Database Connection in WordPress - sitepoint

Error Establishing a Database Connection in WordPress – sitepoint

When you’ve finished repairing your database, remove the line from your wp-config.php file.

6. WordPress Internal Server Error

"<yoastmark

The WordPress internal server error is usually the foremost common WordPress issue and therefore the most confusing too.

This error message typically shows up when something is wrong, but the server doesn’t know where the matter is. And since the message doesn’t tell you where to seem to repair the difficulty, it’s mostly right down to you to seek out it.

When trying to resolve this issue, first check if your .htaccess file is corrupted. You’ll do that by accessing your site using FTP and locating the .htaccess file which you’ll find within the same directory as folders wp-content.

"<yoastmark

Now rename the .htaccess file to something like .htaccess-old and re-visit your website to ascertain if the error has been solved.

If it worked, proceed to your WordPress dashboard and navigate to Settings » Permalinks.

"<yoastmark

Then click the save button without making any changes, which can create a replacement .htaccess file with the proper rules, so you don’t see a mistake anymore.

7. WordPress Parse or Syntax Error

"<yoastmark

When the WordPress parse or software error comes up, it’s normally when you’re adding snippets of code into your WordPress files. The code could have incorrect syntax, otherwise, you may need to miss a character or two when copying it over.

You’ll usually see a mistake just like the one below:

Parse error- software error, unexpected $end in /public_html/site1/wp-content/themes/my-theme/functions.php on line 549.

To solve this common WordPress issue, you ought to first consider this guide for beginners on the way to paste snippets from the online to WordPress to make sure you’re not making any mistakes.

Once you recognize the way to copy and paste snippets in WordPress correctly, you’ll move onto fixing the matter. To repair a software error, you’ll need to edit the code that caused it.

This might sound scary, but it’s easy to repair, don’t worry.

If you added a replacement code snippet via your WordPress dashboard area, the likelihood is that you’re locked out of your site. With this in mind, you’ll need to access your site files using FTP.

"<yoastmark

When you’ve connected to your site files, find the file you edited with the code snippet. If you’ve forgotten which file that was, check out the error code because it tells you exactly where the error is.

Then remove the code you added or rewrite it with the right syntax.

When you’re done, save the file and re-upload it to your server. Then refresh your WordPress site. Your site should now be working correctly!

8. WordPress not Uploading Images

"<yoastmark

When you’re performing on your website, you would possibly sometimes find that you simply can’t upload images properly to the media library. Don’t worry; you’re not alone in this! It’s a reasonably common WordPress issue that we’ve seen often.

If WordPress isn’t uploading images correctly, it’s probably right down to incorrect file permissions, and if it’s, you’ll typically see the subsequent error message:

“Unable to create directory wp-content/uploads/2019/04. Is its parent directory writable by the server?”

Another sign of this error is that your images disappearing from the WordPress media library like this.

"<yoastmark

To fix WordPress’s issue of not uploading images, you’ll first need to connect to your site via FTP. Then head to your /wp-content/ folder.

Inside this folder, you’ll find an uploads folder where your media is stored, including images.

To set the file permissions for your media uploads, right-click the uploads folder and select File permissions to bring up the file permissions dialogue box.

"<yoastmark

First of all, set the file permissions for the uploads directory and all subdirectories inside it to 744.

"<yoastmark

Then check the box next to where it says ‘Recurse into subdirectories” and choose the “Apply to directories only” option. Click okay to apply the changes.

The next step is to line file permissions for the files in the uploads directory.

Right-click on the uploads directory and choose File permissions. Within the dialogue box, change the numeric value to 644.

"<yoastmark

Check the box next to “Recurse into subdirectories” and click on “Apply to files only” Click okay to apply the changes.

When you’re finished, head back to your WordPress dashboard and check out re-uploading your images again.

9. WordPress Login Redirect Loop

"<yoastmark

There may come a time when trying to log into WordPress; the login page will keep redirecting and refreshing. This is often called a WordPress login redirect loop and maybe pretty frustrating.

One of the simplest ways to repair this redirection error is to clear the cookies in your browser. This is often because WordPress uses browser cookies to authenticate your login details.

To clear your browser cookies in Chrome, attend your Chrome Settings and Advanced » Clear Browsing Data.

"<yoastmark

Clear your browser, cache, and cookies, then ensure your browser has cookies enabled.

When you’ve done this, restart your browser and refresh your WordPress login page to undertake logging in another time.

10. 403 Forbidden Error in WordPress

403 Forbidden Error in WordPress - sitepoint

403 Forbidden Error in WordPress – sitepoint

The WordPress 403 forbidden error code is typically displayed when your server doesn’t allow you to access a specific page. More often than not, you’ll see the subsequent error message:

403 Forbidden – You don’t have permission to access ‘/’ on this server. Additionally, a 403 Forbidden error was encountered while trying to use an Error Document to handle the request.

There are quite a few reasons you would possibly see this error, but incorrect file permissions and poorly coded plugins are usually the most culprits.

One of the foremost common solutions for this WordPress issue is to troubleshoot your WordPress plugins. You’ll do that by deactivating all of your plugins, including any security plugins you’ll have installed.

If the error is resolved once you’ve done this, a plugin is certainly the matter. Start reactivating the plugins one by one until you see the error again, highlighting the matter plugin.

And that’s it!

Today you’ve learned the 15 most common WordPress issues and their solutions to resolve them.

The problems we’ve covered above are among the foremost common ones you’ll run into in WordPress, so this list should have you ever pretty much prepared for all common scenarios that show up.

And since you’ll avoid many of the problems we’ve covered by employing a WordPress hosting provider, so choosing the best hosting for your WordPress Website.

We hope you found this text helpful. If you probably did, do follow us on Twitter and Facebook for more content like this.

The 10 Most Common WordPress Issues With Their Solutions

Leave a Reply