After a bit of tinkering, I figured out that this could be fixed with a small change to the mod_rewrite section that WordPress puts into the site’s .htaccess file. As a happy side effect, this system also allows you to manually cache a particular page, such as if you are suddenly getting hammered by an Instalanche or a Digg link.

Open your site’s .htaccess and you should see the following, which was put there by WordPress:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Change it to this:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
#	RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME}/index.htm !-f
RewriteCond %{REQUEST_FILENAME}/index.php !-f
RewriteRule . /index.php [L]
</IfModule>

# BEGIN WordPress
# END WordPress

With this modification to the basic WordPress .htaccess rewrite, you can now put a hard-coded file in a particular place in the hierarchy.

How Does it Work?

For an example, let’s look at this page in a typical WordPress site:

http://example.com/archives/123

With WordPress running the site, there is no actual folder called “archives”, and in turn no actual “123″ folder or file. WordPress is creating the pages on the fly as they are called. Normally, if you were to actually put a folder called “archives” in that location, WordPress would hand control over to the actual directory.

We, however, don’t want that. We want WordPress to relinquish control with /archives/123, but not with, say, /archives/122, or even just /archives.

Our new .htaccess code above changes how WordPress handles “real” directories. With the new code, it only gives up control if the directory in question contains a file named either “index.htm” or “index.php”

So, to manually override /archives/123, we create an “archives” directory at the root of the site. In “archives”, we create a “123″ folder; and inside that, we create either index.htm or index.php that contains the override page.

Note that the base /archive directory, and any other pages or posts within it (e.g. /archives/122), are still controlled as normal by WordPress.

Another part of the reason I did this was that I have a page on this site that is a demonstration of a CSS method, and I wanted the demo page to be an independent page not run by WordPress (specifically, not complicated by the WordPress template).

You can see it in action here:

http://striderweb.com/nerdaphernalia/webcraft/complexspiral/

Note that http://striderweb.com/nerdaphernalia/webcraft/ is still run normally by the WordPress install that runs the rest of Nerdaphernalia. If I wanted to, I could also make sub-pages of the “ComplexSpiral” page that are also run by WordPress.

You will also note that the “ComplexSpiral” page is listed in the Page listing created by WordPress. That is, the WordPress system knows that there’s a page there, even though it’s not running it. How did I do that? Quite simply, actually. I just made a page with the same address within WordPress — a “placeholder” of sorts. It doesn’t matter what’s in the placeholder page¹, because we’ll never see it — it’s overridden by the hard-coded page we created. But it creates the entry within the WordPress system and thus we see a link to the page within the normal WordPress page listings.

(And yes, you could use it to override a particular post, too.)

There is one final step, and this is important: Be sure to change the permissions on your .htaccess file so that WordPress doesn’t overwrite it with the defaults.

Enjoy!

This article was originally published at Nerdaphernalia. Planet WordPress is authorized to reproduce WordPress-related entries. If you're reading this at any other web site, the site owner is stealing copyrighted work. Please visit the original page:

Feed enhanced by Better Feed from Ozh