On Tue, Sep 16, 2008 at 7:38 AM, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > No, it's not an entirely different issue. It's just a case of one error > inadvertently hiding another one. Your URLConf *must* be completely > valid for reversing to work, since all of the patterns are processed > before any reversing is applied (there's a pre-processing caching step). > > If you are referring to an invalid view in your URLConf, you must fix > that before proceeding (commenting out the line would be a reasonable > start).
Ah, well then, that was apparently the problem. My URLConf was referring to the users.login file. The users.login file was referring to the LoginForm I created. The LoginForm I created had a "next" field, initialized (using initial=xxx) to a urlresolvers.reverse() lookup. This fails during the processing of the URLConf, with a "ViewDoesNotExist" error getting thrown. SUBSEQUENT calls do not fail, because (I assume) the urlresolver call completes. But it's too late then, because the urlresolvers function does not retry the failed lookup. Is there any way to set the server to spit out an error if the urlresolver step fails? Knowing a function was blowing up during initialization would have saved me about 10 frustrating hours playing with urlresolver syntax and template code, especially since the problem wasn't a "TemplateSyntaxError" at all. It might also help if the urlresolvers kept a list of what views it failed to initialize, so if you hit one it could tell you the lookup worked, but the subsequent connection to the view didn't. -- Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
