Language: en, de

Antispam Bee 3.0 is a complete rewrite. Before it is released, we need it run on real sites with real comment traffic — which is where you come in.

A pre-release is not meant for production. Please test it on a staging site, or on a site you are able to restore.

• WordPress 4.7 or newer
• PHP 7.4 or newer

1. Open the releases page and pick the newest entry marked Pre-release. Download the antispam-bee.zip attached to it.
2. In WordPress, go to Plugins → Add New → Upload Plugin and upload the file.
3. Confirm the replacement when WordPress asks, and activate.

Do not use the Latest release shortcut on GitHub: it deliberately skips pre-releases and will hand you the current 2.x version instead.

The settings from Antispam Bee 2.x are migrated automatically the first time the new version runs. Have a look at Settings → Antispam Bee afterwards and check that everything arrived the way you expect.

Your old settings are not deleted — the 2.x options stay in the database untouched, so going back is possible (see below).

• Submitting comments on the front end, with your normal theme
• The settings screen: saving, switching individual rules on and off
• The migration itself, from a real 2.x configuration rather than a fresh install
• Multisite, if you run it
• A page cache in front of the comment form
• A persistent object cache (Redis, Memcached), if your host provides one

Please open an issue in the issue tracker.

A report is much easier to act on when it says:

• the Antispam Bee version you are running — the notice in the admin area shows it
• your WordPress and PHP versions
• whether the site is single site or multisite
• whether a page cache or object cache is active
• what you did, what you expected, and what happened instead

Comments that were wrongly treated as spam are worth reporting in detail: which rule caught them, if the reason is recorded, and what the comment looked like.

The pre-release version shows a dismissible notice on the plugins list and on its settings page. Dismissing it applies to the version you are running; a later pre-release shows it again.

WordPress does not offer downgrades, so install the 2.11.x ZIP from the releases page the same way you installed the pre-release. Your 2.x settings are still in the database and are picked up again.

Nothing to do. The stable release is offered as a normal plugin update, and you move back onto the regular update channel automatically.

Thank you for testing. Every report before the release is one fewer problem on somebody's live site afterwards.