[mark370]

Originally Posted by Kiros72

Yes, I came across that issue (the first one) just recently as well. I think that it might be time for a small update to version 1.1.2.

The IP address issue might be caused by the user that you have set to post/send reports. That's also something that I was planning on fixing for 2.0.0, but since more than one improvement can be made in short order, I'll probably release version 1.1.2 sometime soon.

1.1.2 won't fix the past IP address matches, but it will keep it from happening again.

Funny you should say this as we have all the reporting coming from the S-Admin account which is also one of the accouts that is mainly showing up in the Ip search results problem

Question: Is there any sql cmds or something that we could do to clear/ reset all the ip's ready for the 1.1.2 fix so we can get the search back to normal again ?
because how it is at the minute its very hard to distinguish between members who have genuine accounts and who have multiple accounts as we could be repremanding members who are showing to have multiple accounts through ip search.

thanks for your help Mark