raharakhte

Not a problem, cloudhopper!

I found the solution by accident, but when I did some digging around, I think I found out what caused it in the first place. In a comment at BAStat’s home post at Asymptomatic, of all places, staring us in the face for the last month. (That link points right to the relevant comment.) Someone found that this field was set up to be unsigned in the BAStats.php file. By altering the file at the section described in the link above, you should get a setup that stops this behavior.

A little further down among those comments, Owen seems to find this fix workable, with a reasonable caveat:

The method described for changing the default seems reasonable if you have some knowledge of PHP.

Dona€?t come running to me when you screw the pooch….

I found what, I hope, has turned into an instant, quick, and easy fix for this problem, even to the point that it revealed the already-logged 255.255.255.255 IP addresses in their proper form. Perhaps this will be useful to some out there.

In your databases, check the wp_bas_visitors table’s visit_ip field. In my database, this field was unsigned. I simply changed this attribute, setting it to the blank item in the drop-down. Hey presto! This instantly revealed the masked IPs and, up until this point–maybe a half hour later–the 255.255.255.255s have not returned.

Now, let’s hope that this didn’t open up a whole new can of worms, eh? ??

Posted to the wrong thread. Apologies. ??