• Resolved Optimizing Matters

    (@optimizingmatters)


    When adding a filter (by clicking on a link in “top web pages”) and then removing that filter something breaks, leaving graph and data empty and spitting out an SQL error in the PHP errorlog;

    
    2018/03/05 15:50:09 [error] 984#984: *2623995 FastCGI sent in stderr: "PHP message: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '%s AND dt BETWEEN 1517702400 AND 1520268609' at line 3 for query 
    			SELECT COUNT(id) counthits
    			FROM wp_slim_stats
    			WHERE resource = %s AND dt BETWEEN 1517702400 AND 1520268609 made by do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, wp_slimstat_admin::init, wp_slimstat_reports::init, wp_slimstat_db::count_records, wp_slimstat_db::get_var" while reading response header from upstream, client: 94.109.180.81, server: autoptimize.com, request: "POST /wp-admin/admin.php?page=slimview2 HTTP/2.0", upstream: "fastcgi://unix:/var/lock/php-fpm-7.0-sftp_eej2maez:", host: "xyz", referrer: "xyz.com/wp-admin/admin.php?page=slimview2"

    Clicking on “reset all” fixes things.

    frank

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Jason Crouse

    (@coolmann)

    Hi Frank,

    would you be able to elaborate on how to reproduce this issue?

    Thank you,
    Jason

    Thread Starter Optimizing Matters

    (@optimizingmatters)

    sure:
    -> go to slimstat overview (works)
    -> from “top web pages” select a specific page (works)
    -> click on “remove filter for permalink”, resulting in breakage:

    the graph shows “no data to display” and an SQL error is logged in the php errorlog.

    frank

    Thread Starter Optimizing Matters

    (@optimizingmatters)

    well, I just did the same and … it works. no more SQL error, no blank graph. weird.

    Plugin Author Jason Crouse

    (@coolmann)

    Your browser must have cached the old javascript library. Good that this is resolved now! Also because we could not reproduce the issue on our end.

    Thank you for being on top of these things!
    Jason

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘SQL errors in php errorlog after update’ is closed to new replies.