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.
This is the same plug-in as the one found in the 3.5 forum; just cross-posted here for the benefit of 3.6 users.
If for some reason your userids change - weather you reinstalled, started over or whatever; the best way to avoid getting false reports based on the users old userid is to edit the name of the cookie used by the AE Detector:
In Plugin Manager under the login_verify_success section edit the AE Detector: Login checker plug-in code.
Change each instance of "IDstack" to some new name for the cookie to be used. There are four of them all in the first 21 or so lines of the code.
Multiple account login detector (AE Detector) Details »»
About Developer
Visit Web Site
No support by the author.
09-05-2006, 04:13 PM
