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
This has been an amazing modification that's been of huge benefit to ensuring quality in my community.
I wonder if I could suggest a tiny modification/addition - that perhaps a means of recording the useragent for each login by a user, that way you could also have a means of detecting multiple logins by users who clear their cookies but still use the same browser.
It might be a tall order, but if you yourself (or someone else) thought of doing this for vb4, I for one would be more than happy to throw some dollars into the pot.
Everyone who uses 1 version of 1 browser will have the same user agent- how could that help in detecting AE's? There's only a handful of popular user agents out there and millions of people with each.
Now Evercookies on the other hand would be a big help... (I saw someone post this in another thread and it would be a great addition to this mod.)
Hmm , could be issue with this in 4.1 , found 8 members today with all the same ip address , one one warning from this . Its been great up until now but could be the end
Before the upgrade, I disabled all plugins/mods. When I was finished with the upgrade, I merely turned this one back on. It works fine - no probs at all.
Wish it was as simple as the other kagillion mods I have to re-install