On Wed, Jul 7, 2010 at 3:37 PM, DrunkenMonk <[email protected]> wrote:
>
>> No, with toolmapping, you won't need to change the login forms. That's
>> the beauty of it.
>
> I had missed the toolmapping completely, that should work fine, thank
> you.
Great!
> The ingroup function only reads system variables for the current user,
> not checks refering to other id's.
> It needs to be remapped for the 2 variable version.
We could change it, but from the help info:
I SUPPOSE WE SHOULD BE ABLE TO SPECIFY A USER... CAN DO [IF INLIST ID
GROUP.NAME] EASILY ENOUGH HOWEVER
Will that work? For that matter we should be able to add this first
line to the beginning of ingroup:
function BOLTCingroup($args='') {
## CHECKS IF CURRENT USER IS IN A GROUP. PARAMETER GROUP(POS1) IS
GROUP NAME. CAN ONLY CHECK CURRENT USER. I SUPPOSE WE SHOULD BE ABLE
TO SPECIFY A USER... CAN DO [IF INLIST ID GROUP.NAME] EASILY ENOUGH
HOWEVER
if (isset($args[2])) return BOLTCinlist(Array($args[2],
'group.'.$args[1])); // Add this line...
if (! is_array($args)) return false;
if (isset($args['group'])) $group = $args['group'];
else $group = $args[1];
return BOLTingroup($group, $args['id']);
}
Can you test that and see if it works ok? Won't catch superadmins
though... I'm out of town for the weekend. If it works ok I can add
to the core for the next release...
Hey, did you try [if ingroup group=whatever id=whoever]. It looks like
it ought to be set up for this already!
Cheers,
Dan
--
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en.
