System: Debian Etch, Apache 2.2

I have a WordPress instance with multiple blogs. I would like to redirect some of the folders based on the year and month, while leaving other folders to go to the actual locations.

Example: I have archives for a few years, like 2010, 2011 and 2012:

  • http://example.com/wordpress/myblog/2010/02
  • http://example.com/wordpress/myblog/2011/01
  • http://example.com/wordpress/myblog/2012/01

I would like to redirect all 2010 and 2011 posts to another blog with the same folder structure:

  • http://example.com/wordpress/myotherblog/2010/02
  • http://example.com/wordpress/myotherblog/2011/01
  • and so on.

I would like to have 2012 and beyond to go to the actual site (ie. http://example.com/wordpress/myblog/2012/01).

I tried mod_rewrite with the following, one rule at a time to test redirection for just one year (and to expand later for other years), and none of them worked!

  • RewriteEngine is already on since there are some default WordPress rewrites.
  • RewriteBase is set to http://example.com/wordpress/.
  • I put my rule before all the other default WordPress rules are processed.

Didn't work solution #1

RedirectMatch 301 /myblog/2010/(.*) /myotherblog/2010/$1

Didn't work solution #2

RewriteRule /myblog/2010/(.*) http://example.com/myotherblog/2010/$1 [R=301]

Didn't work solution #3

RedirectPermanent /myblog/2010/(.*) http://example.com/myotherblog/2010/$1

I've also tried the above rules with and without a fully qualified URL for the new location.

The rewrite log, with log level set to 9, did not provide any useful information. It shows that it looks at the pattern specified against the URL (as mentioned in the rule), but finally what happens is a passthrough to http://example.com/myblog/ for all URLs or a 500 Internal Server Error.

Any ideas on where I could be going wrong or any alternative solutions?


2 Answers 2


I can't explain why your rules don't work without seeing the whole .htaccess file, but you might find the Monkeyman Rewrite Analyzer Plugin helpful:-

It is only an analyzer, it does not change any rules for you. It parses the rules down to their components and shows the connection with the resulting query variables. It allows you to try out different URLs to see which rules will match and what the value of the different query variables will be.

This might give you some better clues on how to debug your code.

  • Thanks for the response. Unfortunately, I cannot install any WordPress plugins on the site for specific reasons beyond my control. I downloaded this plugin to look at the code. Are there other ways to validate the rules? I'll post the entire .htaccess file after sometime.
    – Ps Cjef
    May 30, 2012 at 19:05
  • @PsCjef AFAIK this is the only one, Wordpress can be hinky though. Delete then reapply your permalink settings and try flushing your machine's DNS cache before testing the rules again. May 30, 2012 at 19:15

Try the following RewriteRule:

RewriteRule ^myblog/(2010|2011)/(.*)$ http://example.com/myotherblog/$1/$2 [R=301,L,NC]

Notice the inclusion of the L flag (last directive) the NC flag for nocase and the fact that the path name doesn't include the forward slash (since you might be dropping a .htaccess file into a directory). If it is not in a .htaccess file in a directory path that doesn't include the forward slash then simply:

RewriteRule ^/myblog/(2010|2011)/(.*)$ http://example.com/myotherblog/$1/$2 [R=301,L,NC]

If you are not sure of either then

RewriteRule myblog/(2010|2011)/(.*)$ http://example.com/myotherblog/$1/$2 [R=301,L,NC]

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.