PHP rewrites.

[jerry_louise]

Is it possible to have php set up my

## PHP REWRITES ##
RewriteEngine On
RewriteBase /
RewriteRule ^([a-zA-Z0-9_-]+)$ html/index.php?page=$1
RewriteRule ^([a-zA-Z0-9_-]+)/$ html/index.php?page=$1

RewriteRule ^([a-zA-Z0-9_-]+)/([a-zA-Z0-9_-]+)$ html/index.php?page=$1&process=$2
RewriteRule ^([a-zA-Z0-9_-]+)/([a-zA-Z0-9_-]+)/$ html/index.php?page=$1&process=$2

Instead of having to manually input different ones into the .htaccess file i would rather able to sent it one from my php file, perhaps making a function so i could tell it were having the "page/date/process" instead of just the "page/date".

[sneakyimp]

You should check out the RewriteMap directive. NOTE that you cannot define rewrite maps in an htaccess file -- it has to be done in the apache conf.

[jerry_louise]

One thing i have just thought of is the possibility of using an array. This would make the .htaccess very simple and the array can be infinitely complex.

Code:

RewriteEngine On
RewriteBase /
RewriteRule ^([^/]+)/?$ html/index.php?location=$1

PHP Code:

PHP Code:

$data[0] = $module
$data[1] = $id
$data[2] = $date
$data[3] = $page


This would hopefully mean i could have
http://mysite.com/blog/13/11/2009/this_is_a_post/page_1 (with the id hidden perhaps)

or a second example with a simpler array say just module and id
http://mysite.com/news/artical_12

Which i would assume would mean that i could have a "complex" navigation structure with very little code compared to a manual method.

Any thoughts on this method?

[sneakyimp]

That latest rewrite you suggest seems perfectly reasonable. I'm sure it's common practice to punt to PHP to handle the incoming request rather than making an elaborate .htaccess file for little advantage. It will certainly result in a much simpler htaccess file.

[Ashley Sheridan]

Take care with having PHP handle all of this though, as it is much faster to have Apache do it. Depending on the number of requests and the general response you get from your site at the moment, you might be better off leaving most of the work to the .htaccess file.

Just a thought though. Why can't you add the .htaccess to the apache group (sometimes wwwrun or www), allow group write access, and have PHP write the .htaccess file from whatever you're using to create the pages; I presume a CMS?

[jerry_louise]

Originally Posted by Ashley Sheridan

Take care with having PHP handle all of this though, as it is much faster to have Apache do it. Depending on the number of requests and the general response you get from your site at the moment, you might be better off leaving most of the work to the .htaccess file.

Just a thought though. Why can't you add the .htaccess to the apache group (sometimes wwwrun or www), allow group write access, and have PHP write the .htaccess file from whatever you're using to create the pages; I presume a CMS?

I am making my own CMS type system, i am looking at using a .htaccess only but i get confused when it comes to different base for the rewrite rule.

All pages link to index.php, ?page=blog or forum or reviews, est. Is where i get confused as they all have slightly different navigation systems that are made to match there respective areas.