I've implemented ErrorReporting as described in the 'third way' and deployed behind mod_wsgi and it all works for me. Are you sure you've enabled the base class in prod.cfg with 'error_catcher.on = True'?
On Thu, Apr 10, 2008 at 7:06 PM, vandevel <[EMAIL PROTECTED]> wrote: > > My turbogears 1.0.4.4 project is deployed behind mod_wsgi 1.3 and it > seems that mod_wsgi causes the application to function in a manner > that differs from executing the app with bare cherrypy. > > Specifically, the application implements a custom error/404 handler > for display of customized pages as per these instructions: > > Method 3: Application-wide Catch-all with CherryPy Filter - > http://docs.turbogears.org/1.0/ErrorReporting#id3 > > The error handler works beautifully, however, when the application is > deployed behind mod_wsgi it appears that the > _cp_on_http_error method of the root controller is not being executed > and therefore the default cherrypy stacktrace is displayed rather than > the custom page. > > any advice would be appreciated! > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
