There are no differences as this plug-in works with the 3.5, 3.6 or 3.7 releases 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
It wouldn't pick up a user who clears their cookies or blocks them; or is using multiple computers. And clearing all cookies when you logout DOES NOT remove our cookie.
We didnt clear or block cookies and i cant get this hack working
This hack dont work at all for me and im not a vbulletin newbie
Me and my friends both tried this and it wont work.
i made 2 accounts and logged into both - no dupelicate account report
my friend made 2 accounts and logged into both - no dupelicate account report
Mine originally stopped working back in 3.6.8. But on one of my forums it worked fine in both 3.6.8. and 3.7.2. There's some other factor at work besides vb version.
Those are only the 10 that have stuck around hoping for a fix. And there's also a lot over in the 3.6 thread.
But clearly there's no simple answer. It's not just a matter of updating for 3.7. And, since when it stops working it doesn't work for anyone on the board, it seems to be some sort of server issue(?). I mean, if it was firewalls then some could trigger it but others couldn't.
Again, on one shared server mine stopped working in 3.6.8, and still doesn't work in 3.7.2. On a different forum on another shared server it's always worked fine in 3.6.8 and now works fine in 3.7. Very mysterious.
I wish it would stop working for Paul M or someone that knows anything about coding, because I have no clue what's going on, and it could be a simple option somewhere disabling things.
Multiple account login detector (AE Detector) Details »»
About Developer
Visit Web Site
Uses Plugins 
No support by the author.
08-10-2008, 05:58 AM
