With some help from you folks (thanks!), I've got some more logging happening. So now I can tell I'm failing because the router is choosing the root controller, way at the bottom of my routes file, rather than the restful route that's right at the top.
So here is my routes file: <http://pylonshq.com/pasties/cd546ef11d0d3a436cece0d16e2e72a5> When I try to hit /incidents, it goes through the authentication stuff, then decides that the right controller is root, which naturally fails. This then produces a simple 404 error in the browser (no fancy backtrace debugger — which is very cool, but I don't think it would help much here, even if I could get it to display). Here is my middleware file: <http://pylonshq.com/pasties/ff95848af8197d4ac4bda7111182f3e1> This is TurboGears 2.1. Is there some equivalent to script/console from Rails here, that might let me look at what the router is doing? -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
