Closed (fixed)
Project:
Mollom
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
9 Sep 2010 at 21:14 UTC
Updated:
24 Apr 2014 at 17:13 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
sunStill tests only.
Comment #4
sunPlus new checkContent sequence server responses assertions.
Comment #6
sunComment #7
sund'oh - stale debugging code.
Comment #9
sunComment #10
sunNow with the actually game changing changes.
Comment #11
sunStill contains unrelated changes, but less.
Comment #13
sunThis one hopefully fixes all other tests.
Comment #14
sunProblem: I've tested manually, and in testing mode,
1. I can post a comment containing "unsure", hit Preview
2. get a CAPTCHA and enter "incorrect" there, and at the same time, change the comment into "ham", and hit Preview again
3. I no longer get a CAPTCHA and the logs contain a HAM response from checkContent
Comment #16
sunNow without that commented out line.
Powered by Dreditor.
Comment #17
sunAll tests are passing locally for me.
@todo:
- Documentation badly needs to be updated in various locations.
- Double-check whether we really need the added tests/assertions.
- Find a proper name for the added tests.
Comment #18
sunReverted the testing profile change.
Comment #19
dries commentedIn addition to your TODOs:
I'd give this a better name.
Comment #20
sunok, I get it now -- not sure how and why tests passed for me locally, but obviously, $this->disableDefaultSetup() does (also) not install Mollom module, so I'm really not sure how tests were able to call mollom() at all. So hopefully, this one will pass.
Working on the other todos now.
Comment #21
sunPlease wait for the bot to come back green. Since it doesn't seem to report back to d.o currently, you need to manually click "View details".
Comment #22
dries commented"When a content" should be "When content".
This can probably be removed?
This is not guaranteed. Maybe instead of 'will be' we should write 'may be' or 'are likely to be'?
This might need to be updated as well.
Comment #23
sunThanks! Incorporated your comments.
Comment #24
dries commentedGreat job, sun! Committed to CVS HEAD. Thanks a lot.
Comment #25
dries commentedComment #26
sunOk, next to backporting this change, I'm using this issue for a massive effort to additionally get both branches synchronized again.
For that sake, I'm attaching both a patch for HEAD and D6 - let's test HEAD first, commit, and afterwards re-test D6. Will manually run tests for D6 anyway.
Btw, we also have to test the update path for D6 since 6.13 before doing a new release. Will do that tomorrow.
Comment #28
sunManual testing for D6 revealed some hiccups, fixed in this one.
Comment #29
sunFixed the update path.
Comment #30
dries commentedPowered by Dreditor.
A D7 comment in the D6 module?
Comment #31
sunYes, as long as we do not backport the entire new profanity checking feature to D6, we are enforcing 'spam' as value for the text analysis 'checks'. It's not the only D7 note in the D6 module though.
Comment #32
sunAttached patch passes for me locally.
Comment #33
dries commentedCommitted to CVS HEAD. Thanks!