Please check your mysql error log and see if you can find any errors related to SlimStat in there.
Here’s what I got from the MySQL admin:
The error logs are not showing any errors related to your DB.
The table “wp_slim_browsers” contains just a single record.
Apparently something is not working when the tracker tries to insert new rows in that table. Could you try to insert a new row manually via phpMyAdmin?
Same problem here. I also tried to reinstall the plugin (after deleting the wp_slim* tables in the MySQL database). Manual inserting of rows in wp_slim_browsers is possible. But it stores only once the first browser and shows that for all access informations. Changing the tracking mode makes no difference. Also changing the design to a standard WordPress theme doesn’t help.
We would really like to investigate this issue. Could you please contact us at support.getused.to.it ?
Thank you so much for your time today. We were able to identify the glitch, and a fix will be added to 3.5.9! In the meanwhile, a temporary workaround is to run the following SQL query in phpMyAdmin
ALTER TABLE wp_slim_browsers MODIFY browser_id SMALLINT UNSIGNED NOT NULL auto_increment
I have the same thing and I also have a scrambled mess when I look at Slimstat Activity Log using Firefox 28.0. It looks nowhere the same in Firefox as in IE. Note that in IE, the problem seems to be that only about the first 10 are showing of what the top bar says “Results 1-50 of 756” (with no scroll bar). When I view the same in Firefox 28.0, the Activity log shows “At a Glance” with colors running out of fields and a list of what looks like various posts from the blog along with a line showing various browser names. Looks not even remotely like the IE version (old version before last night’s total WP and Plugin update).
Also I am not a SQL whiz so I am reluctant to enter the above command (first obstacle being not knowing where to enter it!).
The statement must be entered as an SQL query on your DB, in PHPadmin. Your DB admin, or support at the hosting provider should be able to help.
@camu: Thank you for the great support today! I’ve implemented the change on the live system too and it works beautifully.
I got this error on my database:
SQL query:
ALTER TABLE wp_slim_browsers MODIFY browser_id SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT
MySQL said: Documentation
#1062 – ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry ‘1’ for key ‘PRIMARY’
Then I opened up PhpAdmin and I opened the variable browser_id for manual editing. Everything was set as described here with the exception of the column “Extra”. At the moment I selected the only pull-down option, “auto_increment”, it stated that the Default value of 0 (which was previously in the field) was invalid.
SQL query:
ALTER TABLE wp_slim_browsers CHANGE browser_id browser_id SMALLINT( 5 ) UNSIGNED NOT NULL DEFAULT ‘0’ AUTO_INCREMENT
MySQL said: Documentation
#1067 – Invalid default value for ‘browser_id’
Here is what I see for: browser_id
Type: smallinit(5)
Collation: (blank – empty field)
Attributes: UNSIGNED
Null: No
Default: 0
Extra: (blank – empty field – cannot change to “AUTO_INCREMENT” due to message invalid default value)
Indexes:
Keyname __Type__ Cardinality Action Field
PRIMARY PRIMARY 497 browser_id
browser
version
unique_browser UNIQUE 497 platform
css_version
type
You have entries with no or duplicate browser_id. Before running the query I posted above (which doesn’t have a default value, as you can see) you’ll have to get rid of those spurious entries.
Ok, I did this:
Went through the list for browser_id checking each record. I found about 12 entries that had a number set for browser_id and the only other column populated was the Platform field. So for now, I have deleted every entry that was missing data in any of the fields except user_agent. About half of the entries appear to be missing that field, user_agent.
I went back to try to enable AUTO_ENCREMENT again and it failed again.
When I page down my browser_id table, I see the values for browser_id increment one count per line beginning at 0 and up until value 411 in the list, they all increase by a value of one count per line. Then at the point of reaching value 411, the value for browser_id begins skipping great series of numbers, first it skips up to like 425, 460, 499, then it gets very radical skipping hundreds of number at a time and finally stopping at 1950.
Should I delete all the records that are not incremental counts of one, and will that allow me to set the AUTO_ENCREMENT value without receiving the error:
SQL query:
ALTER TABLE wp_slim_browsers MODIFY browser_id SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT
MySQL said: Documentation
#1062 – ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry ‘1’ for key ‘PRIMARY’
Okay, do this before the alter table:
DELETE FROM wp_slim_stats WHERE browser_id <= 0
and
DELETE FROM wp_slim_browsers WHERE browser_id <= 0
Then run the ALTER TABLE:
ALTER TABLE wp_slim_browsers MODIFY browser_id SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT
That worked, thank you! But FYI, the number skipping starting at record 411 still exists and I say that only in case it means anything to your application. Otherwise the value did change to AUTO_INCREMENT with this bit of instructions, and this appears to have fixed the problem, even in Firefox!
Thanks again – love your plugin!!!!!
