John Pedersen wrote at 2003-7-23 14:44 -0700:
... I've got about a hundred site members and I've had three instances now where for some as yet undetermined reason, something in a user's account becomes corrupted and they can no longer log in. When this happens, each time the user goes to log in, a stack trace is created. Apparently this happens after the user password is compared to what Zope knows, because changing the user password through the management interface will instead cause the expected password failure page to be rendered. ... RuntimeError ... * Module Products.PageTemplates.PageTemplate, line 95, in pt_render <FSPageTemplate at /Plone/folder_listing used for /Plone/Members/lvoss/Favorites> ... * Module Products.PageTemplates.TALES, line 217, in evaluate Line 184, Column 24 Expression: standard:'folder' ... * Module Products.PageTemplates.PageTemplate, line 95, in pt_render <FSPageTemplate at /Plone/folder_listing used for /Plone/Members/lvoss/Favorites> ... * Module Products.PageTemplates.TALES, line 217, in evaluate Line 184, Column 24 Expression: standard:'folder' ...
RuntimeError: maximum recursion depth exceeded (Also, an error occurred while attempting to render the standard error message.)
This is not a corrupted user information. It's a standard endless recursion broken by Python's "maximal recursion depth". Somehow, the evaluation of "folder" in "folder_listing" for "/Plone/Members/lvoss/Favorites" results in calling itself. Look at ".../lvoss/Favorites". It probably contains an object with a dangerous id, maybe "folder" or "folder_listing". If not obvious, tell us what you see there (after you asked user "lvoss" for permission). Dieter