#17012 closed Bug (fixed)
Documentation references non-existent hasNoProfanity validator
Reported by: | Russell Keith-Magee | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.3 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | yes |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description (last modified by )
The documentation for the PROFANITIES_LIST setting makes a reference to the hasNoProfanities validator.
This validator hasn't existed since Django 0.96, so this reference should be cleaned up.
Credit for the report goes to robinne on the django-users mailing list.
Change History (6)
comment:1 by , 13 years ago
Description: | modified (diff) |
---|
comment:2 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 13 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
I think there is a typo in the fix [16935]:
It should read "... will be forbidden in comments when COMMENTS_ALLOW_PROFANITIES is False." (not True).
Also, I don't think COMMENTS_ALLOW_PROFANITIES is documented.
comment:4 by , 13 years ago
Good catch. It's a rather counter intuitive to set something to False
to activate a behavior and to True
do to nothing :(
And yes, I noticed that COMMENTS_ALLOW_PROFANITIES
isn't documented. The "profanities" feature is kept for backwards compatibility but it isn't encouraged (see #8794). I'd rather deprecate it (and its settings) than document it.
comment:6 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
In [16935]: