[ZPatterns] loginmanager and zope 2.6.1

Andi Zeidler andi@elfrie.de
Thu, 21 Aug 2003 02:06:46 +0200


hi everyone,

i'm writing since i've run into a strange problem with loginmanager and
zpatterns.  i've already asked tyler sarna, who has referred me to this
list, so here it goes...

i'm in the middle of a web site transition from an old zope version
(2.3.0) to a more recent one (2.6.1) in order to be able to use cmf and
plone.  a specific area of the site uses your loginmanager product to
handle two different kinds of user sources.  the user's data is stored
in a mysql database and retrieved from there by a 'UserSource' instance
using a zclass inheriting from 'LoginUser' for storage.  the object is
'loaded by accessing attribute'.

so far everything works fine in zope 2.3.0.  for example, i can call
/acl_users/UserSource/getItem?key=testuser, which will return the correct
user object with member data from the database.

as for zope 2.6.1 i get nothing at all, even after starting it with a
fresh copy of the Data.fs working for 2.3.0.  from a debugging session
it seems that 'getItem', 'retrieveItem' and '_RawItem' (inherited from
Rack) are called normally and set up an empty object of the desired
zclass.  but accessing the attribute stored in 'loadAttrib' (in
'if hasattr(item.aq_base, a): return item' or directly by getattr)
doesn't trigger a call of __get_attr__ in the DataSkin class inherited
by 'LoginUser' inherited by the zclass.

this of course has the consequence that the SkinScript method which
retrieves the member data from mysql doesn't get called (which is
obvious by the missing query in the mysql log file as well), which in
turn causes the user validation to fail.

i've also tried to use 'LoginUser' directly as the storage class, but
with no success.  so after a couple of hours playing and debugging i'm
pretty much stuck at this point now, so i hope that maybe one of you
has some piece of advise for me... :)

thanks for your time,


andi

-- 
life's a bummer
when you're a hummer...