[OzzModz] Registration Spaminator 2.2.0 Patch Level 1

Fixed JS errors on XF 2.3

2.2.0
Out of beta
Now working with XF 2.2 and 2.3

WARNING, WARNING, WARNING!!!!!!!!!!!

Now That Ive got your attention:
This is a beta release, take a full backup before installing on a production site. Optimally try it out on a test site that is a replication of your live site before installing on the live site. It has had limited testing.

2.2.0 Beta 1:

WARNING: This is a beta version with changes aimed at more efficient data storage and to comply with coding standards. Careful testing is highly recommended before use in production.

• IP addresses are now stored as varbinary(16), all previous data will be converted to the new format
• Added pagination to logs page
• Added logs filters by IP address, email, date
• Added option to automatically clean up the log
• Added button to clear the log (requires separate permission)
• Fix: use TINYINT column type to store data with Yes/No values

This update is to re add what was done here, https://snogssite.com/resources/ozzmodz-registration-spaminator.87/update/623/

Somehow there was a regression in the code and the removed info was added back. I think this was don by changing dev sites and not removing the info from the files. This update to remove my IP address from the log viewing permissions for the addon. This has been in the addon form the vB days and was there for me to view the logs if people were complaining about false positives with registrations.

This was brought to my attention about 6 hours ago, and is being immediately removed.

Added: Now will store and show the date in the log. This applies for new entries, older ones have no date.

Brought version up to 2.x match other products.
Changed: One of the template modifications to be compatible with an up and coming addon.

This is an update to remove my IP address from the log viewing permissions for the addon. This has been in the addon form the vB days and was there for me to view the logs if people were complaining about false positives with registrations.

It has been brought to my attention that this is unacceptable. So I have immediately removed the code from the addon and issued an update. This will not happen in any addons again.

Fixed: Added code to prevent the addon from being installed on XF version 2.0.x

An update to the Registration Spaminator system for XenForo 2.1+ has been released. Those that have purchased this add-on, please log into your account to download this update.

• Changed - Some of the fields and the CSS for them to harden the ability to ensure there are no false positives.
• Added - A new field to the log showing the User Agent. This is to help troubleshoot any false positives that might trigger the addon.

This is a semi major update. I suggest taking a backup before upgrading just to be safe.

I am really happy with the new look of the log, and I am pleased with the results of the new traps.

Removed

• Some unused phrases that were left over from previous fields and such.
• Unused code in some of the PHP files.
• Some de-funked template modifications

Changed

• The ipaddress column in the database from 15 characters to 45 to accommodate ipv6 addresses.
• The website_code column in the database from CHAR 100 to VARCHAR 2500 to accommodate longer URL's.
• The display of the log. made it more user friendly and easier to read. there ane now checkmarks if a field was filled in, and a X if it was not filled in.
• The way the captcha is displayed in the log. It will now show a checkmark if a bot filled it in, and a X if it did not. If the field was filled in, you can click on the dropdown arrow to open it and see what the bot actually filled in the field. The new location trap also uses this same display. This was done to get rid of the extra noise on the initial display of the form.

Added

• A new trap for a location. Most of the bots are filling this in with a URL.
• Another new trap for a security question. It is a multiple select field that the bots just can not resist.
• The password confirmation field back to the registration form. Change this time from before is the password is not recorded in the database, only if it was entered or not. Also a user will not be rejected if the password field is filled in, this is to ensure someone using an aggressive auto form filler (such as LastPass) will not get rejected if it is auto filled in. This is now just an additional check to ensure it is a bot submission with the other traps filled out.