Is there a way to support multiple, unique themes with this module? My use-case is that I'm using Domain Access to provide per-domain themes, with different users administering their own domains. I'm using a unique instance of a custom theme for each domain, with the idea that different users can recolor their own sites independently of one another. The problem is that a single CSS override file is being created by Theme Hues, which affects all themes.
I could get around some of this by creating unique selectors which don't overlap (#site-a, #site-b), but then all the selectors would be visible to any of the domain admins. The optimal solution would be to have a unique page of settings per theme (just like Blocks are configured per theme).
Is this possible, or likely to be supported in future versions? Thanks!
Comments
Comment #1
aacraig commentedI have a multi-domain system set up as well with the same use case. It's the reason Theme Hues was born, actually.
In my setup, I have a different database and files/ directory for each user, though they all use the same theme in a multi-site setup. In this way, each user gets their own stylesheet in their own files/ folder.
Could you give me a detailed description of your configuration?
Comment #2
ongdesign commentedThanks for responding so quickly!
Mine is a multi-domain, shared database setup, using Domain Access to provide 13 different neighborhood assns. with their own independent sites (the database is shared to make it easy to aggregate calendar events and some other shared content across pages). Each neighborhood will have a different logo, and some minor differences to their themes, although they are using very similar templates; and each one wants to recolor their themes. Only site administrators would be able to recolor, and their choices would apply to all public and authenticated users (i.e., everyone sees each particular site in the same color, but each site uses a unique color scheme). It's not a per-user color scheme -- it's a per-site color scheme.
So my plan is to create a separate instance of the master theme for each, so they can have a few minor changes, and also so each site admin can recolor their own site using Theme Hues. I would be equally happy to use a single theme for all the associations, however, and selectively turn on/off some of the design features in PHP.
Think this is feasible? Thanks again!
Comment #3
aacraig commentedI'm still unclear on your architecture.
Is your multi-site system set up so that each site has it's own files folder or do they all use the same one?
Theme Hues should create a separate css file for each site if they all use their own files folder. If they have the same one, I'll have to look at modifying Theme Hues to cover this use case.
Comment #4
ongdesign commentedUsing Domain Access and a single database, there doesn't seem to be any way to have discrete file directories per domain -- they all share a single directory at sites/default/files. There was a feature in an earlier release to have per-domain file system paths, but it looks like that was removed: http://drupal.org/node/197692
This also seems relevant:
http://drupal.org/node/393000
Thanks again -- I know this isn't part of the basic functionality for Theme Hues!
Comment #5
aacraig commentedI'll add this to the road map, though, as it would certainly be useful.
Comment #6
ongdesign commentedIt would be great if this use-case could be supported soon! I have a client really clamoring for this functionality (again, using Domain Access). Thanks for all your work on this module!
Comment #7
aacraig commentedThat sounds like a nice extension of Theme Hues functionality. I'll add it to the roadmap.
Comment #8
aacraig commentedComment #9
1websitedesigner commentedHi aacraig,
Any update on this?
I'm in a similar position where multiple sites will share a central database and I would like each site owner to be able to choose unique characteristics for their own themes.
Thanks for your work on this!
Martin
Comment #10
aacraig commentedThis has been addded in Theme Hues 2, currently available on the project page.