On Fri, Oct 7, 2011 at 10:18 AM, robinne <develo...@computer-shoppe.net> wrote: > I've finally managed to get a basic validator to work on a model (I > used validate_slug on a model field and was able to catch it as a > ValidationError). After getting that to work I tried to then get the > validator that I actually want to work, hasNoProfanities. I have found > that the validator no longer exists. I think the Django 1.3 docs need > to be updated but before I request that I wanted to be sure that this > is the case. This is from the docs: > > > https://docs.djangoproject.com/en/1.3/ref/settings/ > > PROFANITIES_LIST > > Default: () (Empty tuple) > > A tuple of profanities, as strings, that will trigger a validation > error when the hasNoProfanities validator is called. > > > I guess you have to basically handle this on your own now, is that > true?
It's been true for some. The hasNoProfanities validator hasn't existed since Django 0.96. In Django 1.3, we emptied the PROFANITIES_LIST because of the Scunthorpe problem; see the release notes [1] for more details. So - you've found a flaw in the documentation (a reference to a validator that hasn't existed for a long time). I've logged this as ticket #17012 [2]. Thanks for the report! [1] https://docs.djangoproject.com/en/1.3/releases/1.3/#no-more-naughty-words [2] https://code.djangoproject.com/ticket/17012 Yours, Russ Magee %-) -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
