extended version of taxonomy_theme

Extended version to also apply the correct theme even on paths
of node/1234 format assigned to a term/vocabulary :)

New version that applies on pathes of
- taxonomy_menu/x
- taxonomy/term/x
- node/x
now. Condition to use:
You want theme selection based on the current vocabulary.

Renamed taxonomy_menu_theme to taxonomy_vocab_theme.
Because it changes theme based on current vocabulary and its
no longer dependent on taxonomy_menu.
Also made a minor correction to make it compatible with PHP4.

Have fun, Thilo

@igrcic
Sorry. I should have noticed ... you need to have taxonomy_context installed
to have themes change with taxonomy/term/x pathes using my module.
(I will look at it again. Shouldnt be too hard to have it work without it.)

@jvandyk
... change the variable names in the new module to avoid conflicts.
You are right, I completely missed that point. Its just because I startet to modify
the module and in the end I got a complete new one.
... we try to avoid forking modules, but rather submit patches to existing modules
As I said above, I tried to modify only. But I realized that the existing module takes
different approach on theme selection. I'm not sure the modules should be merged.
The original one uses terms in a "selector" vocab, but my module chooses the
themes to apply based on the vocabs itself. What means every vocab can have a
different theme, but not the terms in it. I think the two points of view are not
compatible to be integrated in one module. What do you think? You will see that
nearly the whole module code has changed somehow. Of course the basic structure
is still the same. I will modify the variable names to avoid conflicts. We can talk about
combining the codes, of course.

Sorry. It was not my intention to displace the existing module in some way.
I just thought some people need what I needed and find vocab_theme useful.

Thilo

Maybe both modules could be merged. And the user decided via radio box or
what selection method he wants. Or with two check boxes what methods to
be active. In principle both methods can be activated at once, but I cant see
what for.
If a node is in a ThemaA vocab but has a term for ThemeB applied also,
what theme should be selected by the module? Possible solution:
- give priority to one method
- uses default theme in case of conflict
- ???

New version available.
I merged the two variations of theme.module. The user can select now which method
he/she needs or prefers. I also updated the original taxonomy_theme code to support
taxonomy/term/x pathes and my code to support it without taxonomy_context being
enabled. The new module should support
- taxonomy_menu/x
- taxonomy/term/x
- node/x
for both (term- and vocabulary-based) selection methods.

Feedback is welcome. Hope you like it.

Thilo

Seems like I published the wrong version :( Sorry.
So this is the right one ... I hope ...

Updated again to allow selection of all installed themes instead of
enabled ones only as requested in http://drupal.org/node/40643.

Updated again to assign themes to forums (http://drupal.org/node/45741).
Hope all options are (still) working, because of many code changes.

Hi igrcic!

I dont understand what you need the additional modification for!? In case you want
to assign different themes to different "sections" (vocabularies) of your site, you can
use vocab-based selection. Whenever you need more detailed configuration you can
create a vocab "themes" and add a term for every theme. On your pages you can
assign one term to apply a specific theme and one term for your navigation. I think
your "or ALL terms in ALL categories" mod is someway redundant to term-based
selection. For your forums you can individually choose themes anyway.

What point do I miss? What specified use does your idea assign to?

Of course, I can agree to your proposal and integrate it with taxonomy_module,
but I think we should discuss its use for other users before.

Thilo

my users dont have to have an option to select a theme also

Last night I had some time and thought over it again. And it doesnt hurt to have an extra
"ALL terms in ALL categories" option. Because I have no better idea how to call it I chose
"all taxonomy" title for this option. I also grouped the different parts of module settings
with form_group (very nice idea ;) ) and optimized some parts of the code.
I think this module will be available on the project page in a few days.
I'm also working on a 4.7 version. Of course, the groups will be collapsible in that version.

and i always append an erroneous attachment :(

Yes, I already have a working 4.7 version of taxonomy_theme. But I'm still waiting
for my cvs account to add the new version to repository. I hope to get it the next
days, so that I can take maintainance for taxonomy_theme. You are welcome to
test the module from attachment by now.

Again I found some bugs in the posted code. So please try this version instead.
The zip archive contains taxonomy_theme for Drupal 4.6 AND 4.7.

All modifications of the extended taxonomy_theme module have been
committed to cvs and are included in the latest 4.6 and 4.7 releases.