404 Errors WordPress

404 Errors WordPress

404 Errors WordPress

WordPress is widely-used by both individuals and business entities for running their website, and most importantly, for creating blogs. That’s because of the ease it provides in making edits in a site and its content. However, no software is without flaws and sometimes a few minor tweaks can make your site inaccessible. But there’s nothing much to worry as you can easily find a solution to any WordPress related issue. But the dreaded 404 errors can be a real pain in the neck to WordPress users and developers alike. Allow the team at Xcurrent Web-Design help walk you through fixing the dreaded 404 errors we’ve all cone to despise!

southparkstudios

Internal server error, or error establishing database connection are most common WordPress errors that can cause panic among novices. And another highly common error that crops again and again is the 404 error message, appearing when we access a post. In this post we’ll help you understand about when accessing a WP post returns “404 Not Found” error and how it can be fixed.

Does everything 404?

If every page and post across your site returns a 404 (Page Not Found error), or if your front page is accessible but nothing else (including regular WordPress pages) then, unfortunately, you’ve got bigger problems than we can really help with.

In a situation like this it would probably be worth reaching out to your designer or developer, if you have one, or else to your web host for further assistance. There is also the whole community of helpful folks over on the WordPress forums who might be willing to pitch in and offer advice, too.

error-404-road-not-found

When does a post returns 404 error?

Many site owners often experience 404 not found error while accessing their blog’s main page or single post.

Let’s elaborate. The 404 error appears when you install something (like plugins and themes) in your WP blog. But if your posts throw 404 errors, probably in such a scenario your users may be able to view your blog homepage homepage clearly but aren’t able to access a single post. Your server generates the 404 error when a requested URL cannot be found. It’s certain that you’ll panic when you can’t find your blog post, but no need to fret as all your posts still exists within your site’s admin area and are completely safe. However, usually the “404 not found” error pops up if your .htaccess file got deleted accidentally or something went wrong with the rewrite rules. All you need to do is fix your permalinks settings.

Why you should resolve the permalink structure?

Many people still can’t understand the need to fix permalink structure, in fact, sadly beginners often tend to overlook setting up the right permalink structure. But, it’s a really important thing that can’t be neglected and must be set up before adding the website content.

So, what exactly is a permalink structure? It is a link that appear on the top of your browser location bar. A permalink points to your site pages and blog posts, so that they can be found even when they’ve moved from the homepage to archives. A clean and well-written permalink help your readers know what they can expect from the post they’re accessing, and also make search engines locate your posts easily.


changing-permalinks-in-wordpress-properly-e1416046338498

So, what exactly is a permalink structure? It is a link that appear on the top of your browser location bar. A permalink points to your site pages and blog posts, so that they can be found even when they’ve moved from the homepage to archives. A clean and well-written permalink help your readers know what they can expect from the post they’re accessing, and also make search engines locate your posts easily.

Nerd Alert

Put simply, permalinks help promote your blog posts, and so it becomes essential that you have set-up the permalink structure correctly.

Understanding the Process to fix the 404 error

Open your website dashboard, navigate to Settings»Permalinks. If the Permalinks are set to Default or Custom, then choose Postname option (as shown in the screen shot below) and hit the “Save Changes” button. This will help to select your permalinks settings, and thus flushes the rewrite rules. In a lot of cases this solution will help resolve the WordPress posts 404 error.

But what if the solution doesn’t work for you, then you’ll most likely have to update your .htaccess file manually.

Wondering how?

Simply login into your server using FTP to verify if the .htaccess file exists or not. If the file already exist, you’ll find it in the same location where the ‘/wp-content/’ and ‘/wp-includes/’ folders are located.

Modify the .htaccess file by making it writeable, by changing the permissions to 666 on temporary basis. Then carry out the same procedure as described above (re-save your permalink settings). A word of caution make sure to change the permissions back to the original value that is 660.

But, in case you don’t have the permission to update your .htaccess files, then you can update them manually, by adding the following code in your .htaccess file:

# BEGIN WordPress

RewriteEngine On

RewriteBase /

RewriteRule ^index.php$ – [L]

RewriteCond %{REQUEST_FILENAME} !-f

RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule . /index.php [L]

# END WordPress

Let’s Wrap Up!

If you get 404 not found error while opening a single WP post in your WordPress blog, then you can choose to change the permalink structure to one that you prefer. Another way to resolve this issue requires finding whether your .htaccess file exists or not. Hopefully the post will help you better understand about the 404 returning error when accessing a blog post and ways to troubleshoot the problem.


error: Content is protected !!