you misconfigured the LDAP settings. this is not a zope error, it is emitted by the LDAPUserFolder (which takes it from the python-ldap module). since the user folder is consulted on any access to its container you will get this error until you fix the settings. try logging in as the emergency user and reconfigure the LDAPUserFolder. test your settings as the emergency user by looking at the Groups tab (do you see any groups?) and search for user records on the users tab (does it find any?). i would be interested in the full traceback traceback you are currently getting. the user folder is misbehaving slightly. instead of raising the exception it should really just not authenticate the user and hand authentication off to the next user folder up. if you can give me that traceback i can fix this problem for the next release. jens On Sunday, Aug 25, 2002, at 13:33 US/Eastern, Patrick Price wrote:
I added an ldpauserfolder as a subfolder and got an error:
Zope has encountered an error while publishing this resource.
Error Type: NO_SUCH_OBJECT Error Value: {'desc': 'No such object', 'info': ''}
yet it was created anyway. Now when I try to open the folder that this folder is contained in by clicking its parent foldername in the ZMI, I cannot see my other folders, just this error.
The "Delete" and other ZMI buttons don't appear so I cannot delete this folder.
-Patrick Price