[wp-hackers] So, this whole .htaccess thing...

[Robert Deaton]

On 8/26/06, Charles <lists06 at wiltgen.net> wrote:
> > It would be helpful if you offered an alternative solution.  [...]
> > It doesn't seem fair to blame WordPress for using the file, with a
> > "how dare you!" air...
>
> Ha!  You can tell I'm in "how dare you!" mode when I use the <armsAkimbo>
> tag.   :O)
>
> Seriously, the solution I offered yesterday was to implement a router that
> handled all requests, then constraining the use of .htaccess to route all
> requests to that router.  The .htaccess file in this case might look like
> this:

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

> I believe that replacing the use of .htaccess with a flexible, extensible
> router would (1) make WordPress more portable (to IIS, for example), (2)
> make WordPress easier to use (I learned quickly that one mistake in an
> .htaccess file can take down your site, or worse, create unexpected and
> hard-to-debug results), and (3) make WordPress more reliable (if plug-ins
> didn't have to mess with plaintext files to extend/enhance routing).

(1) WP does the best it can to support IIS with permalinks, The rest
is IIS's fault.
(2) See (3)
(3) Plugins don't have to :)

-- 
--Robert Deaton