In the doc. for zopeproject, it says:

Note: Even exceptions such as Unauthorized (which normally leads to a
login screen) or NotFound   (which normally leads to an HTTP 404
response) will trigger the debugger.

Is there a workaround, so that I can run "bin/paster server
debug.ini" on an application that requires a login (ie: starts out by
issuing an Unauthorized exception), or is removing the zcml decls
that causes the login challenge to be issued, the only way to debug
such an app?

You can start the application with deploy.ini, log in to obtain credentials, and then restart the application using debug.ini.

http://worldcookery.com -- Professional Zope documentation and training

Zope3-users mailing list

Reply via email to