Mailing List Archive

SQL, LoginManager and SkinScript.
I have been having a problem I cannot get around with Zope 2.4.0,
Python 2.1.1, LoginManager (latest), ZPatterns (p2) and a SQL
database. I followed the instructions I found on zope.org and all of
the SQL methods work as expected. However when I change storage to
"Objects are loaded by accessing attribute ______" and set it to the
field in both the database and the skinscript called 'login'. I
throws the following traceback.

Traceback (innermost last):
File D:\PROGRA~1\zope_dev\lib\python\ZPublisher\Publish.py, line
223, in publish_module
File D:\PROGRA~1\zope_dev\lib\python\ZPublisher\Publish.py, line
187, in publish
File D:\PROGRA~1\zope_dev\lib\python\Zope\__init__.py, line 226, in
zpublisher_exception_hook
(Object: LockableItem)
File D:\PROGRA~1\zope_dev\lib\python\ZPublisher\Publish.py, line
162, in publish
File D:\PROGRA~1\zope_dev\lib\python\ZPublisher\BaseRequest.py, line
447, in traverse
File
D:\PROGRA~1\zope_dev\lib\python\Products\LoginManager\LoginManager.py,
line 237, in validate
(Object: ProviderContainer)
File
D:\PROGRA~1\zope_dev\lib\python\Products\LoginManager\LoginMethods.py,
line 243, in findLogin
(Object: PlugInBase)
File
D:\PROGRA~1\zope_dev\lib\python\Products\LoginManager\LoginManager.py,
line 194, in getItem
(Object: ProviderContainer)
File D:\PROGRA~1\zope_dev\lib\python\Products\ZPatterns\Rack.py,
line 59, in getItem
(Object: ProviderContainer)
File D:\PROGRA~1\zope_dev\lib\python\Products\ZPatterns\Rack.py,
line 96, in retrieveItem
(Object: ProviderContainer)
File D:\PROGRA~1\zope_dev\lib\python\Products\ZPatterns\Rack.py,
line 235, in _RawItem
(Object: ProviderContainer)
File D:\PROGRA~1\zope_dev\lib\python\OFS\CopySupport.py, line 481,
in _setId
(Object: LockableItem)
File
D:\PROGRA~1\zope_dev\lib\python\Products\ZPatterns\DataSkins.py, line
254, in __set_attr__
(Object: LockableItem)
File
D:\PROGRA~1\zope_dev\lib\python\Products\ZPatterns\DataSkins.py, line
240, in _canonicalForm
(Object: LockableItem)
KeyError: _v_parent

And reports a KeyError... Any thoughts?


--
Jeffrey Hulten
SCT Consulting