No data for certain boxes

One of your tables may need to be repaired. You can do that via phpmyadmin.

Hi

Have done a total repair of all tables via phpmyadmin and status after that in phpmyadmin was OK but it didn’t solve the issue.

Any more idea?

See if your mysql error log can help. You may want to inspect it for errors related to WP SlimStat.

No error due to slimstat

What about the corresponding tables? wp_slim_browsers and wp_slim_screenres ? Are they empty?

Data exist in both tables

What tracking mode are you using? Javascript or Server Side?

Javascript

Do you have a caching plugin running on that site? Have you cleared the cache recently?

If you don’t, can you switch to Server-side and see what happens?

Cleared cache, not using any caching plugin, changed to server side. Still no data

Switch back to javascript mode and post your site’s url. I want to run some tests

Javascript mode is on and our url is https://www.mesas.se

Hi

I might found the issue, it’s query that don’t work:

SELECT t1.*, tss.* FROM ( SELECT tss.resolution, MAX(t1.id) maxid FROM wp_slim_stats t1 LEFT JOIN wp_slim_screenres tss ON t1.screenres_id = tss.screenres_id WHERE tss.resolution <> '' AND tss.resolution <> '__l_s__' AND (t1.dt BETWEEN 1388534400 AND 1393571676) GROUP BY tss.resolution ) AS ts1 INNER JOIN wp_slim_stats t1 ON ts1.maxid = t1.id LEFT JOIN wp_slim_screenres tss ON t1.screenres_id = tss.screenres_idORDER BY t1.dt desc LIMIT 0, 9999

As when I test above direct in phpmyadmin query function I get this error:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘BY t1.dt desc LIMIT 0, 9999’ at line 1

I assume this is the root cause: tss.screenres_idORDER BY ie its a missing blank befor ORDER BY that should solve it as it working via PHPmyadmin.

This issue goes for most of the boxes beside Top Users and Latest Users which dont get any data from db when I test both queries in phpmyadmin. I have data so it myght be an incorrect join or something like that for these 2 boxes.

Very good catch. This will be fixed in version 3.5.6. Thank you for pointing it out.

I wonder why that error doesn’t show up in your mysql log, though.