Disabled Burst Statistics but it is still generating error logs

  • Resolved webinclusion1

    (@webinclusion1)


    4 months, 3 weeks ago

    I have had Burst installed on one of my sites but then I noticed it was generating a debug log error on a regular basis and taking my debug.log file to over 20Mb in a short space of time.

    I have disabled it and stopped all statistics, but it is still generating debug log entries like below.

    How is that possible after I have deactivated it? – Please can you help me to remove Burst entirely so it no longer tries to record anything, and stops writing entries to the debug.log…?

    [02-Jul-2024 09:37:57 UTC] Burst Statistics: Failed to determine hit type.
    [02-Jul-2024 09:37:58 UTC] WordPress database error Table ‘azfreight.wpgx_burst_goals’ doesn’t exist for query SELECT * FROM wpgx_burst_goals WHERE status = ‘active’ AND server_side = 0 made by burst_beacon_track_hit, burst_track_hit, burst_prepare_tracking_data, burst_sanitize_completed_goal_ids, burst_get_active_goals_ids, burst_get_active_goals, QM_DB->query
    [02-Jul-2024 09:37:58 UTC] WordPress database error Table ‘azfreight.wpgx_burst_statistics’ doesn’t exist for query select ID, session_id, entire_page_url, time_on_page, bounce
    from wpgx_burst_statistics
    where uid = ‘17189cf3400a005b727b1131d12842a2’ AND time > ‘1719911278’ AND entire_page_url = ‘/my-account/az-messages/’ ORDER BY ID DESC limit 1 made by burst_beacon_track_hit, burst_track_hit, burst_get_hit_type, burst_get_last_user_statistic, QM_DB->query
    [02-Jul-2024 09:37:58 UTC] Burst Statistics: Failed to determine hit type.

Viewing 1 replies (of 1 total)
  • Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @webinclusion1 if the php in the plugin still runs, the plugin is not deactivated, because that’s how WordPress is built. If you see logs from the plugin, it is still activated.

    Some possible causes for this:
    – The plugin was installed twice (with a different folder name perhaps), and one is still active.
    – Deactivating the plugin did not complete because of the missing db table, and the plugin is still active.
    – It is a multisite environment, and the plugin is still active on a different subsite.

    To make sure the code cannot run anymore, you can delete the plugin folder from your server using a file manager or FTP (e.g. FileZilla). Then go to directory wp-content/plugins, and delete the folder ‘burst-statistics’.

    If the code is not there anymore, it can’t run.

    If you need more assistance with this, let me know!

    Regarding the PHP error you see: the error shows the database table was not created properly. This can be caused by hosting restrictions (not allowed to create tables by your host) for example. If there is no such restriction, updating the plugin will often resolve the issue because it runs an upgrade procedure.

    Lastly: it is best practice to disable debugging on production websites, and use debugging only temporary when looking for a specific issue. This prevents large log files, and is a better security practice.

    Hope the above helps, and if not, I’m here to help!

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.