Re: CSRF Token: is it okay if it is attached to my url when I enter my form?

Thank you Collin and Thundebabzy, you identified the problem I think. When I call the form for the first time it is called the wrong way. I will fix this! Am Freitag, 3. Oktober 2014 16:57:23 UTC+2 schrieb Collin Anderson: > > However you would have that behavior when you are submitting a form

Re: Views triggering twice

Malcom, Thank you for this writeup you did on debugging HTML code. I was also showing Django Views loading twice, and it was due to an empty "href". Only took a few minutes to fix after reading your writeup. Thanks On Friday, November 14, 2008 5:52:15 PM UTC-8, Malcolm Tredinnick wrote: > >

Re: crispy form wouldn't show form level errors

I have tried that in my fom_invalid method it has valid messages but crispy firm is not picking it up. But if I just try to print them in template it is empty so it's getting reset between fom_invalid and template rendering? Subodh On Oct 4, 2014 10:18 AM, "Collin Anderson" wrote: > try this if

Re: crispy form wouldn't show form level errors

try this if you haven't: {{ form.non_field_errors }} -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this g

Re: buttons do something

The simple way is to use before your . The other option is to submit the data by hand using javascript. I also recommend checking out templates, if you haven't looked at them: https://docs.djangoproject.com/en/1.7/intro/tutorial03/#write-views-that-actually-do-something -- You received this m

Re: help with idea

If you change how your dictionary is formatted, it can be much easier: dicc_one = { 'string1': {'fieldsFK__total_one__gt': 0}, 'string2': {'fieldsFK__total_two__gt': 0}, 'string3': {'fieldsFK__total_three__gt': 0}, 'string4': {'fieldsFK__total_four__gt': 0}, } results = {} for k, v

Re: Upgrading Django (to 1.7)

Stodge, Part II focuses on migrations, and deals in passing with AppConfig objects via data-migrations. Part III will take a closer look at the app registry, as we will create a custom AppConfig objects for `roundtable`. There is a (very) short section in Part III about import problems caused by

Re: Upgrading Django (to 1.7)

Carsten, Thank you for reading and for the positive feedback! Andrew -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com.

crispy form wouldn't show form level errors

I have a form that clearly form level errors (not field level) I can print those error messages in my form_invalid method. But they are not showing up when using crispy form. I have set following options self.helper.form_error_title = "Form Errors" self.helper.form_show_errors =