Skip to content
This repository

Spam and the ability to modify the comment form #124

mindctrl opened this Issue November 08, 2012 · 1 comment

2 participants

Alex King

This is a great plugin. Thanks for sharing it with the community.

I have a request that I think will make it even better.

To make use of the social comment feature for site visitors, we have to allow anonymous comments in the WP settings. That is to say Settings > Discussion > "Users must be registered and logged in to comment" must be unchecked. If it's checked, visitors cannot comment using their social media accounts via the Social plugin because WP requires them to be logged in via a WP account.

In the scenario above, the WP site obviously receives a lot of comment spam. This requires an additional spam fighting plugin or requires someone spending a lot of time moderating comment spam.

Proposed Solutions
A couple of solutions come to mind.

One option is to add a filter in lib/social/comment/form.php that allows one to modify the form output so that a challenge question can be added.

Knowing the first option could be tricky and some devs could break the plugin, another solution is to add an option in the plugin settings that allows site admins to specify, if they want, a challenge question to be displayed.

Another option, if possible, would be to hook into WP and display the social login buttons when the WP setting is enabled that requires users be logged in. This would allow them to comment using social accounts without requiring they create a WP account beforehand.

Any of these would significantly reduce the comment spam that comes in from bots auto-filling the default fields.


Alex King

The standard WordPress comment form hooks can use used for at least one of these options. I don't think a change here is needed, but will be happy to review a patch if one is presented.

Alex King alexkingorg closed this December 17, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.