Search
Training
New Podcast
Newsletter
Everywhere
Check out DrupalEasy around the web:
Who are we?
DrupalEasy is the collective expertise of Ryan Price and Michael Anello, who joined forces to provide training and consulting services worldwide. Read all about them and what they can do.
What is Drupal?
Drupal is a free, super-powerful content management system for sites that require information posting and collection, including blogs, forums, videos, photos, and databases of information. We think it is the best platform available. Here's why...
Why Drupal?
More and more savvy organizations are going with Drupal for content management, and its no mystery why. It’s free, flexible, and easy to maintain for small or large volume sites. Learn more...
Making Sure Your Redirects Work as Expected
Whenever you need to write a custom module that involves redirection using the drupal_goto() function, things can always get tricky - especially if there are other forces at work. One such force might be the "destination" variable that sometimes gets passed around in the URL querystring when the user is attempting to access content that requires authentication.
I recently ran across the situation where the "destination" querystring variable was interfering with where I was attempting to redirect the user to. Luckily, there was a simple solution - I just "unset" the "destination" variable right before I redirected the user:
unset($_REQUEST['destination']);
drupal_goto('somewhere_completely_different');
Using this method, I ensure that the redirect was "clean" and there wasn't any possibility of any misdirection.
Trackback URL for this post:
More Quicktips
No comments
Glad I found this!
Mike, you told me to try the goto function to redirect to a view page, and it just wouldn't work. But I could tell it was not returing to after the goto call, so I knew something was fishy. Adding the unset did the trick!