How can I reset the past tracking data?
can be a solution change che name of the cookie?

i am interested to see if it will work on 3.8.3 as well. i just installed a fresh forum and am hesitant to install w/o confirmation of this working.

Have you read the description?
"Confirmed! This works perfectly on all vBulletin 3.6, 3.7, and 3.8 versions."

Have you read the previous page? Or even the product xml? Or quotes from people w/ 3.8.3? Read before you type.

Are you absolutely certain that you didn't change any settings or install/uninstall any modifications immediately before or after you upgraded to vBulletin 3.8.3?

Yes, if you would like a "clean slate" all you need to do is change the cookie name.

This modification's plugins do not alter any database information, so it wouldn't do any harm to install it. I haven't known vBulletin to release any maintenance update that would affect thread-posting or PM-sending methods in such a way that the parameters or method names change. Seen as how I haven't had any other complaints that are related to this matter which I can recall, and over 500 people have it installed, I don't think that it's the upgrade to vBulletin 3.8.3 that did it. I could be wrong, but I'm more confident that it will work perfectly fine on vBulletin 3.8.3, just as it did on 3.8.2.

Thank you for noting that! :)

Unless I'm mistaken, there was only one person that claimed of a clash with vBulletin 3.8.3, which was on the previous page. And I'm not sure how the product XML file has anything to do with the compatibility of a new, minor maintenance release.

I'd like to assume that at least 1/5 of the 500+ installations is running on up-to-date vBulletin software. So that would be 100 people (maybe more, maybe less) that are probably running this with vBulletin 3.8.3. If only a single person posted anything about it, I'm doubtful that other people are having problems. My doubt is based on the numbers... But again, I could be wrong.

I'll be testing this as soon as I can get a vBulletin 3.8.3 test installation installed, which might take several days because the license needs to be renewed. Until then, feel free to install it and then uninstall it if it doesn't work properly. Also, please be patient.

Thank you,
Ben

Any updates about the implementation of banning previous created accounts and banning multiple logins ?

Not right now. I'm trying to get finances straightened up. The wake & funeral and other expenses cost about $8000, and my father didn't have life insurance, so I'm pretty much SOL at the moment and I don't have hours to dedicate to coding at the moment.

I use Multiple Account Login Detector currently. I have two questions:

1. Am I right in saying this is improved over that because a) it checks for ip matches too; and b) it can catch users at registration and move to a usergroup or disallow registration.

2. If I install this it will have to set its own cookies; does that mean it will take some time to be as effective as the Multiple Account Login Detector - because it tracks by cookie, and when first installed users dont have this cookie installed.

I'm just deciding whether its worth upgrading - thanks!

Thanks for this, working perfectly on 3.8.2, installed :D

Any reply to my question above - thanks! (apologies for the reminder!)

This has been answered in the thread already. And if you check by IP address as well, it'll start working automatically.

1. Yes and yes. It also has faster function calls (like explode() instead of split()) and personally, I think I have improved upon the logic of the original modification from MPDev. Also, there are far more options like the one that I discuss in the second portion of this response.

2. Nope. I made this modification to be backwards compatible, meaning that if someone had MPDev's login detector, MADP will use the cookies (named IDstack) that have already been set by it. This happens by default. However, the administrators can change the cookie name to be something else and the effect of such would be a "clean slate" for everyone. But it will resume tracking each login and registration. Remember, this is completely optional. By default, it will use the IDstack cookies that MPDev's login detector uses.

Glad to hear. Hope you enjoy it as much as everyone else is :)

Fantastic! Thanks Kiros you just saved me reading over 372 previous posts :)

By tracking "each login and registration", does this mean that on a clean install, each time an existing member logs in for the first time after this mod is installed, they will get a cookie with their login info, and then from that point forward if they were to create a second account, the mod would catch it?

I have installed this and I am using 3.7.0

It did work and was able to open it within the CP

Now I have an error when I try to log in to my CP

This is the error

Warning: require_once([path]/madp/detection.php) [function.require-once]: failed to open stream: No such file or directory in [path]/includes/functions_login.php(185) : eval()'d code on line 3

Fatal error: require_once() [function.require]: Failed opening required '/home/crimecas/public_html/forum/madp/detection.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/crimecas/public_html/forum/includes/functions_login.php(185) : eval()'d code on line 3

It is rather urgent that I can get access to my CP
I hope that anyone can help me.
even if you need access to my site I can give you tha?

Please Help

Regards
Ryan

Not a problem :)

Exactly, yes. As long as they use the same browser and don't clear their cookies, it will catch the second account, and the third one, and so on. If you enable IP address detection, they may be caught if they still have the same IP address.

