Fellow Drupallers:
At our last meeting this past Tuesday I discussed an issue I'm having trying to establish a staging site. While the site works as expected there is so far one-hitch: When attempting to login (the login in the upper right corner of the header) the login prompt screen is displayed and when the submit button is clicked it appears the login process is working but I am redirected back to the LIVE site. The urls are different (www.* vs staging.*). I've been able to trace the page-front.tpl.php that delivers the loginbox but I have been unable to determine where control is going from there.
I've set the cookie_domain in my settings.php file(s) to the corresponding site urls to no avail.
I've also been able to dump the contents of the $conf array (all 68 pages of output) and I'm in the process of searching through it. But preliminary searches show no references to the main site. Everything look 'relative' in regards to paths. The only other item that might be unusual is that we authenticate with ldap.
I thought I would post this progress (or lack thereof) so if anyone had any ideas they would post them to this discussion. I hope someone, somewhere has seen this before and can advise?
Thanks - Bob
Comments
Never with the log in. Some
Never with the log in.
Some questions.
Is this domain access by any chance? Is it a single site or multisite?
Did you flush your browser cache and cookies along with the site.
Also you can just dump the database and search for a reference to the live site with a text editor.
Thanks Tommy; I did manage to
Thanks Tommy;
I did manage to circumvent the redirect issue with a little suggestion from Al Nutile: I disabled both the ldap_integration and securepages modules on the staging site and now I can log in without the redirect. OK for now.
But, here are my answer to your Q's:
Yes it is domain access. Setup as multisite (non-default) but separate drupal directory
Yes - and now I receive two errors:
1) exhausted available memory on mysql-whatever (I've got 128M defined in both etc/php5 and php5/cli dirs.
2) drush now gives me a segmentation fault error
Yes - did that. I used sed to scan for variations on the occurrence of the domain site (i.e.: https:www.sitename.com)
and replace them with a simple single '/' to make them relative to the current webroot. Got nothing but WSOD (but I assume this is due to the php failure about memory).
So, any additional advice form anyone greatly appreciated. Thanks - Bob