HELP exUserFolder went bezerk?
Help, exUserFolder worked like charm yesterday, but suddenly today it does not let authenticate. Traceback follows. What is really strange, If I put the acl_users/redirectToLogin on url, I get to the login screen. Somehow it seems like exUserFolder or Zope suddenly stopped understanding each other and the refresh never comes to browser. HELP! -huima <TABLE BORDER="0" WIDTH="100%"> <TR VALIGN="TOP"> <TD WIDTH="10%" ALIGN="CENTER"> </TD> <TD WIDTH="90%"> <H2>Site Error</H2> <P>An error was encountered while publishing this resource. </P> <P><STRONG>LoginRequired</STRONG></P> Sorry, a site error occurred.<p> <!-- Traceback (innermost last): File /var/zope/lib/python/ZPublisher/Publish.py, line 150, in publish_module File /var/zope/lib/python/ZPublisher/Publish.py, line 114, in publish File /var/zope/lib/python/Zope/__init__.py, line 159, in zpublisher_exception_hook (Object: nokiastories) File /var/zope/lib/python/ZPublisher/Publish.py, line 89, in publish File /var/zope/lib/python/ZPublisher/BaseRequest.py, line 388, in traverse File /var/zope/Products/exUserFolder/exUserFolder.py, line 1010, in validate (Object: acl_users) File /var/zope/Products/exUserFolder/exUserFolder.py, line 916, in cookie_validate (Object: acl_users) LoginRequired: <HTML> <HEAD> <TITLE>Logging In</TITLE> <META HTTP-EQUIV=Expires CONTENT="2002-07-31"> <META HTTP-EQUIV=Refresh CONTENT="0; URL=acl_users/redirectToLogin?destination=https://thesithewhereishouldlogin"> </HEAD> <BODY> </BODY></HTML>
Heimo Laukkanen wrote:
Help,
exUserFolder worked like charm yesterday, but suddenly today it does not let authenticate. Traceback follows.
What is really strange, If I put the acl_users/redirectToLogin on url, I get to the login screen. Somehow it seems like exUserFolder or Zope suddenly stopped understanding each other and the refresh never comes to browser.
Even more stange behaviour. exUserFodler works on another virtual host, where is used cookied based authentication - but it is not https-conenction. I checked Apache-configs and rewrites for both are same - so there shouldn't be the problem. Any help? -huima
On Thursday 01 August 2002 16:31, Heimo Laukkanen wrote:
Help,
exUserFolder worked like charm yesterday, but suddenly today it does not let authenticate. Traceback follows.
What is really strange, If I put the acl_users/redirectToLogin on url, I get to the login screen. Somehow it seems like exUserFolder or Zope suddenly stopped understanding each other and the refresh never comes to browser.
HELP!
i had this once, when i did something to standard_error_message. just trap error_type = 'Login Required', and you should be ok. hth
-huima
<TABLE BORDER="0" WIDTH="100%"> <TR VALIGN="TOP">
<TD WIDTH="10%" ALIGN="CENTER"> </TD>
<TD WIDTH="90%"> <H2>Site Error</H2> <P>An error was encountered while publishing this resource. </P> <P><STRONG>LoginRequired</STRONG></P> Sorry, a site error occurred.<p> <!-- Traceback (innermost last): File /var/zope/lib/python/ZPublisher/Publish.py, line 150, in publish_module File /var/zope/lib/python/ZPublisher/Publish.py, line 114, in publish File /var/zope/lib/python/Zope/__init__.py, line 159, in zpublisher_exception_hook (Object: nokiastories) File /var/zope/lib/python/ZPublisher/Publish.py, line 89, in publish File /var/zope/lib/python/ZPublisher/BaseRequest.py, line 388, in traverse File /var/zope/Products/exUserFolder/exUserFolder.py, line 1010, in validate (Object: acl_users) File /var/zope/Products/exUserFolder/exUserFolder.py, line 916, in cookie_validate (Object: acl_users) LoginRequired: <HTML> <HEAD> <TITLE>Logging In</TITLE> <META HTTP-EQUIV=Expires CONTENT="2002-07-31"> <META HTTP-EQUIV=Refresh CONTENT="0; URL=acl_users/redirectToLogin?destination=https://thesithewhereishouldlogin "> </HEAD> <BODY> </BODY></HTML>
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- http://www.kedai.com.my/ http://www.kedai.com.my/eZine http://www.zope.org/Members/kedai http://www.my-zope.org use Zope? you got HOPE
Bakhtiar A Hamid wrote:
i had this once, when i did something to standard_error_message. just trap error_type = 'Login Required', and you should be ok.
Ah! That did it and now it works again. Thanks. What confused me before was the fact that I had a standard_error_message in the other host - and that made the exUserFolder work there. I copied the basic standard_error_message to the root again and now everything is back to normal. Possibly this should be added to FAQ or other documents of exUserFolder, since eventhough I've been using exUSerFolder for a long time now. I did not know or understand to look for the problems in standard_error_message! Live and learn, live and learn. In any case. Thanks for the help. Once again Zope community showed how helpfull and fast it can be in good situations, thanks ,-) -huima
participants (2)
-
Bakhtiar A Hamid -
Heimo Laukkanen