查看源码

==Help Your Server Find the 404 Page== 
By default, if WordPress cannot find a particular page it will look for the tt404.php/tt web page. However, there may be cases where the web server encounters a problem before WordPress is aware of it. In that case, you can still guarantee that your web server sends the visitor to your tt404.php/tt template file by configuring your web server for custom 404 error handling.

To tell your web server to use your custom error files, you'll need to edit the tt[[Glossary#.htaccess|.htaccess]]/tt file in the main directory (where main index.php file resides) of your WordPress installation. If you don't have an tt[[Glossary#.htaccess|.htaccess]]/tt file, see [[Using_Permalinks#Editing Rewrite Rules (.htaccess)|Editing Rewrite Rules (.htaccess)]] on how to create an tt[[Glossary#.htaccess|.htaccess]]/tt file.

To ensure the server finds your 404 page, add the following line to your code[[Glossary#.htaccess|.htaccess]]/code file:

preErrorDocument 404 /index.php?error=404/pre

The url /index.php is root-relative, which means that the forward slash begins with the root folder of your site. If WordPress is in a subfolder or subdirectory of your site's root folder named 'wordpress', the line you add to your tt.htaccess/tt file might be:

preErrorDocument 404 /wordpress/index.php?error=404/pre


===Additional Error Code Handling===
*Mental Excercise for the most part you don't need this*
Please try to use as many static errordocuments as you can, as a single tt/missing.html/tt file being server for a missing image (404 Not Found) would take up incredibly less CPU and Memory than having it processed by tt/index.php?error=404/tt

To enable your WordPress 404.php template file to handle additional server errors, you can use something like this in your tt.htaccess/tt file.

Notice how some errors are handled by WordPress, while other errors output a static .html document, and a few are actual php scripts.  For instance, a 500 error would not be suitable to be handled by WordPress, as the 500 error could be occuring due to WordPress, like a bad plugin.  So by instructing your server to instead serve a static .html document you can display a much more helpful error message to your visitors.

pre
ErrorDocument 400 /cgi-bin/error-deal.php
ErrorDocument 402 /cgi-bin/error-deal.php
ErrorDocument 403 /error/403/index.html
ErrorDocument 404 /index.php?error=404
ErrorDocument 405 /error/405/index.php
ErrorDocument 406 /index.php?error=406
ErrorDocument 407 /index.php?error=407
ErrorDocument 408 /index.php?error=408
ErrorDocument 409 /index.php?error=409
ErrorDocument 410 /index.php?error=410
ErrorDocument 411 /index.php?error=411
ErrorDocument 412 /index.php?error=412
ErrorDocument 413 /index.php?error=413
ErrorDocument 414 /index.php?error=414
ErrorDocument 415 /index.php?error=415
ErrorDocument 416 /index.php?error=416
ErrorDocument 417 /index.php?error=417
ErrorDocument 418 /index.php?error=418
ErrorDocument 419 /index.php?error=419
ErrorDocument 420 /index.php?error=420
ErrorDocument 421 /index.php?error=421
ErrorDocument 422 /index.php?error=422
ErrorDocument 423 /index.php?error=423
ErrorDocument 424 /index.php?error=424
ErrorDocument 425 /index.php?error=425
ErrorDocument 426 /index.php?error=426
ErrorDocument 500 /error/503/index.html
ErrorDocument 501 /index.php?error=501
ErrorDocument 502 /index.php?error=502
ErrorDocument 503 /error/503/index.html
ErrorDocument 504 /index.php?error=504
ErrorDocument 505 /index.php?error=505
ErrorDocument 506 /index.php?error=506
ErrorDocument 507 /index.php?error=507
ErrorDocument 508 /index.php?error=508
ErrorDocument 509 /index.php?error=509
ErrorDocument 510 /index.php?error=510
/pre