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 got reports of odd behavior after we upgraded them to DA 6.x-2.2. They have several sites, and most editors are only permitted to edit content on the sites they are assigned to. We're using the Domain Source module to assign content to particular sites, though some content is being listed by Views across several sites. The problem is that whenever content is created from one of the child sites, the user is being redirected to the main site. The created nodes appear to be correctly assigned to the child domain using Domain Source, so I don't see any plausible reason why this redirection should be happening.
It seems that, at one time, users were also getting 401 errors after being redirected to the main domain (apparently because they didn't have permission to create content at that domain?), but, suddenly, I can't replicate that behavior (while masquerading as a lower-privileged user), so perhaps some knob I twiddled has corrected that part of the problem…?
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | domain-compat.patch | 674 bytes | Garrett Albright |
Comments
Comment #1
agentrickardThere are all kinds of modules that mess with redirection after node save. We try to correct for this using a session token and domain_node_save_redirect().
However, if your sites do not share a common TLD (and thus do not share a common login cookie), it is very possible that some other module is issuing the redirect. And the session handling doesn't help, because sessions are not shared across TLDs.
There is no way to prevent this.
See, for instance, the discussion here #683400: ImageField Tokens causes redirect to main domain on node save
401 errors would never be issued by DA, which would issue either 403 or 404, so that indicates a server-level issue.
Comment #2
Garrett Albright commentedYou're right, it was another module. Trial and error found that the Signup module was the culprit, so I'll move it to their queue. (There hasn't been a release of Signup since last September, though… Wow, were we that far behind in our updates?) Unfortunately, Signup is rather vital to this site…
Signup folks, any clues? I'll try upgrading to the most recent dev release…
(By 401, I probably meant 403.)
Comment #3
agentrickardSee also a recent patch posted to #683400: ImageField Tokens causes redirect to main domain on node save.
Comment #4
Garrett Albright commentedThat patch had no effect, I'm afraid.
EDIT: No noticeable effect with regards to this problem, I mean.
Comment #5
Garrett Albright commentedOkay, the client wants me to get back on fixing this, so I did some experimentation… In includes/node_form.inc, in signup_save_node(), commenting out the node_load() line makes the problem go away. But that doesn't make any sense. I thought that maybe the node_load() cache was caching the node when it shouldn't be, but even if I go out of the way to make that node not cached (by adding a $revision parameter to node_load()) and clearing the cache immediately after the node_load() call (by adding node_load(FALSE, NULL, TRUE); right after, and even hacking node_load() itself to disable the cache), the problem still occurs. This is weird…
Comment #6
Garrett Albright commentedOkay, well, here's this. Does it totally break the Signup module? Well, it tries not to. It fixes the problem, at least.