On May 20, 6:41 am, Karen Tracey <kmtra...@gmail.com> wrote:
> On Wed, May 20, 2009 at 7:28 AM, Konstantin S <ktechli...@gmail.com> wrote:
>
> > On 20 май, 14:02, Konstantin S <ktechli...@gmail.com> wrote:
> > > Hello!
>
> > > I have a very strange problem and really don't know where to start in
> > > hunting it down. My app uses django-registration, all works fine but
> > > if I been logged in restart django dev. server I immediately get
> > > TemplateSyntaxError:
>
> > > Caught an exception while rendering: Reverse for
> > > 'myapp.add_media_action' with arguments '()' and keyword arguments
> > > '{}' not found.
>
> > > It seems like after restarting django couldn't resolve url's names. I
> > > know this is a very vague and incomplete description but may be it is
> > > a very well known problem that you can identify on the spot ?
>
> > I've tried it in a django shell. 'myapp.add_media_action' really does
> > not resolve, but 'add_media_action' resolves fine. That makes it even
> > more puzzling. Why am I getting 'myapp.add_media_action' instead of
> > 'add_media_action' ?
>
> That's a misleading message. The code tries to reverse the requested name
> with the project name prepended only after attempting to reverse the
> requested name on its own has failed. See:
>
> http://code.djangoproject.com/browser/django/trunk/django/template/de...
>
> That code was recently (r10350, on April 1st) fixed so that the original
> NoReverseMatch is raised instead of the one resulting from the last-ditch
> attempt to find a reversal.
>
> So, ignore the 'myapp' part of the message. The real issue is that your
> server can't reverse 'add_media_action', even though you can reverse it from
> the shell. There's got to be some difference between your server
> environment and the shell environment you are using that is causing that.
>
Konstantin,
To elaborate on Karen's suggestion, one way to see which URLs are
among the candidates for resolving the reverse match is to
deliberately hit a bad URL like the following:
http://localhost:8000/something_that_does_not_match_urls
If you have appropriate debug settings, you should then get back a
list of all the patterns that django knows about in your browser. If
you don't see the URL for add_media_action, then you probably have
some issue with the environment, as Karen suggests.
If you do see the URL for add_media_action, then you probably want to
focus on other theories, such as the wrong number of arguments or
something similar.
Obviously, more information would help people help you figure this
out. At the very least you should provide the line of code from
urls.py that establishes the mapping for add_media_action.
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
