We figured out what the issue was. Version 3.5.7 had mistakenly removed the auto_increment option from browser_id (wp_slim_browsers). Given the primary key constraint on browser_id, the tracker was failing to add new rows to the table (since browser_id was not specified in the INSERT). This was causing the insert to return 0. However, if the lookup table already had a match for a given user agent, then the corresponding ID was correctly returned.
Users who had started using WP SlimStat with version 3.5.7 (and thus had an empty wp_slim_browsers table), had all their pageviews associated to browser_id 0. Version 3.5.9 had a DELETE sql statement to remove those spurious lines, and that’s basically what happened. We have commented out the DELETE statement, and that takes care of the problem.
Unfortunately your pageviews recorded with version 3.5.7 might be gone. We really apologize for the inconvenience, and will make sure this won’t happen again.
