|
Friday 29 May 2009 6:13:17 am
Hi Douglas, I hear you. Yes, the login handler only covers the loginUser function, which you can see from kernel/user/login how the correct class is loaded. You have a few options in order to keep maintenance low. You could copy the ezuser datatype into an extension but that is a high maintenance approach. I would patch ezusertype, specifically the function 'objectAttributeContent' which loads the ezuser object. Instead you could check for your new class and use that instead. That should force the correct object to be used, and therefore the right 'store' method. Patching, if done properly, is a perfectly acceptable technique for modifying the kernel. It should be very easy to maintain this patch. It depends. I can't see the ezusertype::objectAttributeContent method changing much in the future... Paul
eZ Systems
|