Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.we don't use domain_id=0 in the way this module intended it to be used.
patch will prevent user from going to domain_id=0
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | domain-867934.patch | 1.73 KB | mikeytown2 |
Comments
Comment #1
mikeytown2 commentedComment #2
agentrickardIt's fairly clear that this is a follow-up from #867868: node/add/* goes to primary domain if user's domains includes domain_id:0. But it's not clear why this patch is necessary.
Comment #3
mikeytown2 commentedThis isn't necessary; its me hacking this module to get it working exactly how I would like it to. In short, being good about following the GPL. If this is something your interested in including, I can work on a more formal patch.
Comment #4
agentrickardOK. Bumping to 7.x.
Comment #5
agentrickardComment #6
dqdI'll close this issue due to inactivity for 14 years and there is upcoming EOL of Drupal 7 in January 2025. While the project's version for Drupal 7 will surely keep providing support for security issues and website breaking bug fixes for Drupal 7, we should try to minimize the open issues for Drupal 7 in the queue as much as possible. A big thanks around for the report and all the efforts in here. Feel free to re-open if you can provide a fix or found an additional related problem which increases the issue priority.