While Domain Theme settings which are supplied by a Domain's configured theme *do* correctly "stick" with the domain for which they are set, Domain Theme settings which are supplied in a theme by a base theme seem to apply to all Domains, effectively overwriting any other domain's theme settings.

I discovered this while developing a theme based on Omega. Omega provides settings for responsive break points and max page widths, etc. It was these Omega base-provided settings which would not stick for each domain, while settings provided by the sub-theme would. I tested Garland and behold, all Domain Theme settings applied only and completely to each Domain. I tried another custom developed theme based on AdaptiveTheme, and I realized its sub-theme provided settings stuck while theme settings supplied by the base AdaptiveTheme continued to apply to all Domains.

Happy to provide more info / testing / help -- just wanted to get some comments going...

I'm using the most recent commit (5574d0f) from Domain Access 7.x-3.x.

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Postponed (maintainer needs more info)

Are you allowed to configure the base theme per domain as well?

steveoliver’s picture

steveoliver commented

If I understand, you're asking: Do Domain Theme settings stick when configuring only the base theme ...rather than sub-theme(s) per domain?

In fact, I just tried this with Omega base and it seems the answer is No; using only the base theme per domain still applies all settings of that base theme to all implementing domains...

It seems I should dig into the theme's on this issue.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (works as designed)