There's an open ticket currently regarding custom error messages in newforms: http://code.djangoproject.com/ticket/3457
I currently have an ugly hack in place that gives me an error_message= parameter for the field types I use, but, it's ugly, and doesn't work entirely. I'm working on getting a real patch done for this, but have some questions/roadblocks. How do we want to handle field types that have multiple error messages? For instance, IntegerField has a "max" message, "min" message, and "required" error message. I don't really like the idea of three named parameters max_error_message, min_error_message, error_message, but I can't seem to come up with any easier solutions. One of the comments on the thread brings up a point that error_message= could be a single error message and we put it on the coders to write their error messages as, "You must enter a number between 3 and 10." instead of splitting it into "Please enter a number", "Please enter a number greater than or equal to 3", and "Please enter a number no more than 10". Thoughts? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
