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 this use the ip address as a check? we have been running it for a long while now and has been working great but we 10 day banned one of our users and they came back and created a new account but the logon detector didnt flag the account (and we had another one that evening that was tagged so it was working). but we went in and compared the ip addresses and they were exactly the same so it was the same user.
just trying to figure out how somebody was able to get around the system.
does this use the ip address as a check? we have been running it for a long while now and has been working great but we 10 day banned one of our users and they came back and created a new account but the logon detector didnt flag the account (and we had another one that evening that was tagged so it was working). but we went in and compared the ip addresses and they were exactly the same so it was the same user.
just trying to figure out how somebody was able to get around the system.
They may have used a different computer or cleared their cookies....
WElp....This morning I woke up and found that it was working! LOL I know that 2 of my members are boyfriend/girlfriend so they now just happen to login on the same computer! Tripped it like a champ!!
Had it for 3.6.7 worked great...upgraded to 3.6.8 and I can't get it to work. No clue why.
I am running 3.6.8 - just installed the two xmls. nothing. I tried
signing up as a duplicate account, it bypassed my IP, no block,
no PM, no nothing, let the account right on in....
Multiple account login detector (AE Detector) Details »»
About Developer
Visit Web Site
No support by the author.
10-12-2007, 03:06 PM
