wolfey

This issue has been resolved. I went ahead with what I described above (using fresh copies of WordPress 2.2.2 and Spam Karma 2.3 RC 4), and Spam Karma is working properly again.

Last week, I upgraded WordPress to 2.2.2, and – just like the upgrade before – nothing changed.

I’m not sure what else I can do about this, short of:

1. Backing up my database,
2. Deleting all of my WordPress files and my WordPress database information,
3. Doing a fresh installation of WordPress,
4. Re-importing only the fields I need (comments, pages, posts, etc.), and
5. Installing the plug-in again, to see whether the issue was caused by an upgrade to the plug-in, or the plug-in itself.

Should I just go ahead and try that? If so, which tables of the database would I need to export to just get those fields and nothing else, so I can be sure there’s nothing left over from any of the plug-ins I have?

Recently, I have upgraded to WordPress 2.2.1, but – unlike with the previous upgrade – nothing has changed.

I’ve been using WordPress for quite awhile…Maybe an upgrade from long ago (or from an older version of Spam Karma) is causing this problem?

(Bumping topic…)

Just wondering if anyone else has experienced this problem, because I still don’t know why this is happening.

Also, has anyone been able to contact drDave (Spam Karma’s creator) via the “SK2 Contact Form” on his site lately? I tried to do so awhile back, but it refused to submit due to the use of HTML code in my post. What’s interesting about this is that, even after removing every piece of HTML code I had used (including plain-text links, in case those were automatically being converted to hyperlinks before being sent), it still wouldn’t submit my message.

What was the problem? Interestingly enough, it turns out that the space between paragraphs is automatically converted to paragraph tags – squeezing my message onto a single line is the only way I could get it to be submitted, and given the trouble I had with the form earlier, I’m not sure if it got through, even though it said my message was submitted.

Just wanted to bring this up in case anyone else has had trouble contacting him as of late, or has been seeing the issues mentioned in this topic.

Recently, I have upgraded to WordPress 2.2, and have noticed a few changes with Spam Karma (still using the same version, 2.3 RC 1):

• The “Manage > Spam Karma 2” page no longer gives the “Headers already sent” error message when visiting it from the digest report’s link.
• When clicking on the “Yes” link on that page, no errors are listed on the “Spams Caught by SK2” page.
• The “General Settings” page shows an error message that wasn’t there before (white text, bold, and in a gray box) with the previous version of WordPress:
  

  Cannot load news from URL: https://wp-plugins.net/sk2/sk2_news.php?sk2_version=3&sk2_release=rc2&sk2_lang=

The rest remains the same: the digest link has that extra piece at the end and the “Manage > Spam Karma 2” page only shows the WordPress logo, the question and the “Yes” and “No” links.

(That’s odd…I just checked the “Spam Karma 2 Options” page again, and it’s showing the version number as 2.3 Release Candidate 2 – but when I downloaded it from the site, it was 2.3 Release Candidate 1…

Also, I’m running WordPress 2.1.3, but the highest version I could select when I posted this was 2.1.1.)
=====
Regarding the version of MySQL: Yes – it’s at version 5 here.

Regarding the FAQ: No, it isn’t listed anywhere.

I’ve tried out a few other options, and here’s what I noticed:

• Force MySQL Updates:
  

  Could not alter SQL table: wp_comments.
  SQL error: Duplicate key name ‘comment_date_gmt’

  Could not alter SQL table: wp_posts.
  SQL error: Duplicate key name ‘post_date’

  Could not alter SQL table: wp_posts.
  SQL error: Duplicate key name ‘post_date_gmt’

  Skipping duplicate blacklist entry: domain_grey – typepad.com.

  Skipping duplicate blacklist entry: domain_grey – blogspot.com.

  Skipping duplicate blacklist entry: domain_grey – livejournal.com.

  Skipping duplicate blacklist entry: domain_grey – xanga.com.

  Skipping duplicate blacklist entry: rbl_server – opm.blitzed.org.

  Skipping duplicate blacklist entry: rbl_server – bl.blbl.org.

  Skipping duplicate blacklist entry: rbl_server_uri – uri-bl.blbl.org.

  The three two-line items at the top were in a red box, and the rest were in a gray box – all of them were in bold, though.

• Reinit Plugins:
  Disabling RBL plugin (main server offline).
• Reset All Tables:
  

  Dropping all SK2 Tables!

  Dropped all SK2 Tables!

  Could not alter SQL table: wp_comments.
  SQL error: Duplicate key name ‘comment_date_gmt’

  Could not alter SQL table: wp_posts.
  SQL error: Duplicate key name ‘post_date’

  Could not alter SQL table: wp_posts.
  SQL error: Duplicate key name ‘post_date_gmt’

• Reset to Factory Settings:
  

  Could not alter SQL table: wp_comments.
  SQL error: Duplicate key name ‘comment_date_gmt’

  Could not alter SQL table: wp_posts.
  SQL error: Duplicate key name ‘post_date’

  Could not alter SQL table: wp_posts.
  SQL error: Duplicate key name ‘post_date_gmt’

  Skipping duplicate blacklist entry: domain_grey – typepad.com.

  Skipping duplicate blacklist entry: domain_grey – blogspot.com.

  Skipping duplicate blacklist entry: domain_grey – livejournal.com.

  Skipping duplicate blacklist entry: domain_grey – xanga.com.

  Skipping duplicate blacklist entry: rbl_server – opm.blitzed.org.

  Skipping duplicate blacklist entry: rbl_server – bl.blbl.org.

  Skipping duplicate blacklist entry: rbl_server_uri – uri-bl.blbl.org.

  Disabling RBL plugin (main server offline).

  Followed by:

  Running first-time install checks…

  File comments.php is OK.

  File comments-popup.php is OK.

  Your theme appears to be compatible (but you might want to run the Advanced Theme Compatibility Check at the bottom of the General Settings screen, for extra security).

  These three lines were in green boxes, unlike the rest of the errors mentioned above.

• Advanced Theme Compatibility Check:
  

  URL https://example.com/blog-directory/2007/01/23/my-entry/ contains the Payload. Your theme appears to be OK.

  Re-enabling form payload check.

  These two lines were also in green boxes.

Even after doing all of the above, though, the same error is still present on my site.