Skip to content

What Happened to Stop Spammers? #8

@webguyio

Description

@webguyio

UPDATE 1 — I've successfully re-adopted Stop Spammers on WordPress.org.

UPDATE 2 — Dam Spam is now on WordPress.org.


I adopted Stop Spammers many years ago and in one form or another have continued to help maintain it ever since, as others have come and gone from the project. Sometimes things get messy, especially when someone comes into a project who neither cares about it nor its users. Over a year ago, that very thing happened and development was halted immediately.

Seeing the writing on the wall, I got to work forking the project so it didn't die completely:

https://wordpress.org/plugins/dam-spam/

Unsurprisingly, when there's no one at the wheel, things eventually crash, and Stop Spammers was de-listed from WordPress.org for months.

While I do recommend migrating to the new fork, I understand that there are many reasons people can't or won't, so I have made sure to also fix Stop Spammers, which I now refer to as Stop Spammers Classic:

https://wordpress.org/plugins/stop-spammer-registrations-plugin/

If you want to try Dam Spam, you'll want to deactivate Stop Spammers before activating Dam Spam. All your settings will automatically carry over.

All Stop Spammers and Dam Spam users are equally welcome to get support here:

https://github.com/webguyio/dam-spam/issues

Thank you!

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions