There are no differences as this plug-in works with both 3.5 and 3.6 versions of vBulletin.
If you are like me and migrated from .threads, a common modification was an "AE detector", a simple mod that saved a cookie of a history of ids logged into on your site. If someone logged into more than one account, you got a PM letting you know that your site was being accessed from multiple accounts.
Over the years this was very helpful in identifying users who were posting under multiple accounts (alter-egos!) and users who would return after being banned.
You might be wondering why I don't use the vbcookie call - well, thats because on logout all vB cookies are cleared, so we need to store a cookie that is not effected by the login/logout process.
New Installation
1. Add New Product with attached XML
2. Go to vBulletin Options -> AE Multiple Login Detection Settings and set your specific settings.
Time to install: Easy - 2 minutes.
Upgrade
If you installed this as a Plug-in manually, you can delete that plugin and install this Product, just make sure to go into the Options and set them accordingly.
I hope you find this useful and will click INSTALL if you use it; should it prove useful to enough people I can look at making this installation more automated without the need for edits and an Admin Options page.
To upgrade you will want to reimport this XML file and edit your options accordingly.
1.0.3
-----
. Added a check to ensure that users weren't deleted when reporting violations
. added htmlspecialchars_uni call to username
Note: I am unable to get the call to construct_phrase with $vbphrase['multiplelogin_alert'] to work reliably, as such the $message variable is still set manually inside the plug-in and not via the phrase. If anyone has an idea of why this might not always work, I'm all ears.
1.0.2
-----
. Updated to include exclusion groups, users
. Changed so PM is sent by ae sender id
1.0.1
-----
. Released as a Product (thank you PHPGeek2k3 for your help)
. Added option to post to a forum versus send a PM (or both)
. All settings moved into Admin Option
1.0.0
-----
Initial release.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
Does AED generate a report for every additional (2nd, 3rd, 4th, etc.) identity found? Or does it just identify the first pair of overlapping accounts?
Put another way:
1 - Problem member gets banned
2 - Problem member re-registers
3 - AED spots overlap and generates report
4 - Problem member gets banned again
5 - Problem member re-registers again
6 - Does AED generate another report at this point?
It seems that the admin userID selected to generate a report thread does so from the computer of the overlapping users. The IP of the overlapping users' computer appears for the admin userID.
Anyway to prevent the IP logging behavior?
Otherwise, using the ID of one of the overlapping users to generate the report thread seems more appropriate.
Sometimes you get a hubby and a wife that both post from the same computer.
What would really be cool is if there was a way to set it to post a usernote to both duplicate registration ID's automatically (john123 = Jane456). That way I dont have to got post a note on there to keep track of dupe registrations.
Another cool feature would be to query for all duplicates; ie: run a report.
For some reason this isnt creating a thread when I KNOW users have more then one userid, anyone explanation as to this may be happening? Im running 3.6.1
Multiple account login detector (AE Detector) Details »»
About Developer
Visit Web Site
No support by the author.
09-14-2006, 01:44 PM
