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.
The update is that so far I've had only one beta tester from a very large forum. A few minor changes were made based on our experiences on that forum. I have had one other beta tester, but didn't hear from him again after I gave him the file.
Although my current beta tester is not using any of the advanced features (such as automatic notifications or automatic banning / suspending), I still feel that the code is quite solid. I haven't had time to write any of the front-end functions yet, but I hope to get to this in a couple of weeks.
I dropped in to see if anyone was having the same problem I'm having... I have a user who gets detected everytime as "thisuser appears to be using the same computer as thisuser". The userid is identical when you click the linked user names. Corrupt cookie?
I dropped in to see if anyone was having the same problem I'm having... I have a user who gets detected everytime as "thisuser appears to be using the same computer as thisuser". The userid is identical when you click the linked user names. Corrupt cookie?
I have also seen this a few times with a certain user and I have also seen it show the same user 3 times like this..
Quote:
user1 seems to have multiple personalities using user1 and user1 and user1 sharing the same computer.
I also just had this...
Quote:
user1 seems to have multiple personalities using user2 and Admin and user1 sharing the same computer.
I know for a fact user1 did not login as Admin...lol
Idea: It would be very useful to be able to exclude "user couples", not only users.
For instance, if I know for sure that user X and user Y login from the same computer but are different people (eg brothers), I will not want to put them in the whitelist, as each one of them might some day create a double account. So, I keep having new posts each time they login, which is quite annoying.
If that's difficult, what about just posting in the existing thread, instead of creating a new one, if the couple is the same?
Multiple account login detector (AE Detector) Details »»
About Developer
Visit Web Site
No support by the author.
07-17-2007, 11:47 AM
