I had everything setup and working just before I did this update. After doing the update, I got a few errors in the log before I ran the database update script (table cache_mollom did not exist).

Even after doing that, I still get spam messages posted - looking at the log, I don't see any mollom log entries anymore. Going to the mollom admin page, it says everything is fine, and shows no errors.

In the PHP error log, I see:
called mollom.verifyKey at server http://88.151.243.81 with no session ID

I don't know if it is related - for now I've disabled all posting at my site.

Should not have updated! Be careful....
Any help appreciated.

CommentFileSizeAuthor
#35 mollom-bypass-fix.patch1009 bytesdries

Comments

bwooster47’s picture

bwooster47 commented
Priority: Normal » Critical

Just to update the uncertainty in the description - have just run a trial run, and confirmed that this version of mollom does not work, at least at my site - no proof yet of a bug, could still be a config at my site.

I have no errors on Mollom admin page, and the setting for "forum topic" says text analysis and captcha, but still people are able to post spam on forums without Mollom reporting anything in the logs.

Confirmed that Mollom does have a php error:
[16-Jan-2009 14:46:02] called mollom.verifyKey at server http://88.151.243.81 with no session ID
which is probably the root cause of the problem.

Given that the database format changed, I can't go back to previous versions of Mollom, so I'm stuck. Any quick resolution appreciated...!

tech4him’s picture

tech4him commented

add one more user/site to this problem. Just removed CAPTCHA from a site and installed this version of Mollom. Installation was fine for me, no errors. None of the forms are showing the CAPTCHA nor are the Mollom statistics showing and transactions although I've even created some submissions myself.

FYI, I also set Mollom to block all form submissions if the service is unreachable, still all forms are unprotected.

Running Drupal 6.9 and Mollom 6.x-1.7

Thanks

dries’s picture

dries commented

Could you please provide the output of the following MySQL query?

SELECT * FROM variable WHERE name LIKE 'mollom%' AND name != 'mollom_private_key';

More information is needed to debug this query

bwooster47’s picture

bwooster47 commented

