A Mollom user reported a support ticket about unavailable Mollom servers and kept on complaining that he still sees errors. From our side, all Mollom services were confirmed to be up and running though.
Conclusions:
"In the Mollom statistics"...? Oh that explains it!
I guess you were looking at the partial log messages on admin/reports/mollom. These are "extracted" from the real watchdog log on "Recent log entries" (admin/reports/dblog). You can filter the Recent log entries by type/category "mollom" to see the proper/actual log messages with time information.
The log entries output on the "Mollom statistics" page only contain the summary of recent Mollom log entries without any time information, so these log entries were/are still the same log entries you've seen when you reported this ticket.
I'm going to file a bug report against the Drupal module to do something about those log entries on the Mollom statistics page. As far as I know, the intention was to allow to provide site moderators (not administrators) access to Mollom log messages on sites where moderators should not have access to all log messages on admin/reports/dblog.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | mollom.stats-remove-log.1.patch | 888 bytes | sun |
Comments
Comment #1
sunOy! In January 2010, @Dries already removed the watchdog output from the D7 version:
http://drupalcode.org/project/mollom.git/commitdiff/a5266ef130b501f18763...
It doesn't look like any issue was involved for that commit.
Since we seem to agree on this, I'm going to commit attached patch, identical to those D7 changes, which removes those log messages also from D6.
Merely want the testbot to have a stab at this.
Comment #3
sunBackend/testbot hiccup in blacklist tests.
Thanks for reporting, reviewing, and testing! Committed to 6.x-1.x.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.