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.

[Mattikana]

Originally Posted by Lapsetur

I found the problem when I disable "Members who have visited the forum" it started work again

I also have this hack installed and my AE Detector hasn't worked for a while. Imho there's a big chance that this hack is interfering with the other one.

[AFemaleProdigy]

Wow! Installation was super easy and fast! Hope it works well too! Thanks!

[mtha]

It works great.

however, I need more information than that, so I create an other version of this hack, with multipleloginlog table in database (with option to use it), to store (userid,idstack,dateline,ipaddress,proxyip,userage nt,url)

No interface to see the log yet, only store to database, and you can check in the database to see the log.

[amcd]

This is wonderful, mtha. Exactly what I had been waiting for. Been wanting to do it for a long time but never got around to actually doing it.

I am installing it right away. Will give more feedback later.

[Snake]

Is this going to work just fine on 3.6.5?

[amcd]

Originally Posted by mtha

It works great.

however, I need more information than that, so I create an other version of this hack, with multipleloginlog table in database (with option to use it), to store (userid,idstack,dateline,ipaddress,proxyip,userage nt,url)


No interface to see the log yet, only store to database, and you can check in the database to see the log.

Its good, but analysing this table will not be easy as all the ids are not stored in the userid column. Some of them are in the serialised array only, and that is not indexable.

Also, if a person has more than 2 ids, it is creating multiple records for that person.

I think it would be more fruitful to store one record for each id/cookie combination. Lets say userid 1453 logs in with cookie 78, then the plugin should store 1453 and 78 if such a record does not already exist. Later when the user logs in with id 1782 and the same cookie value, this should be recorded as well.

Now when we have to check if userid 1453 has any alter ego, we just run a query where cookievalue=78.

The advantage of this scheme would be that even shared ids would be tracked.

[Dream]

Just thought important to say, I like the no soup for you :P

Also this mod is working nice, although it was just a guy that registered twice and a couple that uses the forum on the same computer.

[Mrdby]

love it!!!!

[redtailboa]

Does this still work if a user logins then logs out, and clears cookies?

[MPDev]

If they use the vB cookie clearer, yes; if they clear their own cookies manually, no.