Web server - show/hide details Not working yet
HTTP request to http://subdomain-test.it-werx.org/subdomain/test returned the following result:
HTTP_HOST:
QUERY_STRING:
REQUEST_URI:
SCRIPT_FILENAME:
drupal_get_normal_path:
Your web server is not routing subdomains to your Drupal directory.
Possible Solutions:
If you're running Apache, confirm you have the wildcard directive, ServerAlias *.it-werx.org, in the VirtualHost declaration in your Apache configuration
Confirm there are no rogue URL rewrite rules in your Apache configuration or .htaccess file
I can ashure you that all the apache side of things are indeed correct...
Also with phpinfo(); everything is fine...
http://www.it-werx.org/info.php?a=1&b=2&c=3
Comments
Comment #1
aboen commentedSame Error with me when update to drupal 6.17 but working fine with drupal 6.16
Comment #2
isopharius commentedsame issue on upgrade to drupal 6.17
Comment #3
nitebreedSame here... rolled back to 6.16 and everything is working fine.
Comment #4
rastarr commentedI had an aweful experience installing this module and my issue related to Drupal v6.17 and the settings.php file - in particular the cookie setting.
After a lot of head scratching, I stumbled upon a line in the readme of 6.17 which made it all work.
=============================
Incompatible changes
Drupal 6.17 introduces the following incompatible changes.
Session handling
Drupal 6.17 changes the way session cookies are handled. Most people don't need to have this setting set, but if you have an explicit $cookie_domain set in settings.php, verify that it is set to a sensible value:
'example.com' if you want sessions to apply to the example.com domain, and none of its sub-domains (especially not www.example.com),
'www.example.com' if you want sessions to apply to the www.example.com domain, and none of its sub-domains nor parent domains (especially not example.com),
'.example.com' if you want sessions to apply to the example.com domain and all its subdomains (www.example.com, mydomain.example.com, etc.).
=============================
Once I changed my settings.php cookie line to the following, it all worked:
$cookie_domain = '.geekandjock.com';
Note the preceding '.' to the domain name
Comment #5
antoniopironti commentedSame issue. As reported in the preceding comment, we have just to set $cookie_domain with the '.' prefix. It works for me too.
Comment #6
vincenzo commentedThis might not be a bug with the Subdomain module, to be honest.
The way cookies are handled has changed from Drupal 6.16 to 6.17 (http://drupal.org/drupal-6.17). Till 6.16 (included), when a $cookie_domain wasn't specified, it was assumed to be your domain, e.g. "example.com", then automatically set to ".example.com" when setting cookies, as per RFC2109 (http://www.ietf.org/rfc/rfc2109.txt). This behaviour has changed in D6.17, where you should set $cookie_domain to
If you don't set the variable explicitly, then it'll be still assumed to be "example.com", but cookies will no longer be set with the leading dot as it used to be.
In plain words, my understanding is that if you use this module, you must also set your $cookie_domain to '.yourdomain.com'.
The module could probably still do this transparently on behalf of the developers, but I will personally leave this out in the open so that developers are aware of what is going on.
Comment #7
antoniopironti commentedI agree with vincenzo: i think this is not a subdomain bug. In any case an install note in the readme is needed, imho.
Comment #8
mefisto75 commentedPLease, help) 6.2 beta1
I tried all possible variations in settings.php with "." without " " with www without www. etc
Still tells me that $cookie_domain is not set correctly.
finally set it back to # $cookie_domain - "example.com"; and uninstalled the module.
Would love to have an option for registered users to have user.example.com type of subdomain.
Maybe with other than this module means?