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.
Just for the mentally impaired, what this mod does is shows if 2 or more member accounts log in from the same IP address (implying that they are hydra's)? Is this correct?
if you have it set to check for ips, it will pm you and open a thread in the forum you like if you've set it to. for people with dynamic ips, you'll possibly get some false positives.
I have tried to make it trip off. I have not ever had it to report anything. I have went to different computers and made new accounts and then loged in and nothing happens at all. Any ideas?
it's checking for cookies, so making two accounts with two different computers would not trigger this. the multiple account reg hack checks for these cookies and also hits for the same ip, which could trigger it if you were not using an account from an exempted user group like admin.
I tried to import the .xml from my local computer, but my vB admin keeps telling me "No file uploaded and no local file found." When I enter all of the product information, it seems to import correctly but it doesn't update the vBulletin Options list with the product option link. Anyone else run into this issue?
Enable New Thread Creation on Multiple Login Detection? -> Yes
Then when some user will be "tripped AE detector" and a new thread will be created, then that post/thread will be created with IP address of that user "tripped AE detector"!
Then if you will search for your user's id=1 posts you will see many users had posted from your account of user id=1.
To avoid this one always create a BOT user on forum and set Userid of who PM sender / Alert poster -> Bot's User ID!
it's checking for cookies, so making two accounts with two different computers would not trigger this. the multiple account reg hack checks for these cookies and also hits for the same ip, which could trigger it if you were not using an account from an exempted user group like admin.
This cleared things up for me. I don't know why but I thought this checked multiple logins to the same account.