Closed (won't fix)
Project:
Domain
Version:
6.x-2.0-rc8
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
9 Apr 2009 at 17:40 UTC
Updated:
5 Aug 2011 at 18:27 UTC
If you edit the present domains subdomain or delete the present domain conditionally redirect the user to the primary domain after performing the operation if we cant determine that the new subdomain is a functional one, in which case redirect to it.
Comments
Comment #1
michaelfavia commentedLearn to type
Comment #2
agentrickardFor the reason we do this now, see issues like #429278: Sudomain and 404 Not Found. Not sure there is a graceful way to fix this.
Also note that batch operations typically must be performed from the primary domain, so we would need to address that as well.
Comment #3
michaelfavia commentedi would plan on refactoring batch and singular operations like drupal does with nod_load_multiple and node_load both functions remain with signatures intact but all logic offshored to the more complex one with simple arguments thrown in to it. Please see code referenced for details. We can also check for the presence of a signature that this install provides and actually ensure the DNS is setup before me let the site be marked active or something if wed prefer to go that route. Then you can create the items in advance and only enable them when it works.
Comment #4
agentrickardThat isn't really the issue, I don't think. The problem is that we need to pull some default values from the main domain -- and the easy way to do that is from the main domain.
But I think the new domain_set_domain() may fix that for us.
Comment #5
agentrickardThis is a nice-to-have but not critical improvement.
Comment #6
agentrickard