Matt's assistance with the implementation of views_slideshow was a great help at last night's meeting. Boy, are the pages different from Drupal v5.x! Here is a follow up that hopefully someone can recommend places to look that would cause this issue:
We have multiple Drupal directories and separate databases for each instance. But this issue concerns our live vs staging site. Last night we were making changes to the front page views in the staging site. Personally I kept verifying that the URL consistently referenced the staging instance. Yet, when I arrived this morning I was immediately barraged with Q's about "what happened to our front page?". It appears that the mods being made, although the URL stated staging, were applied to the LIVE site. OK - it was easy to correct because we use blocks on the front page and I simply reactivated the live one.
But then, I went back into the staging site, reapplied the changes, checking everything in between, and they STILL were applied to the live site.
The first thing I checked was my settings.php file in the staging site and it defines the staging components as it should. Then I dumped my staging database to a flat sql file and grep'ed for hard coded references... there were none. Then I checked my site information page in Drupal and it too was coded as staging. Sooooo, can anyone suggest another area I can look or adjust to determine why this is occurring? FWIW, when I was doing the same with a staging site under v5.x I had no such issues. It is a 6.x issue? I think not!
Advice anyone? Thanks
Comments
Weird...
Whats strange is that we were updating the site from my laptop, so there is no chance that some old Prod sessions were sticking around.
Jim had something like this happen to him locally, where his local site was named close to prod and once and awhile it was switching to Prod. Could possibly be something similar happening here. Very strange though, but I can't think of anything at the moment.
What are the names of your
What are the names of your $cookie_domains in the settings.php for staging v. prod (or is it commented out)?
The reason I ask is that I'd been trying to do a multisite using shared codebase for 2 separate subdomains, separate database tables for almost everything but users, which were shared with the users table from the "master" site's db (per directions I found in a drupal.org page, can't recall url right now) and to set the $cookie_domain to '.localhost' (in my case) - i.e., the dot domain name... setting that cookie_domain allowed the users authenticated on mastersite.localhost to be already authenticated on secondarysite.localhost.
Wondering if something odd like that affected you last night...
BTW, I've already installed & played with OpenPublic & would love to show that off next go 'round.
Thanks all for the
Thanks all for the suggestions. I believe it turned out to be a slightly mis-configured apache virtual server that was redirecting all the access via port 443 to the live server. Oh Well.... I believe its corrected now.