[PEAK] peak.web bugs
Phillip J. Eby
pje at telecommunity.com
Thu Dec 4 19:02:11 EST 2003
At 05:30 PM 12/4/03 +0100, Radek Kanovsky wrote:
> Status: 500 The engines can't take any more, Jim!
> Content-Length: 0
> X-Powered-By: Zope (www.zope.org), Python (www.python.org)
>
> Traceback (most recent call last):
> File "/www/wm4/wm4.cgi", line 106, in ?
> publisher.runCGI(sys.stdin, sys.stdout, sys.stderr, os.environ)
> File "./publish.py", line 432, in runCGI
> File "./zope/publisher/publish.py", line 146, in publish
> File "./publish.py", line 266, in handleException
> File "./errors.py", line 71, in handleException
> File "./errors.py", line 50, in renderingContext
I figured out what caused this, and checked in a fix. Basically, if a
WebException (such as NotFound or NotAllowed) is raised at the application
root, the WebException breaks when trying to create a rendering context to
display itself in. I fixed it by expanding the ITraversalContext interface
to support doing what 'WebException.renderingContext()' was trying to do.
Please let me know if you're able to get things up and running now. Thanks.
More information about the PEAK
mailing list