Closed (fixed)
Project:
Mollom
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Sep 2010 at 17:13 UTC
Updated:
24 Apr 2014 at 17:13 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
sun- Make the current type be preselected as default for new entries.
- Redirect back to the originating type-specific blacklist page after deleting an entry.
Note: I'm currently unable to delete a profanity entry - shouldn't be caused by this patch though.
Comment #2
sunFixed phpDoc.
Comment #3
dries commentedCommitted to CVS HEAD. Thanks.
Comment #4
sunBackport to D6.
Comment #5
sunThanks for reporting, reviewing, and testing! Committed to D6.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.
Comment #6
sun- Moved the add form to the top.
- Removed "Reason" column.
Comment #7
sunAttached patch additionally fixes the blacklist UI test accordingly.
Comment #8
dries commented0 zero passes in #7
Comment #9
sunAdded tests for the profanity blacklist, which reveal that blacklist entries are not deleted on the backend currently.
Comment #10
sunok, it's a client-side bug. This patch fixes it.
Comment #11
sunArgh. Stale debugging code.
Comment #12
sunTested manually and attached patch passes all tests.
Comment #13
dries commentedCommitted to DRUPAL-6. Needs to be ported to Drupal 7.
Comment #14
sunPorted to HEAD.
Comment #16
sunThis one should be better, I hope.
Comment #17
sunThanks for reporting, reviewing, and testing! Committed to HEAD.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.
Comment #18
sunDon't want to clobber the queue with lots of closely related issues, so re-opening and slightly re-purposing this issue.
I just learned that we are not fully conforming to http://mollom.com/api/addBlacklistText, which perhaps explains why I'm not able to delete certain entries. The particular one I tried does indeed contain trailing white-space.
Aside from this patch, there's more to it: Mollom returns TRUE for mollom.removeBlacklistText, even if the value does not exist or when the operation was not successful. This needs to be improved on the backend, and on the client-side, we want to add tests that verify the expected results for all possible (and partially bogus) operations.
Comment #19
sunAttached patch fixes lots of outdated and bogus tests. Now I also understand why the blacklist of the testing keys always contains garbage.
Comment #20
sunComment #21
dries commented1.
This trim is no longer necessary. The backend takes care of that. Probably means we can revert some of the code changes.
2. Now we splitted the blacklist in multiple blacklists, we might want to rename the menu from 'Blacklist' to 'Blacklists'?
Comment #22
sunThanks! I didn't fully revert though, since I prefer to set the $data properties that are sent to Mollom more explicitly, and because both the add and the delete submit handlers are more consistent this way.
In a next step, we should think about further usability improvements for the blacklist. While working on mollom.com's rather large one, I had the following clues:
- First and foremost, we want to sort alphabetically by 'text', and then by 'context'. Ideally, this should happen on the backend already, but we can also do it on the client-side.
- Would be nice to have checkboxes to be able to delete multiple.
Comment #23
dries commentedCommitted to DRUPAL-6--1. Thanks sun.
Comment #24
sunPorted to HEAD.
Comment #25
dries commentedCommitted to CVS HEAD. Thanks.
Comment #26
sunUnfortunately, the previous patch broke our tests (attached patch won't be tested, since tests on Mollom HEAD are failing). In trying to make them pass again, I struggled again with the testing profile, but was finally able to make it work. That revealed a couple of other glitches along the way.
Comment #27
sunThanks for reviewing. Committed to Mollom HEAD.
Comment #28
sunI'm going to run tests manually.
Comment #29
sunum. OK, so rather this one -- getting query strings right in D6 is a major pain; thankfully, we fixed that for D7!
Setting to RTBC, as I'm not sure whether you know a better way to build query strings in D6.
Comment #30
sunCommitted #29 to D6 for now, so as to be able to continue with further improvements for D7.
Comment #31
sun+ Added "match" to the blacklist UI.
+ Added an instant filter to search existing entries. ROCKS. Try it out! :)
Comment #32
sunAlright. The blacklist on mollom.com is so large that I had to do some heavy performance optimizations. ;)
Comment #34
sunFinal edition. I think this is ready to fly. Can't wait to backport this + deploy on mollom.com. ;)
Comment #35
sunBackported to D6.
Comment #36
sunI don't think it can get faster than this. Let's try again. :)
Comment #37
sunLook, I didn't really care for the blacklist before. But hey, with this patch, I'd happily administer blacklists the entire day! 8)
Comment #38
dries commentedI absolutely love it! Applied it on mollom.com for testing purpose.
I noticed there was a @todo in the patch, which is the only reason why I haven't committed it yet. ;-)
Comment #39
sunSo here's the final version with that remaining @todo resolved. Totally love it, too! :)
Comment #40
sunManually ran tests + this one passes.
Comment #41
dries commentedCommitted to DRUPAL-6--1. Thanks sun.
Comment #42
sunPorted to HEAD.
Comment #43
sunThanks for reporting, reviewing, and testing! Committed to HEAD.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.
Comment #44
sunAlso committed mollom.admin.js to D6, which got lost. ;)