By hardieas on

Am doing a multisite setup. I want one particular site, e.g. blah, to have a customised version of a particular theme but also want to have the original un-customised version of the same theme available to all the other sites.
So, I put the theme in /sites/all/themes and in sites/blah/themes. Problem is, Drupal defaults to using the version of the theme in /sites/all/themes not the one in /sites/blah/themes.
This, to me, seems counter-intuitive. Surely the correct behaviour would be to give priority to the themes in the site-specific themes directory, not to the themes directory for all sites, precisely so that you can customise a single site? It also seems somewhat to defeat the advantages of multisite if the only way to do what I want is to copy the unmodified theme directory to each and every one of all the other site-specific theme directories and remove it from sites/sll/themes...

⋅ Categories: Drupal 5.x

Comments

Island Usurper’s picture

Island Usurper commented

I would try renaming the custom theme to something else. While I agree that theme name conflicts should be resolved by specificity rules, I don't know that enforcing this in the code is feasible. Could look to find out, I guess.... The only thing that distinguishes one theme from another is the name of the directory that contains it. That's easy enough to change. Plus you get the added benefit of choosing between the stock or custom theme on the "blah" site.

-----
Übercart -- One cart to rule them all.

hardieas’s picture

hardieas commented

Actually, it does seem to work as expected, after all, with the site-specific theme over-riding the general one.
Once again, it turned out to be a cache persistence problem.

Isn't it about time that a cache clear feature was provided as a core facility instead of having to do magic incatations like re-saving the modules/views/whatever page or running a bit of hand-crafted PHP code somehow/somewhere or expecting non-technical users to grapple with phpMyAdmin/etc?

Or, can't Drupal have a smart "cache check" feature (like AxKit) that checks to see if the cache contents is older that the content sources it is holding the generated copy of?

Also helpful would be a way of having it automatically disabled when in admin pages, for example...