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.

[Videx]

Originally Posted by mark99

Out of interest, did you try the test on several different browsers?

No, I haven't gone so far as to try the test with multiple browsers.

I just wish I understood the code more, but I've looked at it and I swear I see no reason any update or other mod should interfere with this. Makes no sense.

edit: Okay, I just checked 3 browsers - IE6, Opera, and Firefox. None triggered an alarm.

[cynthetiq]

we just upgraded to 3.7.2 and we had several people having some other issues. With their permission I reset their password and logged in as them with FF. As I continued with other people, I got AE messages for each one. It's funny to trip them as staff didn't get how it could happen because they didn't know I was working on issues for people.

test it with regular accounts, not staff accounts. It works on all browsers as I've tested all 3 IE6, Opera, Firefox with no misses.

[Videx]

As in your case, one of the accounts I'm testing it with is a regular user account. I mean, both are my accounts, but one is the regular user I use to test things.

[cynthetiq]

that's my point, you can't use ONE regular account and ONE staff. Log on with TWO regular accounts.

It will NOT trigger any AE for a moderator, supermoderator or admin account at all.

I know this because we had a moderator abuse his position and we did not know all the alter egos he had created until we made him a regular user.

[Videx]

Okay, I just created a new user and logged in and out as him and my regular user. Nothing. I also tried turning off my shoutbox, as I read in another thread tonight a shoutbox was turning off some other mod.

I just realized I'm posting to the wrong thread, as the author has started a 3.7 thread here. I'll be trying to carry on there.

[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.

[obetyance]

on line 71 of product-ae_detection.xml, it says something like:

                            $subject = $vbulletin->userinfo['username'] . " tripped the AE detector";

now, I changed it to:

                            $subject = $vbulletin->userinfo['username'] . , $andids " tripped the AE detector";

hoping that it will show all the tripped members on the subject line instead of opening all the threads.

what happened instead... my admin panel site is not working anymore. how do i fix it please? I can' t login into my admin panel to undo my mistakes.

its says:
Parse error: syntax error, unexpected ',' in /home/fas/public_html/forum/includes/functions_login.php(185) : eval()'d code on line 56

Unable to add cookies, header already sent.
File: /home/fas/public_html/forum/includes/functions_login.php(185) : eval()'d code
Line: 56

Thanks so much for your help.

[Wired1]

Originally Posted by obetyance

what happened instead... my admin panel site is not working anymore. how do i fix it please? I can' t login into my admin panel to undo my mistakes.

its says:
Parse error: syntax error, unexpected ',' in /home/fas/public_html/forum/includes/functions_login.php(185) : eval()'d code on line 56

Unable to add cookies, header already sent.
File: /home/fas/public_html/forum/includes/functions_login.php(185) : eval()'d code
Line: 56

Thanks so much for your help.

This is why you don't edit code on live servers

Just go to the config file and add the code that disables plugins (can't remember it off the top of my head, just search for it here and on vb's site), and then you'll be able to login to the AdminCP again. From there, revert the code, undo the change to the config file, and you're back in business.

[obetyance]

Originally Posted by Wired1

This is why you don't edit code on live servers

Just go to the config file and add the code that disables plugins (can't remember it off the top of my head, just search for it here and on vb's site), and then you'll be able to login to the AdminCP again. From there, revert the code, undo the change to the config file, and you're back in business.

Thanks so much, sir. Found the solution here: http://www.vbulletin.com/forum/showthread.php?t=196688

Anyway, going back to my objective, is there a way we could make it? Show the tripped members in the SUBJECT line of each reported post/thread? Thanks!

[attroll]

I got this working again after reading this post in the 3.5 version of this hack https://vborg.vbsupport.ru/showpost....&postcount=109.