Hi all,
I'm referring to this thread from a couple of months ago:
http://groups.google.com/group/django-users/browse_frm/thread/1f4bb991f9f0f7b5?hl=en&tvc=1
I'm still having problems with the NoReverseMatch exception coming up
with seemingly-random behavior.. or at least inexplicable to me.
Everything works just fine with django's dev server. With other server
arrangements, the exception shows up.
It doesn't show up always. Viewing an url might go on just fine for 10
times in a row, then boom. Someone in the thread above suggested that
the url tag might be getting wrong args, but:
1) i tried reloading a page without changing _any_ value, just hitting
F5: if there was an error in the code it would never work, but
sometimes it does.
2) it works fine with the dev server
So, I think I've been bitten by a nasty bug (could be either in my
code or in the reverse() or {% url %} implementation). And it only
gets triggered using "production" servers, which is very bad. I tested
apache2+mod_python, nginx+fcgi ad lighttpd+fcgi.
You can see a traceback at http://dpaste.com/86124/
(it doesn't just happen with the 'tn-user' url, but also with other
named urls).
Please I really need help with this, my deadline is approaching and I
don't know where to start in debugging this.
Other possibly relevant info:
- I'm using named urls
- I use reverse or the url tag all over the place, i don't want to
have any static url in the code or the templates
Thank you for your help.
Alberto
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
