Administrative and Maintenance Tools - Multiple account login detector (AE Detector)

Mod of the Month winner!
Top 10 most installed mods for vB3.6!

Same plug-in found here:

https://vborg.vbsupport.ru/showthread.php?t=107566

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.

[vitrag24]

i don't know reason but it's waxing and wanning.
initially it worked fine for few days then not..again now working perfactly..

[attroll]

Yeah, I am not sure if what I did was really a fix or if it actually just started working on it's own again. I am just glad it is working again.

[Noctavia]

Originally Posted by attroll

I will jump on the band wagon here to. This was working until I upgraded to 3.7.0. No it has not worked sense.

Me too. I've just had to clean up a mess that a returned (and irate) banned member created on the forums. I didn't even know who he was till I manually went through the IP addresses etc.

Looking for a working form, or an alternative.

[pmcnamara]

working here at 3.7.x

flawlessly.. love this mod.

http://www.sportsinferno.com

[TheLastSuperman]

Thanks! Installed today, tested and works like a charm (3.6.8)

[John_Shaft]

I've just discovered something pretty disturbing with this after using it for many months. It gave me one heck of a fright until I figured out this script was the cause. And that there was no threat to my board, just this script misrepresenting it.

Quite simply the posting IP of the report thread is set to the IP of the *Multiaccounter*.

So when doing an IP check on a months long poster now turned spammer my LOGIN NAME came up under his IP. Leaving me to think he'd hacked my Admin account. Thanks for the heart-attack and panic.

I verified this by previous multiaccounters.

IN NO WAY should a reporting post added under your username be assigned THEIR IP. It is extremely confusing and misleading and really messes up the IP check feature.

I really think this should be corrected.

[Videx]

There's a fix for this posted in the last page or two of the 3.7 thread. Basically changes the IP to 0.0.0.0.

[John_Shaft]

Thanks Videx. Glad I wasn't the only one worried by it and that it's fixed.

[Videx]

Actually, no, it hasn't been fixed I don't think. It's just that if you know to look back in the 3.7 thread you'll see a fix for it. But AFAIK the author has not yet included the fix in the download files.

[John_Shaft]

Ah yeah, you're right. But the fix seems simple and makes sense. I'm happy to use it. So thanks for the headsup, and hopefully we can save some others the unneccesary panic of thinking a multiaccounter has hacked their Admin account.

For those who want it, it's here, and is.

Originally Posted by Pottsy

In the xml, or in the plugin manager (AE detector), find:

$threaddm->do_set('visible', $visible);

And add after:

$ipzero = "0.0.0.0";
$threaddm->do_set('ipaddress', $ipzero);