WordPress Url Rewrite Rules

Sunday, July 18th, 2010 at 3:30 pm

When WordPress Permalinks 404

The 404/Not found error message is one of the most hated screens online, but indicates that even though the browser, were able to communicate with the server, the page you need not be delivered, either because it was found or because the server for some reason has been configured not comply with the request (what is happening in some countries illegal content pages).

The page you see really is not generated by the computer, but a special page on the server that you have tried to contact. Many sites create their own special 404 pages either for artistic reasons, or because The site owner wants to put specific data such as contact information or redirect in the page. In Apache, have their own special 404 page is so simple as modifying the file. Htaccess. (The only exception: the page must be greater than 512 bytes or IE does not show it.)

In most cases, the error 404 appears when a page has been moved or deleted from a site. However, in the case of WordPress, an annoying bug can cause permalinks to point to the 404 page instead of the page you want to touch the subject.

How WordPress Permalinks work?

Permalinks are permanent generated URLs to point to the weblog individual categories, and lists of weblog. Other bloggers use a permanent link to point to his post their own articles, or you can send links to others through a permanent link. When linked to an individual post, the URL is supposed to be permanent, not dynamic (changing).

The three WordPress permalinks types of offers are the default (also known as "Ugly") is, mod rewrite ("Pretty"), and PathInfo ("Almost Pretty ").

Default links are formatted according to the default settings for a new installation of WordPress, and work on all server environments. What looks like this: http://example.com/?p=N Where N is a number. It is neither clear nor elegant, but does the job. Pretty mod rewrite links are more like this: title = "http://example.com/yyyy/mm/dd/post-name/"> http://example.com/yyyy/mm/dd/post-name/ . These permanent links require module Apache mod_rewrite, and will not work on server types. Permalinks PathInfo this: and work in other types of servers in addition to Apache.

Because you go a dynamic to a fixed environment with permanent links, a variety of things can go wrong with them. For example, if your server has FrontPage extensions, permalinks will not function at all, without manual review. Without this revision, the changes to the permanent links section of the WordPress administration interface will damage the Home server extensions, as it interferes with the file. htaccess.

Permalinks can cut time and with only a part of it working properly or the entire link with disabilities. This will cause a 404 error to be generated - but not because there is something wrong with your permalink, and not because the title is too long. You can editing the file address. Htaccess 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 angle brackets () on each end. Software most problematic of email and other not truncate URLs formatted this way.

Permalink Structure in WordPress

When the links do not work, it is often because their structure has not updated Permalink. Each time you add a new static page to your WordPress files, you must generate and update the new rules for the. Htaccess (in the latest versions are addressed through the management control area). If you do not get a page back to all, even a 404, and the use of PHP 5 with Apache 4.4 or 2 should look like in insects and PHP pages problem. This is a specific error known.

By creating permanent links, other strange thing can happen: your WordPress blog must start the process of creating a permanent link before you know if the page you're creating one to really exists. If not, too late - the link is already pointing to an error page 404. To fix this, you must include instruction 404 in the file header. htaccess to rewrite permit conditions not found error, and simply delete that page of his work permalinks. Try adding the following line above the WordPress rewrite rules, outside # BEGIN WordPress WordPress [...]# END. Some plugins will overwrite this part if you change the permalinks structure if it is in the wrong place.

404/index.php ErrorDocument? Error = 404?

Another solution is to use this as follows:

404/foo/index.php ErrorDocument? Error = 404

foo = The directory is used as a blog. The structure should be:

/ Foo% /% category /% postname% /

If you call a nonexistent directory, however, you still going to have to permalink 404.

You can automate the tasks of permanent links with various plugins, however. The Ultimate Tag Warrior (UTW) has received some good reviews, especially for search engine pages and sensitive. Google Sitemaps is a complement good too.

One more thing: if you use xampp settings, your WordPress permalinks do not work at all in the default installation ..

The ultimate solution is actually the installation of WordPress 2.0.2, this new version has fixed the problem with permalinks, and a number of other problems.

Always check all the pages before starting to work with permalinks, and after they Permalink. In some cases, you may need to delete all permanent links and start again, but in most cases only look at what you are telling your server to do the will to avoid making a lot of stupid mistakes.

About the Author

http://www.theinternetone.net

How to configure SEO-friendly URL for WordPress