What is causing /user/*/taxonomy/term/* to redirect to /taxonomy/term/*?

Question

I got a view with contextual filters set up as the following:

• Global: Null (Fixed value "user")
• Content: Author uid (User ID from URL)
• Global: Null (Fixed value "taxonomy")
• Global: Null (Fixed value "term")
• Content: Has taxonomy term ID (Taxonomy term ID from URL)

When I go to mysite.com/user/*/taxonomy/term/* I'm being redirected to mysite.com/taxonomy/term/*.

How can I prevent this?

I also got Pathauto to change the URLs to [user:name] for user/* and tags/[term:name]for taxonomy/term/*.

Edit: If I disable the URL alias for the taxonomy terms it still redirects to mysite.com/taxonomy/term/*.

Answer 1

The source of the redirect could be essentially any module you have, and several modules allow for configuration that will cause redirects as well. You will need find the source of the redirect on for your particular situation.

Suggestions:

1. Deactivate modules in a 50 / 50 manner. This allows you to quickly narrow down which module is providing the redirect, and hopefully that will help you to work it out. Using drush to disable/enable modules will make this much faster.

2. Install Devel. It has a settings called "Display redirection page", and implements devel_drupal_goto_alter halting the redirection.

   The primary purpose of this is to gather up debug information that would otherwise go lost due to the redirect. In this particular case, I suggest you add a dpm(debug_backtrace()); into the hook so you can trace the call to the source of the redirect.

3. Everything else failing, fire up a full debugger, and trace the call, ideally with help from the information provided by the debug_backtrace() above.

Answer 2

Implement hook_drupal_goto_alter() in a module and

a) put a breakpoint on code in this function and view the call-stack to determine which function is setting the redirect in the first place.

b) change the path.

path is passed by reference so this can be changed directly. Assuming you create a module name ungoto:

ungoto_drupal_goto_alter(&$path, &$options, &$http_response_code) {
   // regular expression can be tightened
   if (preg_match('#^taxonomy/term/', $path)) {
     // Guessing that you are trying to 'display profiles' not display current 
     // users details, so global $user is not useful. 
     // Contextual filters says is is on the path. 
     // OP to do work to extract only the information needed.
     $user_details = $_GET[q];

     // Reset the path
     $path = $user_details . $path;   
   }
}

Answer 3

You could use hook_exit($destination) to change the redirect.

• Create a new module. I use the Netbeans drupal-7 plugin to create .install, .info and .module files.
• Fill out the .info template.
• Implement hook_exit($destination). Call another drupal_goto(). Be careful that it can't create a redirect loop.

Hook Exit passes the destination address, and if you put a debugger on it you may be able to trace the call-stack to find another drupal_goto() that is causing the redirect.