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
do you know what the logic is? like how many days does it wait before it reports again ?
should be in one of the files perhaps the xml or another one, it might also be set to hours instead of days... If I have time later today I'll look and see else check it out yourself and learn something along the way
I've been using this mod for a quite long time successfully but I've noticed that some users (banned or not) are using proxies to not been detected and this mod has not so effective in detecting them.
I know some proxies available on the web refuse the use of cookies, or something like that and probably that's the reason this mod is not been effective.
May be you guys have some experience with the same situation as my self and probably has more suggestions on what would be the cause for it.
I know, some of the tough banned guys know they could be controlled by a cookie and they always clean their caches and some Anti-virus like Norton also detects and clean automatically tracking cookies very fast but I think someone here could have more ideas to make this mod even more efficient against those.
Not sure if it'll work properly on my version of vB (3.7.4) but it's a VERY needed mod with my forum. Unruley users are always sneaking back on using IP proxies.
Multiple account login detector (AE Detector) Details »»
About Developer
Visit Web Site
Uses Plugins 
No support by the author.
04-20-2009, 05:13 PM
