Monday, June 20, 2011

Re: Possible bug in form validation

On Mon, Jun 20, 2011 at 1:49 PM, Shawn Milochik <shawn@milochik.com> wrote:
I know that, whenever someone finds a "bug" in Django they're usually doing something incorrectly. Hopefully someone will point out what I need to do to make this work.

I don't know if it's considered 'correct' or not, but the max_value constructor parameter is only used at instantiation time, to add a validator to the field.

You can easily add the validator manually in your own constructor if you need to. You may also want to set the max_value attribute, if you use it elsewhere, but it is not used internally by the form machinery.
 

However, this is looking like a legitimate bug to me.

http://dpaste.com/hold/556603/


I've updated with a working example, as http://dpaste.com/hold/556805/

--
Regards,
Ian Clelland
<clelland@gmail.com>

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

No comments:

Post a Comment