I am not sure if this is a bug-report. At least it seems to be impossible to set up domain specific settings running Domain Access and i18n together in one Drupal 7.2 installation. As far as I can think of how it all works, it may could probably be a unsolvable conflict between the detection mechanisms of domain access domains and its aliases and the URL detection from Drupal localize needed for i18n on the other hand? Or am I wrong?

Finally I still wonder that I don't see the typical domain specific settings options from Domain Access module below the Language settings options under admin/config/regional/language/edit/ when I try to specify a certain domain for url-detection. Is this something I missunderstand or is this still a missing feature for domain access.

Any hint would be much appreciated. Please let me know if you need more information. I am not sure if my describtion is good enough understandable.

Comments

agentrickard’s picture

Category: bug » support
Issue tags: -i18n, -domain access, -compatibility, -language settings

The Domain Settings module only works for forms that use system_settings_submit(). Any form that requires more complex logic is ignored and requires custom handling.

Domain Conf allows for domain-specific default language handling.

[Removing unwanted tags, see http://drupal.org/node/1023102]

agentrickard’s picture

Status: Active » Closed (works as designed)
Crouchie’s picture

Hi Digidog,

One year after your post, I have the same Problem. So, have you solved it or rather how did you solve it?

Kind regards
Crouchie