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.
i dont know why but it messed up something in my forum so users and i couldnt login. i had to first disable all products by config.php and delete it. after that i enabled all products.
Add me to the list. I've seen a user reported under the same account multiple times "usera" is sharing an account with "usera." I've also seen a user reportedly sharing an account with a user who hasn't logged in for years (before I installed the mod). The only possibility I can think of is a corrupt cookie unless there is a bug or incompatibility (I'm using 3.6.5).
-vissa
I'm on 3.6.7pl1 btw. I like the pairs/couples whitelisting idea, too
I'll hold off installing this until MPDev has had a chance to check it out with vB3.6.8 but it looks like an excellent mod .
Are there any significant changes between 3.6.7 and 3.6.8 that would lead you to believe that this mod might not work? There should be no reason why this mod will not with future versions of VB, there is no need for MPDev to test it with every single new version before people install it.
Quote:
Originally Posted by bulbasnore
I'm on 3.6.7pl1 btw. I like the pairs/couples whitelisting idea, too
I just wanted to make a comment about the pairs/couples whitelisting idea that has been suggested on this thread. In the forthcoming version I have decided not to implement this feature. Why not? There's no easy way to offer it via a user interface. The old (current) version exempts users by way of a list of userids in the vbulletin settings. However, this quickly becomes problematic if you have a big forum and big list. The forthcoming version exempts users via a field in their user record.
I can't think of any other way to implement the pair idea, without resorting to a manually entered list of userid pairs, which I decided not to do for the reasons listed above. Exemption of the users on an individual basis is the compromise.
Are there any significant changes between 3.6.7 and 3.6.8 that would lead you to believe that this mod might not work? There should be no reason why this mod will not with future versions of VB, there is no need for MPDev to test it with every single new version before people install it.
I only said that because he said he would give it a test on the new version once he'd had a chance to upgrade and I'm in no rush so what does it matter? Some people have been reporting bugs since 3.6.8, just read the last couple of pages.
Multiple account login detector (AE Detector) Details »»
About Developer
Visit Web Site
No support by the author.
08-16-2007, 07:31 AM
.
