The 404 / Not Found error message is one of the most hated screens on the Internet; indicates that even if you, the browser, were able to contact the server, the page you need was not delivered because it was not found or for some reason the server was configured not to complete the request (which happens in some areas. countries with pages with illegal content).
The page you are viewing was not created for your computer; instead, it is a special page on the server that you tried to contact. Many websites create their own 404 special pages for technical reasons, or because the site owner wants to put certain data, such as links or redirections, to the page. In Apache, having your own 404 special page is as easy as converting an .htaccess file. (Only warning: page must be larger than 512 bytes or IE will not display it.)
In most cases, a 404 error occurs when a page is deleted or deleted from the site. However, in the case of WordPress, an annoying bug can cause permalinks to point to page 404 instead of the page you want to display.
How does WordPress Permalinks work?
Permanent Permalinks URLs are generated to point to your posts for each blog, categories, and list of web blogs. Some bloggers will use permalink to direct your posts to their articles, or you can post links to other people via permalink. When connected to each post, the URL should be permanent, not dynamic (changing).
The three types of permalinks introduced by WordPress are the Default form (aka “Ugly”), mod rewrite (“Pretty”), and PATHINFO (“Almost Beautiful”).
The default links are formatted according to the default settings for the new WordPress installation, and will work across all server locations. It looks like this: http://example.com/?p=N, N number. It is not clean and neat, but it does the job. Links to good mode rewriting look like this: http://example.com/yyyy/mm/dd/post-name/. These permalinks require Apache's mod_rewrite module, and will not work on other server types. PATHINFO permalinks look like this: http://example.com/index.php/yyyy/mm/dd/post-name/, and will work on other server types besides Apache.
Because you go from a fixed location to a fixed location with your permalinks, various things may go wrong with it. For example, if your server incorporates Frontpage Extensions, permalinks will not work at all without performing manual editing. Without this correction, any changes in the permalinks section from the WordPress administrator interface will damage the Frontpage server extensions because they are disrupting the .htaccess file.
Long permalinks can be terminated again, only half of them work properly or the whole link is turned off. This will cause 404 error - but not because there is anything wrong with your permalink, rather because the title is too long. You can edit it by editing your .htaccess file to add a line:
RewriteRule ^ post / ([0-9] +)? /? ([0-9] +)? /? $ /Index.php?p=$1&page=$2 [QSA]
You can also make a habit of posting URLs with angular () brackets on both sides. Too much email and other troublesome software will not reduce URLs formatted this way.
Permalink structure in WordPress
If your links do not work, it is usually because you have not updated your Permalink configuration. Every time you add a new static page to your WordPress files, you should generate and update new rules in .htaccess (which in new versions are managed by the administrator control panel). If you do not find a fully restored page, even 404, and you are using PHP 4.4 or 5 with Apache 2, you should check that for PHP bugs and news pages. This is a well-known distraction.
When you create permalinks, another strange thing can happen: your WordPress blog should start the process of creating a permalink before it knows whether the page you are creating exists or not. If it doesn't, it's too late - your link is already pointing to page 404. To fix this, you need to enter 404 guidance in the header of your .htaccess file so that your rewriting conditions allow for error detection, and simply delete that page from your permalinks function. Try adding the following line above the WordPress rewriting rules, except for the 'START START WordPress'…] #END WordPress. Some plugins will override this section if you are editing the permalinks structure if it is in the wrong place.
ErrorDocument 404 / index.php? Error = 404?
Another solution is to use the following:
ErrorDocument 404 / foo / index.php? Error = 404
foo = index that you use as a blog. The structure should be as follows:
/ foo /% category% /% postname% /
If you call a non-existent guide, however, you will still get that 404 permalink.
You can automatically perform your permalinks functions with several plugins, however. The Ultimate Tag Warrior (UTW) has received some positive reviews, especially the critical pages of the search engine. Google Sitemaps is also a great plugin.
One more thing: if you use xampp settings, your WordPress permalinks will not work at all in the default installation.
The ultimate solution is actually to install WordPress 2.0.2; this new version fixed the permalinks problem and a number of other issues.
Always double-check all of your pages before you start working with permalinks, and after you have officially linked them. In some cases, you may need to remove all permalinks and restart, but in most cases just checking what your server tells you to do will prevent you from making too many stupid mistakes.
You must be logged in to post a comment.