Greenguy's Board - Preventing the WordPress .htaccess file rewriting requests from a specific sub-dir

Greenguy's Board (http://www.greenguysboard.com/board/index.php)

- Programming & Scripting (http://www.greenguysboard.com/board/forumdisplay.php?f=15)

- - Preventing the WordPress .htaccess file rewriting requests from a specific sub-dir (http://www.greenguysboard.com/board/showthread.php?t=54022)

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:



RewriteEngine On

RewriteBase /

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

RewriteCond %{REQUEST_FILENAME} !-f

RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule . /index.php [L]

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?

In the subdirectory, in the .htaccess

RewriteEngine off

will turn it off.

If it isn't, then something is wrong with the apache config. It is possible that mod_rewrite is turned off for certain directories, but, that would again be a server config issue. Some hosting companies running on networked storage do have a slight lag for the webserver to pick up that there has been a change to the files in directories, so, it is also possible that the .htaccess with RewriteEngine off hadn't been noticed by apache or the webserver software your server uses.

Thanks cd34, I thought it should have worked.

I'll get in touch with my host to see if there's a funky configuration.

:)