Administrative and Maintenance Tools - Multiple Account Detection & Prevention

It happens all of the time. Some members will make multiple accounts to back their own opinion or get an extra vote in a poll. Here's a modification that will detect and prevent multiple accounts, as well as notify the administration about multiple accounts. Inspiration for this modification came from the work of MPDev (creator of the Multiple Account Login Detector) and randominity (creator of the Multiple Account Registration Prevention). This is basically a combination of those two modifications but with new and improved functionality.

This is not an update to the "Multiple Account Login Detector (AE Detector)" nor is it an update to the "Multiple Account Registration Prevention." If you have either one of these (or both of them) installed, you should uninstall them before installing this modification.

With the initial release of Multiple Account Detection & Prevention, I believe that I have fixed previous bugs/complications as well as improved the efficiency and logic of the code. This is my first publicly released modification. I would appreciate any comments and suggestions!

Confirmed! This works perfectly on all vBulletin 3.6, 3.7, and 3.8 versions.

Unfortunately, I cannot give support right now. I may be able to help periodically, but until my schedule yields some more free time, I won't be much support. Please check back in a week or two.

Basic Details
File Edits: None
Template Edits: None
New Files: 6
Hooks/Plugins: 3
Global Phrases: 36
Install Time: 2 Minutes or Less
Install Difficulty: None, Very Easy

Features and Settings
- Login Detection
- Registration Prevention (Multiple Methods)
- Ignore Child Accounts
- Ignored Users
- Ignored Usergroups
- Ignored ISPs
- Prevention Usergroup
- IP Address Based Prevention
- Extended IP Address Prevention
- IP Address Time Inclusion
- Banned Account Check
- Primary Banned Usergroup
- Cookie Expiration Time
- Cookie Refreshing
- Cookie Name
- Cookie Reset
- Multiple Account Reporter
- Reports via PM
- PM Report Recipients
- Reports via New Thread
- Forum for Report Threads
- Verbose Mode
- BB Codes: LIST, URL, CODE

How it Works
With every newly recognized login/registration, an account-counting cookie is set (or added onto) with the member's User ID. Depending on the settings, Multiple Account Detection & Prevention will analyze the cookie during login/registration to see if there are any multiple accounts.

Login Detection offers cookie-checking and reporting. Registration Prevention offers the same thing, plus more advanced features. First of all, when it prevents an account from registering, it actually moves the registrant to the Prevention Usergroup so that the administration can review the case. This also allows for customized privileges for recognized multiple registrants. Registration Prevention also has IP address detection which finds out just as much information about users. Depending on an administrator's preference, this modification can also reban a new registrant if one of their previous accounts has been banned. In fact, if the administration wishes, multiple registrants can simply be denied registration all together.

Whenever there is a detection/prevention, the modification will report the information to the administration through private messages, a new thread, or both (depending on settings). The Multiple Account Reporter can be any valid user.

Known Issues
- vB Optimise users: Reporting via thread seems to get messed up by vB Optimise, so try reporting via PM instead.
- PhotoPost vBGallery users: The registration handling appears to not work properly when PhotoPost vBGallery is enabled.

From what I can tell, these known clashes have been caused by the other modification's coding. The author of vB Optimise will not even work with me to fix it. Until they improve their coding, I'm not sure if I can do anything about these issues. As far as I know, administrators that do not use the above modifications will not have any problems.

Installation / Upgrade
Unzip the package (madp.zip), upload the files to your forum location, and import the product file (allow overwrite if upgrading). Please read the ReadMe.txt file that is packaged with the modification for more information.

Please remember to mark this modification as installed if you use it!
If you like it, nominate it for the Mod of the Month!

Thank you!

[Kiros72]

I'll be releasing version 1.1.0 as soon as possible, but I'd like to get all of the bugs worked out prior to doing so. This means that I'll be doing extensive testing.

I think that I can confirm this bug. It seems that I released version 1.0.3 too soon.

I'll release a fix (version 1.0.4) within 24 hours.

[Sagua]

After I installed this add-on I try to log into my account or any user I get this code:
Warning: require_once([path]/madp/detection.php) [function.require-once]: failed to open stream: No such file or directory in [path]/includes/functions_login.php(185) : eval()'d code on line 3

