I have two domains, kozub.in.ua as #1 (default) and personal.kozub.in.ua as #3. Domain Configuration is enabled, while Domain Settings module is disabled. I can put my domains into maintenance mode via admin/structure/domain/view/1/config and admin/structure/domain/view/3/config, respectively. I.e., when I check "Put site into maintenance mode" and save settings at admin/structure/domain/view/1/config works and puts my default domain (domain #1) into maintenance mode. However, there at admin/structure/domain/view/1/config I see this warning message: "This is your default domain. Use of this form is discouraged. Set these values through the standard interface". What does it mean? If it means (as I suspect) that I should use admin/config/development/maintenance, then I have to say that "Put site into maintenance mode" checkbox unchecks on its own every time I try to check it and save settings. So, admin/structure/domain/view/1/config is the only form where I can put my default domain (#1) into maintenance mode; why then does it say "Use of this form is discouraged"?..
Comments
Comment #1
Maksym Kozub commentedComment #2
Maksym Kozub commentedComment #3
agentrickardUse of the form is discouraged for the very trap you have found yourself in.
If you use the Domain Conf form to save values for your default domain, you break the normal Drupal forms.
The easiest way to back out of this is to clear the Domain Conf settings for the default domain. (See admin/structure/domain/batch/domain_conf).
What is happening is that the values saved in {domain_conf} are overriding the expected values saved in the {variable} table.
Comment #4
Maksym Kozub commentedHmm. First of all, many thanks for your advice. It works :). I must say, however, that as far as I remember, the very reason I started using the form at admin/structure/domain/view/1/config was being unable to put #1 into the maintenance mode via admin/config/development/maintenance. (That said, now I cannot guarantee this was the case.)
In any case, this is not a very intuitive idea, to be honest. I treat my two domains as quite the same level (of course, not from the DNS perspective, since one of them is a subdomain of the other), and I would prefer to have no default domain at all, and to fully manage these two via admin/.../1/... and admin/.../3/..., respectively, maybe even killing the "general" form at admin/config/development/maintenance.