I haven't been able to test incoming pings yet, but I have been worried about having the Captcha module installed. Anonymous comments are allowed on my site, but they're captcha protected. Will this stop the pingback module from being able to create the anonymous pingback comments? Technically, the pingback module is already on the "inside" of the site and can directly manipulate the comment system so I would think it might not be a problem, but I don't have deep knowledge of how the internals of the Drupal comment system work. I think this issue should be addressed in the documentation for the module, either a mention that the module should work with comment spam control modules installed or notice that it won't.

Comments

andreashaugstrup’s picture

I have previously used pingback module alongside captcha module on my personal website. I don't recall any problems (captcha uses form_alter rather for all the hard work and doesn't touch hook_comment). I am currently using pingback module alongside mollom ( http://mollom.com/ ). Legitimate pings are coming through and I'm no longer getting the very low volume pingback spam I received pre-mollom.

duckpuppy’s picture

Thanks for the fast reply! I'm investigating mollum myself - good to know that this works as well.

andreashaugstrup’s picture

Title: Pingback and Captcha interaction » Captcha & mollom interoperability
Assigned: Unassigned » andreashaugstrup
Category: support » task

I'll get something added to the documentation about captcha module. Keeping this open until I get it done.

andreashaugstrup’s picture

Oh, and to test incoming pings: A long long time ago I wrote a stand-alone pingback client/server that you can use to manually send pingbacks. Go to: http://www.solitude.dk/ping/client.php

Select "send manual pingback" as the method and paste in the target and source to send a manual pingback.

doublejosh’s picture

This seems to suggest that it will work, but there is no definitive answer. Curious.

Dave Reid’s picture

There shouldn't be any problems because the spam prevention modules work on the Form API processing of comments, while Pingback just uses the comment_save() function which basically saves the comment to the database and that's it. I don't think we need to document something that already "just works".