Fatal error: require_once() [function.require]: Failed opening required '/home/doncubac/public_html/foros/madp/detection.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/doncubac/public_html/foros/includes/functions_login.php(185) : eval()'d code on line 3

Can somebody tell me what I did wrong or what can I do to fix this problem. Thank you for any help.

[Total666]

Originally Posted by Sagua

After I installed this add-on I try to log into my account or any user I get this code:
Warning: require_once([path]/madp/detection.php) [function.require-once]: failed to open stream: No such file or directory in [path]/includes/functions_login.php(185) : eval()'d code on line 3

Fatal error: require_once() [function.require]: Failed opening required '/home/doncubac/public_html/foros/madp/detection.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/doncubac/public_html/foros/includes/functions_login.php(185) : eval()'d code on line 3

Can somebody tell me what I did wrong or what can I do to fix this problem. Thank you for any help.

did you place the madp folder into your forum root directory ?? For example forum / madp ??

[Sagua]

I did 2 steps only

1) Upload the contents of the 'upload' folder to your forum's root.
(If your forum's location is http://www.example.com/forums/, the root is /forums/)

2) Import the product XML file (product-kiros_madp.xml) into the Product Manager within your AdminCP.
(When upgrading, always make sure that Allow Overwrite is set to yes!)

do I have to make any config to make it work?

[Mr Peabody]

Very very nice mod I hope support continues for many moons to come

[Kiros72]

Originally Posted by Sagua

I did 2 steps only

1) Upload the contents of the 'upload' folder to your forum's root.
(If your forum's location is http://www.example.com/forums/, the root is /forums/)

2) Import the product XML file (product-kiros_madp.xml) into the Product Manager within your AdminCP.
(When upgrading, always make sure that Allow Overwrite is set to yes!)

do I have to make any config to make it work?

No, that should work just fine. But it really looks like you uploaded the /madp/ folder to the wrong place. Either that, or it has the wrong permissions set.

Please be certain that you've uploaded everything INSIDE the 'upload' folder, and not the 'upload' folder, itself. If you go to your forums, you should be able to go to (website.com)/(forums)/madp/index.html and get a blank page without warnings if you have it correctly set up.

[Sagua]

Originally Posted by Kiros72

No, that should work just fine. But it really looks like you uploaded the /madp/ folder to the wrong place. Either that, or it has the wrong permissions set.

Please be certain that you've uploaded everything INSIDE the 'upload' folder, and not the 'upload' folder, itself. If you go to your forums, you should be able to go to (website.com)/(forums)/madp/index.html and get a blank page without warnings if you have it correctly set up.

I have solved my problem thank you very much :up :

[yagane]

Originally Posted by Kiros72

I think that I can confirm this bug. It seems that I released version 1.0.3 too soon.

I'll release a fix (version 1.0.4) within 24 hours.

Hi Kiros!!!

Version 1.0.4 Installed, I should have some fishes on the MADP in around 24 hours. I let you know the results. I setup the Prevention Group to 3 again on my settings, so they should activate they account and don't got a clue that has been catch.

Thank you very much for the update.

Best regards!!!

[Kiros72]

Alrighty, cool stuff. Just keep in mind that if you normally have your members confirm their email address, then their Usergroup will be changed to 'Registered Users' whenever they click on the activation link. If you want to prevent this, use a different Prevention Usergroup.

[yagane]

Originally Posted by Kiros72

Alrighty, cool stuff. Just keep in mind that if you normally have your members confirm their email address, then their Usergroup will be changed to 'Registered Users' whenever they click on the activation link. If you want to prevent this, use a different Prevention Usergroup.

Hi Kiros!!!

Yep, that's why I setup that Group (3), the users can activate the account, and all works normally, but the Thread send by the MADP alert all the staff and moderators about this account.

I have a secondary configuration, just in case the forum is attacked, in that case the Prevention Usergroup goes to a group with the Miserable Users mod, in that way I buy some time.

I think this mod is awesome, save a lot of time to the admin and pretty useful to all size of forums.

EDIT: Checked... Tested... All working great. Thanks Kiros.