The RevvedUp theme

****** POST-INSTALLATION INSTRUCTIONS *******

These instructions will lead to an optimal installation of this theme.  These instructions assume that your blog is anchored to your web server root -  if this is not the case, you will need to tune the following .htaccess directives.

ARCHIVE PAGE

This theme requires a plugin which enables the archive page (location hard-coded at /archives/) , various error pages and directory indexes.  The plugin is included and is named RevvedUp-plugin.php.  Deploy it to your plugins folder and activate it.


FAVICON

Most browsers request a favicon when they connect, which can skew statistics if the favicon cannot be found (this is valid for most statistics plugins, such as StatTraq).  If you're using elegant error pages, add this rewrite rule:

<IfModule mod_rewrite.c>
RewriteRule ^favicon.ico$ /wp-content/themes/RevvedUp/images/favicon.ico [QSA,L]
</IfModule>

evidently you have to adjust the path if your theme is installed in a different Web location.


ELEGANT DIRECTORY LISTINGS

You can also let this theme beautify directory listings for folders that don't have an index.html or index.php.  Use the following .htaccess directive for that:

-------------------------------------------------------------------
DirectoryIndex index.html index.shtml index.php /index.php?showpage=directoryindex
------------------------------------------------------------------

Where the first index.html, index.shtml and index.php are the preferred directory index files, and the last one (/index.php?showpage=directoryindex) is the location of your WordPress topmost index.php.


ELEGANT HTTP ERROR PAGES

You can, at your option, also let this template handle HTTP errors gracefully.  Put this in your .htaccess:

---------------------------------------------
ErrorDocument 400 /index.php?showpage=error&httperror=400
ErrorDocument 401 /index.php?showpage=error&httperror=401
ErrorDocument 403 /index.php?showpage=error&httperror=403
ErrorDocument 404 /index.php?showpage=error&httperror=404
ErrorDocument 405 /index.php?showpage=error&httperror=405
ErrorDocument 408 /index.php?showpage=error&httperror=408
ErrorDocument 410 /index.php?showpage=error&httperror=410
ErrorDocument 411 /index.php?showpage=error&httperror=411
ErrorDocument 412 /index.php?showpage=error&httperror=412
ErrorDocument 413 /index.php?showpage=error&httperror=413
ErrorDocument 414 /index.php?showpage=error&httperror=414
ErrorDocument 415 /index.php?showpage=error&httperror=415
ErrorDocument 500 /index.php?showpage=error&httperror=500
ErrorDocument 501 /index.php?showpage=error&httperror=501
ErrorDocument 502 /index.php?showpage=error&httperror=501
ErrorDocument 503 /index.php?showpage=error&httperror=503
ErrorDocument 506 /index.php?showpage=error&httperror=506
---------------------------------------------
and so on for each error code that you want to handle.  Be aware that attempting to handle HTTP error 403 (Forbidden, which is triggered when the Web server is not allowed to enter a folder) in a .htaccess directive will most certainly fail for directory listings, because the Web server will be looking for an extra .htaccess on that folder, and fail at that point, before parsing the parent .htaccess file.  Thus, if you have access to your Web server main configuration files, these directives would work better there.
