Project

General

Profile

Actions

Feature proposal #3880

closed

Bad word filtering

Added by krileon over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
22 January 2013
Due date:
% Done:

100%

Estimated time:

Description

Implement bad word filtering for frontend text for the following.

Category Description
Group Description
Wall Post
Event Details
Photo Description
File Description
Video Caption

This should be a global parameter to apply to all of the above locations (or others as found necessary). It should simply parse a comma separated list of words and remove them in favor of a custom censor text (simply remove by default).

Actions #1

Updated by krileon over 9 years ago

  • Tracker changed from Bug to Feature proposal
Actions #2

Updated by krileon over 9 years ago

  • % Done changed from 0 to 10

Implement a textarea field where you supply a filter per line then separate the word and its replacement with =. Example as follows.

jerk=hero
idiot=genius
stupid=smart

The above word on the left is not case sensitive so it'll match no matter what odd casing the user supplies. Left and right sides of filtering will both be passed through CBTxt for translation so you can use language strings as well.

Actions #3

Updated by krileon over 9 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 10 to 100

Word filtering implemented for all locations that allow user text to be supplied (backend category and group descriptions also processed so re-save can clean if needed). Note the filtering only applies during save operations so existing words that are configured to be filtered will not clear until re-saved.

Actions #4

Updated by krileon over 9 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF