Needs work
Project:
Mollom
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 Jan 2014 at 19:42 UTC
Updated:
27 Oct 2015 at 12:08 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
eshta commentedI'm not up on the historical knowledge, but from speaking with the Mollom engineering team, there isn't a reason not to from the service point of view. My hunch is that this feature was originally omitted to try to keep things simpler to set up and configure. Also, there may be some confusion since the white list api only applies to author information (not post content).
Comment #2
damondt commentedI would like to see this happen.
Comment #3
glekli commentedI'm attaching a patch that implements a whitelist configuration page. Please let me know your thoughts on it.
Comment #4
eshta commentedThanks for this! just wanted to give the heads up that this is not unnoticed. I'm hoping to review in the next few days.
Comment #5
eshta commentedAgain - so happy that someone kick-started the work here. As you picked up - it's very similar to the black-list functionality. I'd like to see a few things generalized a bit more so that there isn't so much duplication. See below.
We should add some instructions here. For example from the API docs: "Whitelist entries are checked first. On a positive whitelist match, no other checks are performed." It should be clear that if a term matches the whitelist, the blacklist won't be checked at all.
I don't think this does anything, does it? It's only used for automatic filtering on the blacklist in specific cases.
Could this just re-use the existing theme function that the black-list uses? The name/parameters can be generalized.
See above - no need for a duplicate of the same theming.
After all that - we'll need some tests too. Would be similar to the blacklist tests. This is awesome!