#django

At first I thought it was that there's no handler404, but that doesn't appear to be the case because when I implemented one, it didn't change anything.

Or that it was using a default handler404 which hit one

*hit a template

Oh wait, it's in handle_uncaught_exception... so I'd need a handler500

check your 500.html template

yup

also, i recommend to make your error templates dead stupid

Yeah, it looks like there was an error when trying to handle a 500

preferably, just static html

Ah, we have other middleware which assumes there will be a logout view

Yeah, I think our normal 500 error page is pretty dumb, but I'm taking a number of shortcuts in my tests

so it doesn't surprise me that I broke something

Awesome, that was it. Thanks for your help!

o/

\o

\o/

Sup #django

hi, I have a simple modelForm and if I print(form.errors) I can see the validation error messages. However, if I try render this in the template, with {{ form.errors }} or {{ form.non_field_errors }} it shows nothing about errors, just like these variables don't exist. What's wrong?

fellipe: Maybe "form" is not in your template context?

schinckel: hi! take a look: https://dpaste.de/iEVT

schinckel: it is in the context for sure

Yeah, but it's called "profile_form"

Also, I'm not sure why you are doing the recreate of the profile_form after saving: generally you'll want to redirect after a successful POST (otherwise you are likely to have a user accidentally hit REFRESH and submit again)

schinckel: yeah, I just said "form" to abbreviate the question here. But as you can see, either the view and template are using profile_form

When you re-bind the profile form, that means it's a new instance of the form, without the data (and thus without the errors)

Your view should be much simpler than that.

schinckel: you are right about the successfull post. I will change it.

schinckel: oh, I did not think about the rebind form problem.. let me fix it now

Something like https://dpaste.de/2Bz6#L should be more helpful.

Indeed, that's close enough to an UpdateView, that I'd probably just use that (and override the get_object() method)

schinckel: right.. I am reading your paste...

schinckel: I want if the request method is GET, the profile is created with just the emailfield prefilled, since it is the username

You don't want to "create" something (in the database sense) on a GET, you want to prefill it: if that's the case, then you may want to set the form.initial using that.

schinckel: right. that's it

schinckel: thanks a lot. solved!

A question for people who use Django with Conda.

Under what circumstances would you get symlinks for conda's bin/activate, bin/conda, and bin/deactivate installed directly in your django project directory?

Anyone in Australia ever used LinkMarket Services?

hey, so i need to have form fields be hyphenated for field names: so I created form fields using an __init__ constructor, self.fields['field-with-dash-name'] -- the form itself works fine, but I can't reliably use it in a template - can't refer to it like 'form.field-with-dash-name'. Is there a way to just override the rendered field name when I submit a form post?