Once again, this is the classic symptom of missing files. Make sure you upload everything in the /upload/ folder to your forum root. That means, if your forum is at www.example.com/forums/, then you should have the files uploaded at www.example.com/forums/madp/ because the /madp/ folder is within the /upload/ folder. Read the ReadMe.txt please.

Thanks Kiros for the nice mod. I was able to successfully trigger an alert PM with some test accounts. This is going to be a handy mod.

Glad to hear that :)

I will confirm this does work on 3.8.3 just fine. I have been running it for a few days now and have caught a few people. Works well.

Goodness, thank you! I knew there was something I was forgetting to do :o

That's a relief ^_^

Is this mod compatible with vBFirewall ? I'm getting alot of wrong detections and never used this plugin before and I can't afford to turn vBFirewall off to test.

Anyone running both of them ?

I've never heard of vBFirewall, and I don't see why such a thing would be necessary. vBulletin is pretty secure as is. But as you're having problems, I can look into it if you PM me with login details.

I have a question.. is there a way to set it up so that multiple users who have been banned previously are sent to a moderation usergroup, but those that haven't just get reported - no action is taken immediately. That's how I want to set it up - but I can't seem to find how!

Hi there, I have installed this on 3.8.2 to replace the original login detection only version.

I have tried several test forums accounts and I have found the registration alerts are working via pm and forum posting.

I have not yet had any login alerts.

I've done all the settings.

I also disabled vboptimise rather than remove for the moment.

I think it must be fine with optimised turned off because the register alert is working.

Is that likely or do you think I should just remove it comletely and then try?

many thanks for reading my request

Kiros, any update on my question? Thanks :)

Sorry, I was out of town for a little while. I haven't set up anything to operate like that, but I'll see what I can do in future releases.

If you tried testing the registration yourself, and then tried logging in with the same accounts that you registered, it wouldn't alert you. The modification is set up to only report new cases. For instance, if someone created one account on one computer, and another account on another computer, the registration would not be caught because of the virtual location difference. Now if that same person logged into both accounts on the same computer, the login detection would catch it because it didn't recognize the multiple account earlier during registration.

Let me know if you would like me to help you out.

Thanks Kiros - I know that we definitely want to ban multiple accounts (or put them in a moderation queue) who have previously been banned; and the rest can just be reported.

Have you considered enhancing the IP check by having some basic proxy detection? The Proxy IP to Real IP conversion being a base example of how you might integrate it (ie detecting the http variables and passing the real IP to be checked).

That would be great addition!

I already have proxy to IP. Am I correct that MADP and Proxy to Real IP work together?

Hi. I also use vBOptimise but doesn?t work correctly the reports with function move to usergoup (thread nor PM) :(

I use v3.8.3

I believe this has already been suggested. I have not gotten to it yet, but it is on my list of additions.

Sadly, I do not think that this works as intended. Unless the Proxy to Real IP modification sets the global IP address variable... I'll work to either make the two modifications compatible or to add a comparable internal functionality to my modification.

The author of vBOptimise never responded to my inquiries. So it looks like he/she doesn't want to cooperate with me to find a solution. I apologize for this inconvenience, but you may have to chose between a slightly optimized vBulletin or the functionality of Multiple Account Detection & Prevention.

I understand, thanks anyway :up:. I will use the function Disallow Multiple Registrants with no report.

Regards

Great because while this hack is very well done, if it can be easily bypassed by proxies and a cookie clear, it's not robust enough.

3.8.3 works beautiful - Thank You

Why? :( I got this msg 5 times.

Edit: Just got it 40 times overnight. Is it when someone logs onto the forums? =o

Would you consider supporting LSO cookies.

If you set an LSO cookie (they are set by flash) then a normal cache clear wont get rid of it, and they are persistent across sites.

Shouldn't have too much trouble playing off a small flash pixel in one corner which sets the cookie.

http://en.wikipedia.org/wiki/Local_Shared_Object

thank you, installed

Sorry, but I don't think that my modification is related to those errors. I see where the syntax is messed up, but without knowing where that query is coming from (the file, that is) then I'm not going to be able to help you out. =/

Well, I'm not flash coder, and from the looks of it, that would require more code and files and it would just make things more complicated. So for now and probably for years to come, I'm not going to be messing with LSO cookies. Sorry =[

Hi,

I turned off the registration preventation option since at the moment I want the app only to to detect and report duplicates without preventation.

However, the app reported today the following "The new account has been moved to the Prevention Usergroup" and moved it into the "COPPA users awaiting..."

I'm using VB 3.8.3.

Any advice?

Thanks.