Caching is often the culprit in these situations. Disable it and recheck. Obviously clear cookies and history in the browser as well.
Also, verify that your database shows the correct data state (meaning that the fields in the database show as checked) once the models are saved, either through the Django shell or directly interrogating the database.
Your web server process is least likely to be the culprit, unless it is telling the browser to use the cached version of your page for some reason.
-James
--
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...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5e28d66a-58a2-4f66-b77e-1a0898ae45b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
In that case you should post up the relevant model, view, and form code. You may not be instantiating the form correctly.
Are you manually rendering it?
-James
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3bbdba86-5e05-4c5d-9c24-be48d324f377%40googlegroups.com.
Awesome. Glad to help.
As an aside, if your function is expecting a list of integers, I would also validate the code in the caller is actually doing what it is supposed to. You may have a use case where either longs or ints may be passed in, but something smells fishy in the code leading up to calling your render function if you're receiving unexpected data types.
Of course that may be expected behavior, so you may be just fine as is.
Just a thought.
-James
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/007338f4-3337-4823-9519-8ef4e0e11ed0%40googlegroups.com.