Delete comments for spam reasons

Hi @brrasmussen

sorry for the late reply – I was on vacation the last week!

This looks like a local problem. As you are the first and only person reporting this problem, I think there is something interfering in your browser here.

You can try to disable other plugins (which maybe are conflicting with JS/CSS here) and you can try to disable browser extensions, Adblocker, Firewalls and other tools which could modify the browser content in some way. (Or try to use a different browser and/or network, if possible, to further check where it breaks.)

If you are familiar with the browser devtools, you can check if there are any errors in the console showing up.

All the best,
Torsten

Simply think I’ll let Antispam Bee have a break.

Tried with different browsers (Edge, Firefox and Chrome), where all give the same result. Also tried both from home and via PC equipment at work.

Have had the product running on two different WordPress installations, where the problems are the same in both places.

Perhaps it is the PHP version that is the problem, which is something I have no control over myself.

Blog 1: https://web.brr.no/wordpress/ => PHP Version 8.1.12
Blog 2: https://www.brr.no/wordpressbrr/ => PHP Version 8.2.3 (Antispam Bee on break here, Zero Spam in use instead.)

Hi @brrasmussen

thanks again for reporting this to us! We can reproduce this on PHP 8.

It looks like our tests haven’t found this bug. I opened up an issue on GitHub for this:
https://github.com/pluginkollektiv/antispam-bee/issues/490

All the best
Torsten

Hi @brrasmussen

this is a bug coming only with 2.11.2. We fixed another bug and have missed that we broke this functionality.

See the GitHub link for more details.

All the best
Torsten

@zodiac1978 : Thanks for the response and the explanation!

With self::add_reasons_to_defaults(); out of the if-part it seems to work. Hopefully the next release will have a permanent fix included.

Hopefully the next release will have a permanent fix included.

Of course it will have a fix!

We found the bug, and it is fixed now on GitHub. Next release will come soon!