My setup: Drupal 7.22 / PHP 5.3 / IIS 7.5 / SQL Server 2008
My issue:
When I log in with the admin user (user 1) account, I get redirected to the home page without a problem here: http://SERVERNAME/drupal/welcome.
When I log in with a regular user's account that I've created for testing and content creation, I get redirected to a blank "white screen of death" page here: http://SERVERNAME/welcome?destination=node/2.
And when I refresh that same page, then I can see the home page properly.
I also tried the suggestion on this post of un-commenting the "RewriteBase /drupal" in the .htaccess file without success.
This strange behavior happens for me with Firefox20 and IE9, and I've tried it on the User login block as well as the User login page at http://SERVERNAME/drupal/user/login with the same result.
This is what I see on the Recent log messages/DBLOG report:
Type user
Date Friday, April 26, 2013 - 13:48
User jayhawkfan75
Location http://SERVERNAME/drupal/welcome?destination=node/2
Referrer http://SERVERNAME/drupal/
Message Session opened for jayhawkfan75.
Severity notice
Hostname 172.16.1.111
Operations I'm stumped as to what the issue could be. Any suggestions would be very welcome.
Comments
Comment #1
katannshaw commentedNo replies so far...bummer. I'll keep working on a solution for myself in the meantime.
I just created a rule for a specific role to redirect to the welcome page at http://SERVERNAME/drupal/welcome upon logging in. But even though the rule is set to override the system's own redirect, that user account still gets redirected to the same page with a blank view at http://SERVERNAME/drupal/welcome?destination=node/2.
I'll keep on truckin', but any ideas would be great.
Comment #2
longwaveThis is unlikely to be a bug in Drupal core. What module did you use to perform the redirect on login? Have you followed the white screen of death instructions at http://drupal.org/node/158043 to show "invisible" errors?
Comment #3
katannshaw commentedThanks for replying and the clarification on the category.
I used the Rules module to do this, and I checked the "Force redirect" checkbox.
Yes, that was my first stop. Sorry that I didn't mention that in the original post. Here's what I experienced concerning the "Invisible" Errors section on that page:
Upon my research, I've also found an article at http://stackoverflow.com/questions/703230/drupal-nodedestination-not-wor... that made me look at what other modules could be causing the problem (perhaps the LDAP module). But with be selecting "Force redirect" on the rule, shouldn't that overwrite any other redirect from core or another module?
Thanks for your assistance.
Comment #4
pfrenssenUnfortunately it is out of scope for this issue queue to help you set up your development environment. The PHP error messages are vital to be able to figure out what is going wrong, so get it set up and report the actual error message.
You are also using contributed modules such as Rules so what you are experiencing is probably not a problem in Drupal Core but in one of the other modules or in your particular configuration. You should try to figure out which module is causing the problem and move this issue to that module's issue queue. That will make sure it ends up with the right people.
Comment #5
katannshaw commented@pfrenssen: Thanks for the reply. I will continue researching the issue and report here what I find it to be.
Comment #6
katannshaw commentedThis ended up being an issue with the LDAP module version that I was using at the time (7.x-1.0-beta12). Once I uninstalled it and installed 7.x-2.0-beta5, the rule worked fine, and this issue went away. Thanks for the reply pfrenssen.