GreXXL on my prod 1.8 forum I have the following two extensions:
- FoF AntiSpam
** Delete user -> true
** Delete posts -> true
** Delete discussions -> true
** StopForumSpam -> various settings but I guess they are irrelevant since they concern registration
- Spam Prevention configured through the
extend.php with the following:
(new Spam\Filter)
->allowLinksFromDomain('youtube.com')
->allowLinksFromDomain('youtu.be')
->allowLinksFromDomain('pianoclack.com')
->allowLinksFromDomain('pianoclack.s3.us-east-1.amazonaws.com')
// How long after sign up all posts are scrutinized for bad content
->checkForUserUpToHoursSinceSignUp(24)
// How many of the first posts of a user to scrutinize for bad content
->checkForUserUpToPostContribution(3)
// Specify the user Id of the moderator raising flags for some actions, otherwise the first admin is used
->moderateAsUser(1)
// Disable specific spam prevention components
->disable(\Blomstra\Spam\Filters\UserBio::class),
When I copied and migrated the 1.8 copy to 2.0 beta 7 (and then upgraded to beta 8), I kept only the FoF Anti Spam which now merges both and it actually migrated properly the existing settings (e.g. the StopForumSpam token and the other UI settings), however it didn't copy the extend.php settings, which is understandable, so I configured them manually:
On my prod forum the spam prevention seems to be working great and it affects only newly registered users with less than 3 posts or within the first 24 hours.
Now, on the new forum, an old regular posted the following post which got auto-flagged and unapproved:
Just starting a thread in hopes that helps with any testing. Well something odd emerges right away: I cannot type enter (end paragraph). The enter key has a shift key functionality instead. This is on Android 10 on my phone. No such issue on the "production" forum instance. Cheers!
BTW, I think this is important and I already posted it above: in the "blocked registrations" tab in the extension settings, I can see some blocked registrations that are apparently old, however they are always displayed with the current time and date. When I reload the page, the time and date will be the actual time at the time of the reload. Furthermore, the paging is broken and it initially shows that there are 2 pages of blocked registrations, but when I click on the second page, it shows there are 3, etc. and there can be many. To me something is wrong with the time and date functionality of the extensions and I wouldn't be surprised if the extension somehow thought that the user above is a brand new user (posting in the first 24 hours) and blocked him due to short content?
Is it worth it removing the extension completely, purging its DB data and then try installing it clean? Because I think the migration might have caused some issues.