cimddwc

Thanks for the reply. Well, Akismet successfully caught 44 spams over night but still displays this “…from checking 1 comment”.

I investigated a bit more: There’s this one “akismet_error” db entry which contains the very same comment_id as the “please moderate” comment I mentioned yesterday, which I deleted – so Akismet is indeed trying to re-check a comment that doesn’t exist anymore: function akismet_check_db_comment, which is called from akismet_cron_recheck, returns an empty result since $wpdb->get_row returns nothing from the comment table, and thus akismet_cron_recheck in its “else” section just reschedules the recheck.

Or in other words: akismet_check_db_comment (and thus akismet_cron_recheck) doesn’t distinguish between “comment doesn’t exist anymore” and “akismet_http_post, the communication with akismet.com, had an error and returned ””…

The numbers seem to have almost(?) caught up by now, so I guess nothing was lost, or not much – thanks for that. 🙂

Just had almost the same problem (only “Argument #1”) when I just upgraded to 2.9.1, but only sometimes. It seems to be caused if there are GET or POST parameters (Argument #1 and #2, respectively) in the request but these are unset by a plugin, which in my case is a modification I made to better combine Language Switcher and WP Super Cache.

I added the line
if (!isset($_GET)) $_GET=array();
before the array_merge line 637, and my warnings are gone. For the “Argument #2” warning, a similar line would be needed for $_POST; however, this probably won’t help you with your new post problem – since the important post data is apparently missing from the request – and you’re gonna have to try esmi’s hints. It might help searching your plugin files for unset($_GET) and unset($_POST) (note that there might be additional blanks around the parentheses).

(Edit: On a second thought and more investigation, I rather changed my aforementioned modification, since that was my only cause, so no core file mod needed for me…)