Missing panels after update to 3.4.2

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/xxxxxxx/public_html/wp-includes/functions.php on line 3017

WP SlimStat doesn’t use has_cap, so that must be from another plugin. The issue is however affecting only very few users, and we are not being able to replicate it on our dev environment.

Do you have access to your webserver error logs to see if that gives you any clues?

Two different types of error I can see easily.

[03-Dec-2013 11:38:29 UTC] PHP Warning: wp_slimstat_reports::show_rankings() [wp-slimstat-reports.show-rankings]: Node no longer exists in /home/xxxxxxx/public_html/xxxxxxx.com/wp-content/plugins/wp-slimstat/admin/view/wp-slimstat-reports.php on line 782
[03-Dec-2013 11:38:29 UTC] PHP Warning: number_format() expects parameter 1 to be double, string given in /home/xxxxxx/public_html/xxxxxx.com/wp-content/plugins/wp-slimstat/admin/view/wp-slimstat-reports.php on line 803
[03-Dec-2013 11:40:17 UTC] PHP Warning: number_format() expects parameter 1 to be double, string given in /home/xxxxxx/public_html/xxxxxx.com/wp-content/plugins/wp-slimstat/admin/view/wp-slimstat-reports.php on line 809'

[29-Nov-2013 10:19:56 UTC] WordPress database error Incorrect key file for table ‘/var/mysqltmp/#sql_d5951_5.MYI’; try to repair it for query
SELECT t1.*, tb.*,tci.*,tss.*
FROM xxxx_slim_stats t1 INNER JOIN xxxx_slim_browsers tb ON t1.browser_id = tb.browser_id INNER JOIN xxxx_slim_content_info tci ON t1.content_info_id = tci.content_info_id LEFT JOIN xxxx_slim_screenres tss ON t1.screenres_id = tss.screenres_id
WHERE t1.id <> 0 AND t1.dt BETWEEN 1383264000 AND 1385855999
ORDER BY t1.dt desc
LIMIT 0, 50 made by do_action(‘toplevel_page_wp-slim-view-1’), call_user_func_array, wp_slimstat_admin::wp_slimstat_include_view, include(‘/plugins/wp-slimstat/admin/view/index.php’), include_once(‘/plugins/wp-slimstat/admin/view/right-now.php’), wp_slimstat_db::get_recent ‘

Hm, the first group is what we fixed in version 3.4.3. I am going to run some tests.

But the MySQL error seems to be the real culprit. For some reason your database is corrupted.

You may want to look into that.

This is the code snippet we fixed in version 3.4.3. As you can see, all the values are cast to integers, so I don’t understand how that error message can be related to this release ??

if ($response->SD[1]->POPULARITY && $response->SD[1]->POPULARITY->attributes()){
	$attributes = $response->SD[1]->POPULARITY->attributes();
	$rankings['alexa_popularity'] = (int)$attributes['TEXT'];
}

if ($response->SD[1]->REACH && $response->SD[1]->REACH->attributes()){
	$attributes = $response->SD[1]->REACH->attributes();
	$rankings['alexa_world_rank'] = (int)$attributes['RANK'];
}

Well, after my earlier post I cleared every error_log in my install and went back looking at all the stats pages, and theres nothing showing up in any log. Every one is clear.

I’ll go and try repairing the db’s and see if that helps. Failing that I’d be prepared to allow you access to my cPanel if you’d like to take a look and see if you can get more of an idea what the problem is.

Just uninstalled slimstats, made sure the relevant databases were deleted, reinstalled the plugin – and still exactly the same, with no errors showing in any logs.

Going through the settings, in the maintenance tab there is now:-

WARNING: a misconfigured setting and/or server environment is preventing WP SlimStat from properly tracking your visitors.

(I’m pretty sure this wasn’t there before). Pointing my browser at admin-ajax.php gives a “0”

Could we be making progress? ??

Yes, all these clues point to a database issue.

Anything I can do to support the debugging? I am not as WP-savvy as Griff seems to be, so I’d probably need a bit more specific instructions, but I’m willing to help…
I’m really missing the stats…

AFAIK there have not been any significant changes to the DB on my server recently, so an external source of pain is quite unlikely.

TechnoViel, do you have access to your webserver error logs? Can you ask your provider to see if they notice anything strange?

The only errors to show so far are

[03-Dec-2013 16:45:25 UTC] WordPress database error Duplicate key name "resource_idx" for query ALTER TABLE xxxxx_slim_stats ADD INDEX resource_idx(resource(20)) made by do_action("slimstat_page_wp-slim-config"), call_user_func_array, wp_slimstat_admin::wp_slimstat_include_config, include("/plugins/wp-slimstat/admin/config/index.php"), include_once("/plugins/wp-slimstat/admin/config/maintenance.php")
[03-Dec-2013 16:45:25 UTC] WordPress database error Duplicate key name "browser_idx" for query ALTER TABLE xxxxx_slim_stats ADD INDEX browser_idx(browser_id) made by do_action("slimstat_page_wp-slim-config"), call_user_func_array, wp_slimstat_admin::wp_slimstat_include_config, include("/plugins/wp-slimstat/admin/config/index.php"), include_once("/plugins/wp-slimstat/admin/config/maintenance.php")
[03-Dec-2013 16:45:25 UTC] WordPress database error Duplicate key name "all_idx" for query ALTER TABLE xxxxx_slim_browsers ADD INDEX all_idx(browser,version,platform,css_version,type) made by do_action("slimstat_page_wp-slim-config"), call_user_func_array, wp_slimstat_admin::wp_slimstat_include_config, include("/plugins/wp-slimstat/admin/config/index.php"), include_once("/plugins/wp-slimstat/admin/config/maintenance.php")
[03-Dec-2013 16:45:25 UTC] WordPress database error Duplicate key name "all_idx" for query ALTER TABLE xxxxx_slim_screenres ADD INDEX all_idx(resolution,colordepth,antialias) made by do_action("slimstat_page_wp-slim-config"), call_user_func_array, wp_slimstat_admin::wp_slimstat_include_config, include("/plugins/wp-slimstat/admin/config/index.php"), include_once("/plugins/wp-slimstat/admin/config/maintenance.php")

That’s because you manually clicked on the ‘Add Index’ button under the Maintenance tab. Which shouldn’t have been there, but SlimStat is getting confused by the database problem (corrupt tables).

Ok Camu, I’m out of my depth now ??

Is it a slimstat db thats corrupt? If it is, wouldn’t deleting the plugin and its databases, then reinstalling have fixed the problem?

Apparently the database is not doing its job, and the new table is still corrupted.

I have scanned the error logs odf the last 4 days and not found anything related to wordpress or slimstat. All I see are files not found, access denied and the like.

Anything else I should look out for?

Can we confirm or exclude the chance that I have also have a DB problem?