Dizkus

hahahha.. i didn't think about a user in multiple groups.. hahaha.. yeah, that'll cause some issues :)

2) yes, below function head() in header.php

3) yes, actually.. change it to:

..it'll take some playing with, but the majority of what you'll need is here .. hope it works out for you :)

--
http://www.invalidresponse.com

ok, so the end result: it works! mostly.

• 
  
• [*:73b174a96a]I can't get the "test" group to show. it shows the "Users" group theme am i on crack and missing the obvious? (my best-case-scenerio would have four groups)
  
• [*:73b174a96a]upon login, it shows the theme of the previous login for the index.php- it will correct it self if you click through on a link, but that initial page, it based on whoever was previously logged in. I had a Konqueror window open- logged in admin; opened firefox, logged in as a user, and the index was in the Admins group theme. the reverse worked the same. if the user was logged in first, the admin's initial index was
  

how would unregistered users be handled? by the default theme set in the administration>settings field?

This does sound like an interesting and useful feature. For a generic solution the requirement would be that the existing API - pnUserGetTheme - returns the theme based on the group membership. If this isn't the case then any solution would only be considered a hack given that the existing API would return the wrong value.

A potential avenue to explore would be adding a field to the existing groups table for the theme. The pnUserGetTheme API should check this value. I'd work with the .8x groups module since it's API compliant and add extraction of this field to the getall and get module API's. Make the results of these API static to prevent extra SQL calls.

-Mark

..it's definitely a hack.. one that needs a good, long bathing ..but, the basics are there to be toiled with. we'll leave the credit to Not_Public ;) ..I just connected the dots haphazardly.

--
http://www.invalidresponse.com

Devin

It wasn't a criticism of you at all (don't take it that way if it came across as such) but this is something i'd like to see end up as a feature that can be added to core code. However in order for this to be possible it needs to be done 'right'.

-Mark

ARRRGGGHHH!
//stabs himself in the eye with a pencil repeatedly//
"Damn you case sensitivity! damn you lack of caffiene and sleep!"

guess what my problem was?

now to figure out a way to avoid users from seeing their theme change after their intital log in...

THANK YOU IR!

as to the credit- I don't want no stinking credit.. just happy to be slowly learning what pushing these button thingys can do. not to mention.. uh.. well- I obviously didn't _do_ anything.. :wink: again, thank you IR

as to what Mark mentioned.. *whoosh* right over my head... but it sounds like this type of function may be accomplished in a less "hackish" way in .8? maybe something that would survive an upgrade to .9? ( I know this won't.. but I'm taking notes!)

..no offense taken ;) ..none at all, I knew it was dirty before posting it, even hesitated due to that fact.. as for adding the feature to the core (a 'cleaner' version :) ).. I suppose some might find use in it.

you're welcome Not_Public.. ;)

--
http://www.invalidresponse.com