• I’d like to stop spammer registration. I reached out to “Stop Spammers” but they told me I should not run their plugin with Wordfence. Can anyone suggest a way to accomplish this while running Wordfence?

    Thanks you!
    Scott

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi @thinkblissful,

    Did the “Stop Spammers” plugin authors provide more information?

    Have you tried to run both plugins on your site? If so, what type of issue did you experience?

    Anonymous User

    (@anonymized-5837566)

    We discussed over email.

    He didn’t report any bugs, was more just a general inquiry about if he could or should use them both together.

    I’m not aware of any conflict, but concerning potential conflict and memory consumption, I would recommend choosing one or the other. Also, dog-piling on multiple security plugins doesn’t necessarily make a site more secure.

    I’d say, from simplest to most complex, there are three good choices for users:

    1. Akismet plugin. This is generally good enough for non-membership sites to block basic comment spam.

    2. Stop Spammers plugin. This is generally good enough for small to medium sized membership-based sites where you really need to lock down registration from spammers getting in.

    3. Wordfence plugin. Probably overkill for very small, non-member sites, but generally good enough for locking down larger, more enterprise-level websites, where the best security is needed.

    Would you say that’s a pretty fair break-down?

    Do you need to allow public registration on your WordPress website? If so, you indeed have a difficult situation but not impossible.

    Myself, I have a fully monetized blog that makes my living, with what’s probably average traffic for that type of endevor, and plentiful traffic from criminal bots. I get zero spam of any sort. I deleted or hid anything that allows access to public registration. I also use a challenge question on our comments, along with Wordfence, and a few .htaccess items and server level firewalls (CSF and ModSecurity). I deleted Akismet years ago, and the only security software in my front-end stack is Wordfence, with the only spam plugin being that which creates the challenge question.

    If I had to allow public registration I’d just use a challenge question or captcha, along with Wordfence and the usual backend stuff in .htaccess and server firewalls, problem solved.

    Edit: I also use a small blacklist in the WordPress Discussion/Settings, but this has not been required for more than a year, I leave it configured with a few of the more obnoxious and obvious spam words, as a last resort. In the case of allowing public registration, spam word blacklists are quite useful.

    MTN

    • This reply was modified 8 years, 3 months ago by mountainguy2.

    Moderator, is the opening post on this thread clickbait for a gold investment website?

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Help Stopping Spammer Registration’ is closed to new replies.