Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hi, sorry for my English googletranslate :)
I installed the module subdomain and encountered an error specified in the title.
The fact is that to check the variable $cookie_domain, going line by line reading of settings.php and enter $cookie_domain search in the resulting array.
In settings.php comment present
* between your various domains. Make sure to always start the $cookie_domain
that satisfies the search condition, and is transmitted in parts quality of the argument to the function eval(), this results in an error.
It might be easier to get a value of $cookie_doman, declaring it to the global scope:
global $cookie_domain;
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | subdomain-use_global_for_settings_php-1366682-6.patch | 3.57 KB | agrozyme |
Comments
Comment #1
Ser_Mir commentedThe fast way to fix the error (if you need to use module right now) before the developers release a new version of the module - change line 453 in includes/subdomain.admin.inc
before:
after:
Comment #2
stewart.adam commentedAttached patch makes subdomain read $cookie_domain from the global variable, as per Andruxa's recommendation.
Comment #3
inventlogic commentedthe method used to obtain the $cookie_domain setting from the settings.php file is to parse the whole file. This means it snags the first occurrence of the $cookie_domain within the file which is mentioned at least twice with default settings. If you place your own $cookie_domain= '.yoursite.com' at the end of the file. The $cookie_domain value that is grabbed is the first occurrence which is not your domain names value.
You can edit the settings.php and change all occurrences of $cookie_domain to something like $cokie_domain. leave the $cookie_domain = '.yoursite.com' as the only one.
Or apply the patch above to check the $cookie_domain from the global variables
Comment #4
lovelykaushik86 commentedThanks @Ser_Mir for solution
Comment #5
agrozyme commentedremake patch
Comment #6
agrozyme commentedComment #7
agrozyme commentedwhen path is empty, use original_path replace path.
Comment #8
agrozyme commentedAdd support the "Content: Has taxonomy term ID (with depth)" which is contextual filter of view.
Comment #9
honza pobořil commentedCan anybody else confirm if the patch #8 works?
Comment #11
honza pobořil commentedI adapted your patch to newest dev version and commited it.
Could anybody confirm the newest dev fixes errors reported here? I did not tested it in term mode.
Comment #12
honza pobořil commented