CiviCRM Community Forums (archive)

Your screenshots don't all include URLs - but from the URLs I can see, I think I see the issue.

In that first screenshot, you're on "navysailing.org" - but the link you're hovering over is a link to "www.navysailing.org".  In Drupal, logging in on mysite.org does NOT log you in on www.mysite.org.

There's a number of ways to handle this - it could be a matter of mismatched base URLs between Drupal/Civi, or a number of other issues - in my experience, the best way to make sure this never happens is to edit Drupal's settings.php in the section that allows you to redirect all non-www URLS to www or vice versa.

Huh! That was pretty good, Jon! 

I learn something new everyday! :-)

This has a twist that's worth mentioning.

First, I tried inputting www.navysailing.org directly into the browser URL field. And everything worked as it should have, i.e. the browser held the address as www.navysailing.org all the time.

Next I went to the settings.php and searched for 'redirect'.  On my setttings.php that was around 400, but I have some views crud in there, so searching for "redirect" brought me to this slug of code:

/**
 * Drupal automatically generates a unique session cookie name for each site
 * based on its full domain name. If you have multiple domains pointing at the
 * same Drupal site, you can either redirect them all to a single domain (see
 * comment in .htaccess), or uncomment the line below and specify their shared
 * base domain. Doing so assures that users remain logged in as they cross
 * between your various domains. Make sure to always start the $cookie_domain
 * with a leading dot, as per RFC 2109.
 */
# $cookie_domain = '.example.com';


I un-commented the "$cookie_domain = '.example.com'; and replaced it with $cookie_domain = '.navysailing.org'

That didn't work ... so I replaced it with
$cookie_domain = 'www.navysailing.org'

That didn't work.

Sooooooooo .... I went to the .htaccess and fixed it by uncommenting the redirect to a non-www to a www. (around line 85ish)

That fixed the problem, BUT I don't like making these kind of changes to the .htaccess, because of the upgrades will trample on .htaccess thus eliminating the fix.  I don't like having to remember to deal with that upon  upgrade.

So, looking at my settings.php change to the $cookie_domain ... could I have made a mistake interpreting the the directions to fix the problem in the settings.php?  (which I much prefer to changing the .htaccess).

Sorry for the verbosity! 

Carl

Jon!

You 'Da Man!

Thanks for the quick responses. This has quickly solved what could have been a really nasty problem!

Onward!

Carl