Re: setAdminContainers changed to what ?

It looks like some major changes happened in the login method, ive gone 
through and debugged where the problem was.

  if (!$perm->mapUser($auth->getProperty('auth_user_id'), 
$containerName)) {
                         $this->dispatcher->post($this, 
'onFailedMapping');
                     } else {
                         $this->_perm =& $perm;
                     }

Should it not be a call to errrorstack then i would have known what the 
problem was, should i setup a callback method for this then ? I think 
this should be calling error stack however is perm containers optional 
?

My issue was the perm container stored in the db is DB_Local and the 
one in the config is DB that was it !

On 27/01/2006, at 11:28 AM, Dan Rossi wrote:

> Sorry to bug you, what about my issue with the perm container not 
> loading properly ? Any check for groups or rules is failing, because 
> the information is simply not there.
>
> On 26/01/2006, at 8:04 AM, Lukas Kahwe Smith wrote:
>
>> Dan Rossi wrote:
>>> Just to confirm, init() needs to be called before doing anything 
>>> with logout or i got the session destroy error.
>>
>> yes .. calling init() is the first thing you do after you create the 
>> instance.
>>
>> regards,
>> Lukas
>>
>>
>> _______________________________________________
>> LiveUser mailing list
>> [email protected]
>> http://mailman.21st-hq.de/mailman/listinfo/liveuser
>>
>
>
> _______________________________________________
> LiveUser mailing list
> [email protected]
> http://mailman.21st-hq.de/mailman/listinfo/liveuser
>