For some reason, when not using a Views-generated page (e.g. viewing a node detail page), the site-wide default theme gets applied, instead of the custom theme for the virtual site.
By default, the Virtual Site Theme module executes after the system module. Since the Virtual Site Theme module sets the $custom_theme global var that is used by init_theme() to dictate which theme gets applied.

To address this, I adjusted the weights of all Virtual Sites modules to execute before the System module-- e.g. changed them to -1 instead of 0.

Comments

KathyIce’s picture

craigmc - thanks for the fix

Changing the weights on the modules also helped us... It not only took care of a display problem on the user side of our site, but also made it so that our chosen admin theme worked on the virtual site host... (myvirtualsite.com) ... we're using the condition that fires based on the host URL.)

Good module... it's nice not to have to worry re: which tables are shared or not shared, just to have a site with multiple "faces".

andrewtf’s picture

Priority: Normal » Critical

Hmm. I'm having this exact same issue with non-views-generated pages with my Virtual Site setup. Changing the module weights (via the Utility module) unfortunately not only didn't solve the problem for me, but somehow broke the path to the virtual site home pages (their URLs redirected back to the default front page).

Changing the weights back to 0 for all VS modules fixed the home page problem, but I'm still stuck with the default theme on most of my pages.

FWIW the admin theme is doing what its supposed to do.

Update: I tried setting the module weight to -1 again. This time it seems to have done the trick with switching the theme on all pages, but it still breaks Virtual Site's default front page function. Trying to reach default front pages for either of the two virtual sites I've set up just sends me back to the site's main front page. I'm using a Zen sub-theme, if that makes a difference in the situation.

AdamPS’s picture

Issue summary: View changes
Status: Active » Closed (cannot reproduce)

Tidy up: closing very old bug report - cannot reproduce without more information and presumably is no longer relevant to the raiser. Please re-open if desired.