Posted by matt2000 on June 6, 2008 at 2:58am
Jump to:
| Project: | CiviCRM Theme |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | matt2000 |
| Status: | closed (duplicate) |
Issue Summary
The attached patch adds a third theme selection for civicrm pages which the user defines as 'public.'
This allows, for example, CiviEvent pages to display in the default theme, but still use an alternate theme for managing contacts.
| Attachment | Size |
|---|---|
| civicrm_theme.module.patch | 1.95 KB |
Comments
#1
Weird... I checked the issue queue before writing this, and the other two patches related to this issue didn't show up. So, I guess users have multiple approaches to pick from.
#2
One quick question...
How would I add a second one of these options? We'd like CiviEvents public pages to have one theme, CiviMember/CiviContribute pages to have another theme. Basically it's the same theme, the header just changes.
I think I see how you changed the module, but I want to make sure.
I think it would be good in the future to give us the ability to set a theme for each of the sections (CiviEvent, CiviContribute, etc.).
#3
jsimonis,
You might be served by
http://drupal.org/project/taxonomy_theme
Despite it's name, that module can also be used to set theme based on path. No need for the taxonomy component at all, if you don't want it.
#4
I'm marking this as a duplicate of #804804: CiviCRM backend should use admin theme as it makes more sense to automatically determine what's public based on Civi's configuration.
#5
I disagree. I think it makes more sense to let users decide which paths are public or not. For example, some sites use profiles as public directories, other use profiles as data entry tools for sub-admins. So it depends on the site.
This is a valid feature request that does not necessarily overlap with #804804: CiviCRM backend should use admin theme. I'll be rolling a version for 6.x shortly.
#6
OK, I just read the patch on #804804 and I see that it's doing more than the issue described, so maybe this is a duplicate. But it can still be argued that it's better to use the drupal convention (lists of paths) for designating a Drupal feature (the theme).
I will investigate further, and see if the other patch is sufficient, and report back.
#7
Fixed as part of http://drupal.org/node/804804