Preventing the WordPress .htaccess file rewriting requests from a specific sub-dir

JK · 2009-08-13, 03:28 PM

Say I have WP installed at the root of a domain and I have free sites in the /sites/ sub-dir. I don't want /sites/oops.html to be parsed by the RewriteRule at the root of the domain.

I thought adding this would do the trick:

Code:

RewriteCond %{REQUEST_URI} !^/sites/.*$

which would make the entire .htaccess file at the root of the domain:

Code:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} !^/sites/.*$
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

This doesn't seem to work.

I have also tried adding a blank .htaccess file to /sites/ (and /sites/free-site/) and adding RewriteEngine Off to these files. These don't work either.

Is what I want to achieve possible?

2009-08-13, 03:28 PM	#1
JK Well you know boys, a nuclear reactor is a lot like women. You just have to read the manual and press the right button Join Date: Nov 2003 Posts: 157	Preventing the WordPress .htaccess file rewriting requests from a specific sub-dir Say I have WP installed at the root of a domain and I have free sites in the /sites/ sub-dir. I don't want /sites/oops.html to be parsed by the RewriteRule at the root of the domain. I thought adding this would do the trick: Code: RewriteCond %{REQUEST_URI} !^/sites/.$ which would make the entire .htaccess file at the root of the domain: Code: <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteCond %{REQUEST_URI} !^/sites/.$ RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> This doesn't seem to work. I have also tried adding a blank .htaccess file to /sites/ (and /sites/free-site/) and adding RewriteEngine Off to these files. These don't work either. Is what I want to achieve possible? __________________ To alcohol! The cause of, and solution to, all of life’s problems