On Mon, Jul 12, 2010 at 5:32 PM, Guyren G Howe <[email protected]> wrote:
> 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).
First, make sure it's working with other URLs. Does "/admin" work?
Then, create a route and action containing only "raise RuntimeError".
That should bring up the interactive traceback, to make sure it works.
"Not Found" can mean several things: no route matched, controller
missing, action missing. In the latter two cases, I'd expect the
interactive traceback when in debug mode though.
Lines 16 and 20 overlap: a resource route "/incidents" and a regular
route "/incidents". It should match the first one. It's surprising
it's not matching either one. That suggests something strange is
happening, like maybe this route map isn't even being used. Have you
asked on the TurboGears list? They may be better at diagnosing it. I
haven't used recent versions of TurboGears.
You could try commenting out line 18 ("/evidences"). It's probably not
the problem, but it's the most unusual route..
--
Mike Orr <[email protected]>
--
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.
