Serendipity Forums

I just updated my old s9y installation to 1.7.8. Suddenly my comments to moderate are flooded with pingbacks. I'm sure I have a few real comments buried in there, but I cannot find them due to the flood of pingbacks.

How do I completely disable pingbacks?

And what is the SQL query that I should use to DELETE the over 2000 pingbacks that are pending moderator approval?

You mean trackbacks, don't you.
Did you play around with the trackback section options of the spamblock plugin config?
Else you also might disable comments (which would include trackbacks I assume) in total for a while with the killswitch option.

A simple sql command could be like this Certainly you will need to find something matching for your case like WHERE type = 'moderate' AND ..., since I don't have an exmple by hand how moderate set trackbacks are stored.

The emergency blockade could really be an option in this case.

You could also deactivate pingbacks by setting the option "Behandlung von per API übermittelten Kommentaren" (Treatments of comments made by the API) to block, in the trackback-section of the spamblock-plugin. Some of the other options there should help as well.

To disable pingbacks by code, edit the comment.php and insert an in line 139, before the if (untested).

Timbalu wrote:You mean trackbacks, don't you.
Did you play around with the trackback section options of the spamblock plugin config?
Else you also might disable comments (which would include trackbacks I assume) in total for a while with the killswitch option.

A simple sql command could be like this

Code: Select all

DELETE FROM `s_spamblocklog` WHERE reason LIKE 'BEE Honeypot%'

Certainly you will need to find something matching for your case like WHERE type = 'moderate' AND ..., since I don't have an exmple by hand how moderate set trackbacks are stored.

Well, the comments say 'Pingback' and not 'Trackback'. With a little tweaking, I got the SQL to work. I also removed the 'pingback' header from index.tpl and that pretty much shut it down.

Could you document your query and "fixes" here for others, please?
Maybe there also might be enhancements to do better, if we can see what you did.