Paul was doing some misc work on the site earlier, it's still up but no worries just basic info ;).

Odd, you could temp redo cookie prefix in config, this way your pc will generate newly prefixed cookie for the site and pull current info, when done testing change back but in the meantime anyone who visits the site will have a new cookies generated with the alternate prefix etc.

It's sitting quietly in the background, perhaps doing something, but nothing has triggered as yet - BUT we are a relatively quiet Forum - perhaps our mischievous gentlemen have left us alone....

[s]Sadly a member using the same email address and the same ID had two accounts (a long-standing member so may have gotten on before same email switch was set) did not trigger the mod.[/s]

EDIT: Plot thickens : there was an attempt by the member to log in via an account that was banned a year ago - [s]so perhaps that's why it wasn't triggered?[/s]

It worked !

The banned account obviously set up the cookie and when the member tried with their main account it triggered the mod :thumbsup:

^^^Well, at least it confirms the decision a year ago - to ban the account ^^^^

;)

This member with two accounts was banned, sadly he created a further three accounts which were not detected.

If user knows what this mods looking for, he can avoid it. And that can be done very easily. As you probably know, cookies are easily controlled within any browser, just deleting all cookies, or if user is more technically inclined, deleting only cookies associated with site in question, disables this mod from knowing this user.

Usually the most annoying users learn this fact fast.

If someone would implement something like http://samy.pl/evercookie/ this would make deleting cookies harder, but not impossible.

Detector has never been wrong.

It's working properly now as it's still catching the usual suspects.

It caught someone logging in to all the Admin handles, which is concerning obviously.
https://www.sp411.cc/threads/198886-...ight=detection

How can this be?

Can anyone offer me any advice?

For PHP 7 compatibility all calls to split function should be changed to explode in product-ae_detection.xml.

I've been relying on this for years and years. Is anyone using this in vB 5 or something equivalent? we may be upgrading soon.

I have vB 4.2.5, php 5.6, and I'm very much afraid this has stopped working. (It worked in earlier versions of vb4 - I don't know whether it was the php or vB upgrade that killed it.) I would gladly pay to get it back. Anyone have any suggestions?