Re: I'm afraid 0.16.2 is broken (or I am :- ) )

Hi,

First of all, thanks a lot for the quick fixes!!! Both this and the 
logout problem.
I'm currently staying with 0.15.1 because I'm in the middle of some 
development, I don't want to interrupt with an LU update.

When the fixes are released in the next release I will give it a try again.

I don't have any problem with the changes done to the getProperty. I 
will probably have some impact on my code, but that's OK. Does this also 
leave out the alias part in the config?
What is the reason for using the aliases anyway? "Obscuring" the 
database fields??

regards,

Tim

Tim Daeleman wrote:

 >> Hi,
 >>
 >> OK, I give up!!
 >>
 >> I started up from scratch again to see what I was doing wrong since
 >> updating from 0.15.1 to 0.16.2. I build the most basic login system 
with
 >> my (custom field) needs, but the result was still the same behaviour.
 >>
 >> But apparantly the strange behaviour I encountered is also present in
 >> the examples, even example 1!!!
 >> I extended example 1 with 1 custom field (name) in the xml file and as
 >> follows in the config:


Ok .. this should be fixed in CVS.

note however that there were BC breaks in the process.

in getProperty() you will now need to use the unaliased keys as defined
in the storage layer.

so this means

$LU->getProperty('handle') // may remain as is
$LU->getProperty('lastlogin') // used to be 'lastLogin'
$LU->getProperty('is_active') // used to be 'isActive'
$LU->getProperty('perm_user_id') // used to be 'permUserId'
$LU->getProperty('perm_type') // used to be 'userType'
$LU->getProperty('group_ids') // used to be 'groupIds'

etc.

Therefore it might be a good idea to make the next release 0.17.0 ..
and push the caching stuff into 0.18.0 ..

opinions?

regards,
Lukas