ansaurus

Question

What is the .htaccess/mod_rewrite solution for this redirect problem?

Answer 1

A:

RewriteRule ^home/templates/cnb/fb_calendar/events/view/([^/\.]+)?$ /home/index.php?option=com_content&task=view&id=574&Itemid=85&direct=view:$1 [R=302,L]

I just removed the http:// from the url it redirects to.

Works like a charm. Test it here:

http://manson.revora.net/home/templates/cnb/fb_calendar/events/view/1234

goes to

http://manson.revora.net/home/index.php?option=com_content&task=view&id=574&Itemid=85&direct=view:1234

Also, this rewrites the url in the address bar too, but since you added R=302 I take it that's what you wanted? And you don't need that first rule, as pointed out in the comments.

Litso 2010-09-09 08:07:54

This fails in my particular circumstance - I think there is another .htaccess file in a directory on the target path that's interfering - please see Additional information I've edited at the end of my question. Thanks!

Mark Flint 2010-09-09 08:55:44

Yes, that .htaccess definitely interferes, for it sends all requests that end up in the fb_calendar folder to the subfolder /app/webroot/. I don't think it's possible to have a .htaccess rule that overwrites rules in subdirectories, that's just the way htaccess rules work.. You could change the htaccess in the fb_calender folder though but that might mean you're going to have to do that in a lot more folders.

Litso 2010-09-09 09:15:42

Hmm... that's a bit annoying - I want it to rewrite the whole path as it is defined, not parse any other rules along the way. Powerful feature, but if that's not the behaviour you want then it's a big limitation.

Mark Flint 2010-09-09 09:43:01

Wait a second, I might be wrong. The request goes from base folder down to subfolders, but in the base folder you already say you want to rewrite fb_calender to something else. This shouldn't even hit your fb_calendar at all. Maybe there's something else interfering after all.

Litso 2010-09-09 09:49:30

Answer 2

+1 A:

mod_rewrite will, by default, only use directives from a single .htaccess file per (internal) request, and the .htaccess file used will be the last one found to have mod_rewrite directives down your request path.

In this case, .../fb_calendar/.htaccess exists and contains directives, so they are used instead of the directives in your root.

Furthermore, note that none of the directives are inherited automatically, so doing something like the following will generate a 404, since directives are present, but the RewriteEngine was never turned on in the second file:

/.htaccess:

RewriteEngine On

RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ /index.php?here

/test/.htaccess:

RewriteRule ^ /index.php?there

Request -> http://example.com/test/non-existent-path

As it turns out, you can import rules from parent .htaccess files using the RewriteOptions directive:

RewriteEngine On
RewriteOptions inherit

Note that the parent rule set is imported after the existing rule set though, so in your case the path would be rewritten to .../fb_calendar/app/webroot/events/view/... before being processed by the rule in your root .htaccess file (and would therefore not match).

Your options in that case would be to either modify your rule to accommodate for that, or, perhaps more easily, you could just move your rule to the .../fb_calendar/.htaccess file and adjust it for being in that directory.

Tim Stone 2010-09-09 18:28:29

Useful info, thanks.

Mark Flint 2010-09-13 23:01:12

ansaurus

tags:

views:

answers:

What is the .htaccess/mod_rewrite solution for this redirect problem?

related questions