At first, this release
should be important for those who tired
of massive spam registrations, which can't be avoided even if Captcha module is installed, or some other protection tool (China still has lots of 1-buck workers to complete this manually). Spammers usually have registered insignificant accounts, but having Website field provided, or even other Profile-related fields filled in with URL-values.
Despite these URLs are active only for logged members, and inactive for guests and search engines, this version of miniBB provides a solution to avoid this behavior. We still support the Website field, considering it is important for "normal" posters who will get some "profit" from their useful postings; but the solution doesn't allow to fill this field in, until a member has been made more than '$allowHyperlinksProfile' posts on forum. '$allowHyperlinksProfile' can be defined differently, or it is equal to '$allowHyperlinks' value by default.
The approach works that way:
1) when registering an account, it's not possible to provide Website field's value; and if it has been provided, the script will not allow to register an account;
2) when editing the Profile, it will be possible to provide the value for the Website field only having at least '$allowHyperlinksProfile' total posts made on forum;
3) if member's topic or message has been deleted, and now this member has less than '$allowHyperlinksProfile' of total posts, the Website field will be nulled
automatically (so the spammer has no chances to keep this link after his bulk postings were deleted);
4) There is a basic function coded to protect other text-type fields of the Profile to not have possible to insert 'http', 'www' or 2-4 letter char followed after dot (single domain).
This solution came from the suggestional thread
of one of our members: and it has been proved to work on miniBB forums for about two weeks - now it seems I'm truly happy with it, because it also stopped bulk registrations for miniBB forum.
Other minor updates of this release include few non-critical bugfixes and polishing updates. Follow Updates History
for details (check below the file, as usually).
Make a backup of your database and files before upgrading!
And feel free to provide reports and comments in this thread.
Hopefully you all will feel safe with this release (like me) ;)