Here's what I got using phpMyadmin:
mollom_acidfree_node_form i:0;
mollom_blog_node_form i:0;
mollom_book_node_form i:0;
mollom_comment_form i:2;
mollom_fallback s:1:"0";
mollom_faq_node_form i:0;
mollom_forum_node_form i:2;
mollom_image_node_form i:0;
mollom_page_node_form i:0;
mollom_public_key s:32:"9890312d963f6e8a7490317fac6d55c3";
mollom_servers a:2:{i:0;s:20:"http://88.151.243.81";i:1;s:21:"htt...
mollom_story_node_form i:0;
mollom_user_pass i:1;
mollom_user_register i:1;

MrGeek’s picture

MrGeek commented
Version: 6.x-1.7 » 5.x-1.7

Same thing here except:
I'm using 5.x
The create-user form seems to be working - but the protect comments and new forum posts does not (no captcha)

dries’s picture

dries commented

#360857: Mollom Stopped Working After Upgrade looks like a duplicate. Text from the report: I had 6.X-1.6 installed and everything was working fine. I upgraded Drupal from 6.8 to 6.9 and then upgraded Mollom from 6.x-1.6 to 6.X-1.7. Now I do not have any protection. I checked all the mollom settings and they are all set to captua. My keys are good, and I still have the graph showing what is stopped before. I have all input types checked, ie, blog, pages, story. etc... I then uninstalled 6.X-1.7 and went back to 6.X-1.6. Now it does not work. I had to block anonymous posts, because of a lot spam...

dries’s picture

dries commented
Version: 5.x-1.7 » 6.x-1.x-dev

re #5: the Drupal 5 version of the Mollom module did not really change. The only new change in Mollom 1.7 for Drupal 5 is a documentation update. I'm moving the version back to Drupal 6.

@all: I have not yet been able to reproduce this problem. I need some help debugging this problem ...

bwooster47’s picture

bwooster47 commented

I can help with debugging - but I've never looked at this module, what should I look for?
Starting with the PHP error message above, I added some debug output lines in nodeapi and expand_element.

I did try this for a authenticated / power user, since I can't turn on anonymous postings because of the flood of spam.
When I post an node, nodeapi never gets a isset($GLOBALS['mollom_response']) - it is always empty when I print it out using mollom_debug.

And mollom_expand_element never gets called - I have a mollom_debug line at the top, and it never shows up in my PHP error_log.

MrGeek’s picture

MrGeek commented

I believe my Mollom stopped working when i did the D5.14->5.15 update.
At any rate, it is currently not working for comments and new forum-topics so i will watch this thread for any updates and try to help with the troubleshooting.

dries’s picture

dries commented

Re #9: did you update Mollom or only Drupal core? If you only upgraded Drupal core, that suggests that somehow the Mollom module broke due to a change in core.

Benjamin Schrauwen’s picture

Benjamin Schrauwen commented

I'll have a look in the backend logs, but what are the URLs of the websites where you guys are experiencing these problems.

bwooster47’s picture

bwooster47 commented

I suspect this is something in Drupal core and mollom.module, not a backend issue.

I just noticed that Mollom is filtering comments. It is not filtering nodes - specifically tested "Forum" postings.
I don't see the "submitted handler" message when nodes are being submitted.
if (!empty($edit) || !empty($form_state['submitted'])) {
_mollom_debug("mollom_expand_element: submitted handler");
never happens for a node (tested Forum node).

BTW, looks like with this version _mollom_debug messages are always written to PHP error_log by default - shouldn't the default be to not to write to the error_log? It could get huge and not too many people monitor that file!

I added some printfs, here's what I see:
[19-Jan-2009 14:53:12] mollom_expand_element: in it XXX
[19-Jan-2009 14:53:12] mollom_expand_element: XXX gen empty state (if (empty($mollom_state)) code)
[19-Jan-2009 14:53:12] mollom_expand_element: submitted handler
[19-Jan-2009 14:53:12] mollom_validate_analysis for 'comment_form'
[19-Jan-2009 14:53:13] called mollom.checkContent at server http://88.151.243.81 with no session ID
[19-Jan-2009 14:53:13] mollom_validate_analysis retrieved spam status 1 and session ID 'c0f25b42eed08b2e'
[19-Jan-2009 14:53:13] mollom_set_data XXX for did comment-5163
[19-Jan-2009 15:17:47] mollom_expand_element: in it XXX
[19-Jan-2009 15:17:47] mollom_expand_element: XXX gen empty state
(repeated)
[19-Jan-2009 15:35:20] mollom_nodeapi XXX for node-932 op: insert response-isset: N
[19-Jan-2009 15:38:48] mollom_expand_element: in it XXX
[19-Jan-2009 15:38:48] mollom_expand_element: XXX gen empty state
(repeated)

dries’s picture

dries commented

It sounds like this _might_ be specific to node types (and not to comments) ... I haven't tried to reproduce this problem for node types, but I'll give it a try. Let me know if that is consistent with what others are seeing.

xamount’s picture

xamount
Primary language English
commented

i cant say for sure if mollom was working before drupal 5.15.

I upgraded to 5.15 tonight. I was not using mollum before. I just installed mollum and it doesnt seem to work. The keys are correct. It only seems to work on the "password request" form. Doesn't work on forum topics, node types, contact form, webforms.

After searching the issue queue, I found this thread.....subscribing.

dries’s picture

dries commented

I tried to reproduce this problem by creating some custom content types on a fresh Drupal 6 install, but was unable to reproduce the problem above. I did not have a D6 website that I could upgrade, so I've not been able to re-test the upgrade path yet. If someone can help me reproduce the problem, that would be great. Thanks!

bwooster47’s picture

bwooster47 commented

[Preliminary observation: I think this is a problem when mollom_expand_element is not called.

I have found it works fine for anonymous-user comment creation, and for node creation for logged-in users.
But it does not get called for anonymous-user node creation.]

Update: I just re-tested, reenabled anonymous users, and now mollom_expand_element is being called at least for one anonymous user (i.e. me, when I tested it manually). It is not being called for all the spamming anonymous users who are using automatic bots.

bwooster47’s picture

bwooster47 commented

Would it be possible for someone to hack up a non hook_elements version of the current Drupal module? My previous comment test seems to be holding - anonymous spambots are able to get/post a node without hook_elements in mollom ever being called. When I tired to reproduce this manually, it works fine and hook_elements does get called.
I don't know where to go from here - but if I had the previous version of this module working with the current database, I could easily test it and that would confirm that the problem is Drupal's hook_elements mechanism or eliminate it as the source of this problem.

crozilla’s picture

crozilla commented

I'm having this same problem, I'm getting about 10 spam posts a day, but only in forum topics. Everything else seems to work. My blocked-spam stats drop off right about the time I upgraded (first, I upgraded the mollom module, then I upgraded to v6.9 if that matters).

I am now running v6.9 and v1.7.

Here is my SQL output:

mollom_blog_node_form i:1;
mollom_comment_form i:1;
mollom_fallback s:1:"0";
mollom_forum_node_form i:1;
mollom_page_node_form i:1;
mollom_poll_node_form i:1;
mollom_public_key s:32:"a3dcda2d5e3b1380309db67f61f185cc";
mollom_servers a:2:{i:0;s:20:"http://88.151.243.81";i:1;s:21:"htt...
mollom_story_node_form i:1;
mollom_survey_node_form i:1;
mollom_user_pass i:1;
mollom_user_register i:1;

bwooster47’s picture

bwooster47 commented
Title: Not filtering after update » 6.x-1.7 Not filtering after update

Well, looks like we are not going to get a fix for this anytime soon?

If that is true, it seems bad to leave this deficient release out there for everyone to download! 6.x-1.6 worked just fine, 1.7 had too many changes which should not be made to a supposedly stable release. As it stands now, people will upgrade, and find they are now owners of a broken module. If this truly is going to take a while to fix, then shouldn't someone withdraw the 1.7 from the recommended release and put back 1.6 there? Or if that is no longer possible, maybe mark it in red so people are warned before downloading.

Oh well....

crozilla’s picture

crozilla commented

I found a solution to the problem. I re-installed Akismet and enabled it only for forum topics. That seemed to stop the onslaught of spam posts. Still, it isn't an elegant solution and will certainly cause its own problems. But until someone fixes that bug, it seems to be working. Let's hope they solve this in the next revision...

crozilla’s picture

crozilla commented

My bad. That solution doesn't seem to work. Still need a real fix for this problem...anyone?

bwooster47’s picture

bwooster47 commented

Well, I am ready to vote for this module as the worst maintained-module in Drupal! Major code was changed in a production release, and no one is around to fix the problem... either a Drupal problem (hook_elements not working as designed - #359905-17: 6.x-1.7 Not filtering after update), or some other mollom bug.

Here's a workaround that should work:

Disable module.
Drop all mollom* tables from the SQL database using phyMydmin, or a
DROP TABLE (list all names here) ; command in SQL. Uninstall-ing the module might do this too.
Delete the mollom module folder.

Then re-install the better working version, anything before 1.7, here's link to 1.6:
http://ftp.drupal.org/files/projects/mollom-6.x-1.6.tar.gz
Enable module, re-enter all required values, and it should work correctly since it is not using that new-fangled "hook_elements" call.

dries’s picture

dries commented

Almost no one has problems with the 1.7 release. The Mollom 1.7 release is actively being used by a couple thousand users, and new users are installing it every day.

Furthermore, the Mollom module for Drupal 6 comes with SimpleTests that test the filtering. I ran the tests on 3 setups, and they all pass. Does the tests pass when you run them?

Last but not least, based on the comment in #12 it looks like Mollom _is_ working. You realize that Mollom will not always show a CAPTCHA, do you?

I'd love to help fix this problem, but as indicated, I have been unable to reproduce the problem. Can you reproduce the problem on a clean Drupal 6 install? How do you test whether Mollom works or not?

dries’s picture

dries commented
Status: Active » Postponed (maintainer needs more info)
axel pressbutton’s picture

axel pressbutton commented

Hi,

+1 for the 'not working' list :(

Drupal 6.9 and Mollom 6.x-1.7

I'll rephrase that, The CAPTCHA only works but if I enable the Text analysis and CAPTCHA backup mode I certainly am not getting any text analysis as I've tried putting all sorts of rubbish into my site-wide contact form.

A point to note for my setup is that this all works fine on an identical install that I'm running locally via XAMPP. After moving the site to a remote server and changing to the appropriate set of keys I get the problem. I've tried clearing caches, disabling the module and re-enabling.

Could this have anythign to do with a corrupt path anywhere that is being inherited from my local install that would be prefixing paths with the site folder in htdocs of XAMPP? e.g. /drupal6/ (from 127.0.0.1/drupal6/).

According to the message on /admin/settings/mollom it is quite happily talking to the Mollom server "We contacted the Mollom servers to verify your keys: the Mollom services are operating correctly. We are now blocking spam."....in fact, my logs even show stuff like

Ham: if mollom doesn't stop this viagra message with large ********s then there's something wrong with free qualifications and prescription drugs

Surely this would be classed as SPAM and NOT HAM?

Any help, as usual, would be greatly appreciated. Thanks :)

elstudio’s picture

elstudio commented

Agree with Axel's comment -- Mollom filtering does not seem to display captcha after upgrade to 6.x-1.7.

Interestly, simpletests do work, at least on my staging server. Doing this manually works in Staging:

* Manually set Mollom keys to test case values
* Messages with "ham" "spam" and "unsure" values give results expected in tests
* Captcha submission always fails

Back in production, with 1.7 and the proper (not test) keys:

* Attempt to post test comment "Herbal viagra! Herbal viagra! Herbal viagra!"
* I expect this to throw the captcha, like it did with v 1.6 and previous
* Instead, comment is posted without display of captcha

And we've seen a bunch of spam messages get through over the weekend. I've reported these to Mollom before unpublishing. As in Axel's case, Mollom says it's working and blocking spam.

How else can I help diagnose this?

bwooster47’s picture

bwooster47 commented

Here's current state of debugging this issue:

I allow anonymous posters to create topics, and have set Preview required, and Mollom to scan forum topics, and when I manually do a test, both of these features get invoked
But when spammers do a POST, they bypass both mechanisms - they don't seem to need a preview and
then save, and secondly, no mollom gets invoked.

This is quite painful to debug, here's where I'm at, in case anyone has any hints.
I used the trace module, to trace hook elements and nodeapi, and database update and inserts.

First add, I did this manually, which works fine - mollom does get invoked, and two POSTs are required:

#892a731b T=0.000000 [REQUEST] 2009-02-23 16:35:30.722485 POST /node/add/forum/11/ HTTP/1.1
#892a731b T+0.633373 [QUERY ] d=0.079597s variable_set: UPDATE variable SET value = 'b:1;' WHERE name = 'dev_query'
#892a731b T+0.714043 [HOOK ] hook_elements: system, user, mollom
#892a731b T+0.991585 [HOOK ] hook_nodeapi: book, comment, menu, path, search, statistics, taxonomy, trigger, acidfree_image, faq, mollom, print, print_mail, print_pdf, forum, pathauto, ed_readmore, xmlsitemap_node, acidfree
#892a731b T+2.685201 [QUERY ] d=0.000381s cache_set: UPDATE cache_mollom SET data = 'a:6:{s:11:\"#session_id\";s:16:\"...\";s:8:\"#form_id\";s:15:\"forum_node_form\";s:17:\"#require_analysis\";b:1;s:16:\"#require_captcha\";b:0;s:15:\"#passed_captcha\";b:0;s:16:\"#user_session_id\";s:32:\"...\";}', created = 1235421333, expire = 1800, headers = '', serialized = 1 WHERE cid = '...'
#892a731b T+2.685582 [QUERY ] d=0.023873s cache_set: INSERT INTO cache_mollom (cid, data, created, expire, headers, serialized) VALUES (...)

... now the second POST shows the drupal_write_record;
#8b708468 T=0.000000 [REQUEST] 2009-02-23 16:36:07.044344 POST /node/add/forum/11/ HTTP/1.1
#8b708468 T+0.081902 [QUERY ] d=0.004409s variable_set: UPDATE variable SET value = 'b:1;' WHERE name = 'dev_query'
#8b708468 T+0.087439 [HOOK ] hook_elements: system, user, mollom
#8b708468 T+0.103133 [HOOK ] hook_nodeapi: book, comment, menu, path, search, statistics, taxonomy, trigger, acidfree_image, faq, mollom, print, print_mail, print_pdf, forum, pathauto, ed_readmore, xmlsitemap_node, acidfree
#8b708468 T+0.647160 [QUERY ] d=0.000992s cache_set: UPDATE cache_mollom SET data = 'a:6:{s:11:\"#session_id\";s:16:\"...\";s:8:\"#form_id\";s:15:\"forum_node_form\";s:17:\"#require_analysis\";b:1;s:16:\"#require_captcha\";b:0;s:15:\"#passed_captcha\";b:0;s:16:\"#user_session_id\";s:32:\"...\";}', created = 1235421367, expire = 1800, headers = '', serialized = 1 WHERE cid = '...'
#8b708468 T+0.649021 [HOOK ] hook_nodeapi: book, comment, menu, path, search, statistics, taxonomy, trigger, acidfree_image, faq, mollom, print, print_mail, print_pdf, forum, pathauto, ed_readmore, xmlsitemap_node, acidfree
#8b708468 T+0.651509 [HOOK ] hook_nodeapi: book, comment, menu, path, search, statistics, taxonomy, trigger, acidfree_image, faq, mollom, print, print_mail, print_pdf, forum, pathauto, ed_readmore, xmlsitemap_node, acidfree
#8b708468 T+0.671562 [QUERY ] d=0.052473s drupal_write_record: INSERT INTO node_revisions (nid, uid, title, body, teaser, log, timestamp, format) VALUES (0, 0, 'Testing only', 'Just a test', 'Just a test', '', 1235421367, 1)
------------------------

Second add - watching a automated spammer - they get to drupal_write_record on the first POST itself!
The mollom update cache line from previous test never shows up here - nothing from mollom shows up here, though the HOOK line shows mollom in it.

#99226b79 T=0.000000 [REQUEST] 2009-02-23 16:39:46.160993 POST /node/add/forum/11/ HTTP/1.0
#99226b79 T+0.015110 [QUERY ] d=0.000448s variable_set: UPDATE variable SET value = 'b:1;' WHERE name = 'dev_query'
#99226b79 T+0.016622 [HOOK ] hook_elements: system, user, mollom
#99226b79 T+0.034763 [HOOK ] hook_nodeapi: book, comment, menu, path, search, statistics, taxonomy, trigger, acidfree_image, faq, mollom, print, print_mail, print_pdf, forum, pathauto, ed_readmore, xmlsitemap_node, acidfree
#99226b79 T+0.044998 [HOOK ] hook_nodeapi: book, comment, menu, path, search, statistics, taxonomy, trigger, acidfree_image, faq, mollom, print, print_mail, print_pdf, forum, pathauto, ed_readmore, xmlsitemap_node, acidfree
#99226b79 T+0.076909 [QUERY ] d=0.012505s drupal_write_record: INSERT INTO node_revisions (nid, uid, title, body, teaser, log, timestamp, format) VALUES (0, 0, 'FREE PORN | ADULT .....
....
#99226b79 T+0.089414 [QUERY ] d=0.021515s drupal_write_record: INSERT INTO node (vid, type, language, title, uid, status, created, changed, comment, promote, moderate, sticky, tnid, translate) VALUES (953, 'forum', '', 'FREE PORN | ADULT | ejaculation film sexadult shop toy', 0, 1, 1235421586, 1235421586, 2, 0, 0, 0, 0, 0)
#99226b79 T+0.110929 [QUERY ] d=0.000477s node_save: UPDATE node_revisions SET nid = 955 WHERE vid = 953

Created [#382472] to track what may be the root cause - drupal node module allowing forum nodes to be created with the first invocation of a HTTP POST even though Preview is required before saving.
Not sure yet if it is related, so keeping this issue open too.

bwooster47’s picture

bwooster47 commented

Finally, I think I have data that might be useful - seems like a Drupal core bug to me.

So I started collecting all the POST data, and here are the results:

First working trace - there are two POSTs, first only shows Preview button, second shows Save button. The Second working trace is from the spammer - it shows no "op" - neither Preview or Save, that seems like the key difference which causes Drupal to immediately insert that spam post.

FIRST - my manual test, which works fine - shows Preview then Save:

Sun, 01 Mar 2009 01:10:22 +0000 /node/add/forum/111 [FIRST - PREVIEW]
a:8:{s:5:"title";s:15:"Anon Me Testing";s:8:"taxonomy";a:1:{i:1;s:2:"11";}s:7:"changed";s:0:"";s:14:"teaser_include";s:1:"1";s:4:"body";s:55:"I am testing this to see what shows up in POST data log";s:13:"form_build_id";s:37:"form-3debe7e4d723f11e66f084d16dea6436";s:7:"form_id";s:15:"forum_node_form";s:2:"op";s:7:"Preview";}

Sun, 01 Mar 2009 01:10:42 +0000 /node/add/forum/111 [SECOND - SAVE]
a:9:{s:5:"title";s:15:"Anon Me Testing";s:8:"taxonomy";a:1:{i:1;s:2:"11";}s:7:"changed";s:0:"";s:14:"teaser_include";s:1:"1";s:4:"body";s:110:"I am testing this to see what shows up in POST data log
Second line added before clicking on Save button.
";s:13:"form_build_id";s:37:"form-a2517a789618759ac56b3485c5c0e77e";s:7:"form_id";s:15:"forum_node_form";s:6:"mollom";a:1:{s:10:"session_id";s:16:"4cc667ed28ad4bf0";}s:2:"op";s:4:"Save";}

SECOND - spammer bypassing Preview button and also mollom checks:

Sun, 01 Mar 2009 01:14:02 +0000 /node/add/forum/111/  [SPAMMER POSTING]
a:7:{s:5:"title";s:39:"PharmacyOnlineShop - viagra cheapest uk";s:8:"taxonomy";a:1:{i:1;s:2:"11";}s:7:"changed";s:0:"";s:14:"teaser_include";s:1:"1";s:4:"body";
s:683:"<a...(deleted spam) ... buy now";
s:13:"form_build_id";
s:37:"form-6260e2d9d06de1e4bb16e86b9cf4f15a";
s:7:"form_id";
s:15:"forum_node_form";}
elstudio’s picture

elstudio commented

Rolling back to 6.x-1.6, which works fine for me. There is clearly an issue with 1.7 and drupal 6.10.

Anybody have further thoughts about bwooster47's diagnosis?

joestewart’s picture

joestewart commented

Dries, can you update the status of this bug?

Do you need more info?

The way this was triggered for me is the same as others above - anonymous are able to create forum topics. Before the upgrade to mollom 6.x-1.7, mollom protected this very well. After upgrading, spammers were able to post and there is no sign that mollom saw the POST. Comments are still being protected fine.

It seems bwooster47 provided a lot of troubleshooting a few weeks ago. Also kind of disturbing that he opened [#382472] almost a month ago and there has been no acknowledgment, comment, or assignment of this core bug report.

dunlop’s picture

dunlop commented

I experienced the same problems with 6.x-1.7 on my site. After upgrading I started getting many spam posts on my forums which allow anonymous posts. Spam posts are listed in my logs as being posted by the anonymous user. While using the previous 6.x-1.6 version I had no problems with Spam on my site.

After reading this issue I tried disabling, uninstalling mollom and completely deleting the mollom module directory. I checked that the mollom DB tables had been deleted and they were. I then reinstalled 6.x-1.7 and the spam continued to get through. I tried to test mollom by entering some Spam myself (as anonymous) and it was correctly blocked by mollom. It was the same message content that the spammer had successfully posted without being flagged as spam. I did all this to verify to myself that mollom was cleanly installed and configured.

I then disabled, uninstalled mollom and completely deleted the mollom directory again, but this time I reinstalled mollom 6.x-1.6. Now mollom is protecting my site again and no more spam is getting into my forums.

During the time while using 6.x-1.7 my logs showed no blocked Spam but did show allowed Ham messages. The spam was getting onto my site as well as the ham. Note that the allowed Ham message was for a comment and not for a forum post. This suggests the mollom was not actually checking the content, although I did have the setting for the forum content type set to check.

After reverting to 6.x-1.6 I am now again getting Spam blocked for forum messages in my logs again and the Spam is being correctly blocked.

That's all I have for now, but I do wonder if spammers have found a way to submit anonymously which bypasses or disables the mollom check.

dunlop’s picture

dunlop commented
Status: Postponed (maintainer needs more info) » Active
dunlop’s picture

dunlop commented
Version: 6.x-1.x-dev » 6.x-1.7
kerberos’s picture

kerberos commented

Just wanted to say that we are having the same issue: anonymous forum posts are not being successfully filtered. I'll try reverting to 1.6.

dries’s picture

dries commented
StatusFileSize
new mollom-bypass-fix.patch1009 bytes

Damien discovered a fix. Patch attached.

dries’s picture

dries commented
Status: Active » Fixed

I've committed this patch to the development branch of Mollom. Should be part of the next release. Thanks DamZ!

bwooster47’s picture

bwooster47 commented

Preliminary results show that the patch seems to be working.

Now if we could also get two more fixes to the 1.7 release:
1) it spams the error log
[21-May-2009 18:14:22] mollom_validate_analysis retrieved spam status 2 and session ID '....'
[21-May-2009 18:14:29] mollom_expand_element: submitted handler
[21-May-2009 18:14:29] mollom_validate_analysis for 'comment_form'
and many other messages - I am hoping developers leave debug statements out of logs when a release is made - is there some way to locally patch this 1.7 version to make debug not go out to disk?

2) Issue #387094: When "do not send feedback", get Error 1000 error 1000 seems like a coding error also.

dries’s picture

dries commented

The mollom debug issue that you mention in 1, should be fixed in the DRUPAL-6 development branch. Fixed that a while ago.

I'll look into issue #2.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.