If that's your complete view, you've forgotten to return an HTTPResponse object.
Since action='.', it appears that you are using the same view to get the form and to post (which is fine), but each case must return a response for the prowser, presumably rendered from the same template. The render_to_response() shortcut is your friend here. Also, while not required, it is usual for a successful post to actually return a redirect to a separate success view (helps guard, I believe, against inadvertent double submits). On 3/5/12, Tom Evans <tevans...@googlemail.com> wrote: > On Mon, Mar 5, 2012 at 3:24 PM, leaks <tonykyriaki...@gmail.com> wrote: >> no, no errors get displayed... Just nothing happens. > > Absolutely and literally 'nothing happens'? Really? > > Does the browser submit the form, django receive a request and render > a response? I would definitely class that as 'something' and not > 'nothing'. > > We can only help you if you help us. You need to explain precisely > what happens, and what you expected to happen. Saying 'nothing > happens' is nonsense, and perhaps if you had investigated what was > actually happening, you may have understood why it didn't happen as > you expected, rather than expecting us to magically deduce both things > from the ether. > > Cheers > > Tom > > -- > 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. > > -- 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.
