BugWP logo BugWP
Back to Community
Home / Community / Plugin → Wp statistics – the most popular privacy-friendly analytics plugin

Resolving Common Issues After Updating WP Statistics

26 threads Sep 16, 2025 Plugin → Wp statistics – the most popular privacy-friendly analytics plugin

Content

Updates to the WP Statistics plugin are designed to improve performance and add new features. However, sometimes an update can introduce unexpected issues, such as tracking stopping, errors appearing, or data seeming to disappear. This guide compiles the most common post-update problems reported by users and provides step-by-step solutions to get your analytics back on track.

Why Do These Issues Happen?

Problems after an update can stem from various sources. A caching plugin might not have cleared its stored files, preventing the new tracker script from loading. A database schema change might not have been applied correctly during the automated update process. Occasionally, a specific setting may revert to its default state. Understanding the root cause is the first step to a solution.

Common Problems and Their Solutions

1. Tracking Stopped or "No Recent Data Available"

This is one of the most frequently reported issues. Your dashboard may show zero visitors and views after an update.

  • Clear All Caches: The most common fix is to clear every layer of cache on your site. This includes your caching plugin (e.g., W3 Total Cache, WP Rocket), server-level cache (if you have it), and your own browser cache. Caching plugins can sometimes serve an old version of the critical tracker.js file.
  • Check Tracker Diagnostics: Navigate to Statistics > Settings > General and click on Open Debugger. Ensure both Tracker.js Status and Hit Endpoint Status show as "Successful".
  • Database Maintenance: Go to Statistics > Optimization > Plugin Maintenance and check the "Check & Repair Database Schema" status. If it's not "healthy," run the repair tool. In some cases, you may need to click Reinitialize Now under Database Management.
  • Review Settings: After a major update, check your key settings haven't reverted to defaults. Pay special attention to IP detection methods, privacy settings, and tracker configuration.

2. PHP Errors and Warnings (e.g., "Undefined array key")

You might see technical errors on your site's frontend or in your debug logs.

  • Resave Settings: A very common fix for errors like "Undefined array key 'robot_threshold'" is to simply visit Statistics > Settings and click the Save Settings button without changing anything. This repopulates missing values in the database.
  • Manual File Replacement: For errors related to specific files (e.g., a warning about ReferralsParser.php or a missing source-channels.json file), the solution may be to manually replace a file. The WP Statistics team often provides updated files on their GitHub repository for this purpose.

3. Data or Menu Items Seem Missing

You might notice that a familiar data export or admin page is gone.

  • Menus Have Moved: The plugin's interface is occasionally reorganized. For example, the "Online Visitors" page was moved to a tab within the "Visitors Insights" menu. Look around the admin menu for new locations.
  • Data Tables Merged: For performance, older data tables are sometimes consolidated. The wp_statistics_visits table, for instance, was merged into other tables. Your data is not lost; it can still be accessed through the plugin's other export functions.

4. Conflicts with Consent Plugins (e.g., Borlabs Cookie)

If you use a consent management plugin, tracking might break because the method of tracking has changed.

  • Check Tracking Method: WP Statistics offers both Client-Side and Server-Side tracking. Consent plugins typically only manage Client-Side tracking. If your tracking method was switched to Server-Side during an update, you may need to reconfigure your consent plugin or switch the tracking method back in Statistics > Settings > General > Tracker Configuration.

Advanced Troubleshooting

If the steps above don't resolve your issue, deeper investigation is needed.

  • Enable Debug Logging: Enable WordPress debug logging by adding the following lines to your wp-config.php file above the /* That's all, stop editing! */ line: 
    define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
    After reproducing the error, check the wp-content/debug.log file for specific error messages that can pinpoint the problem.
  • Conflict Test: Temporarily disable all other plugins and switch to a default WordPress theme (like Twenty Twenty-Four). If the issue is resolved, reactivate your plugins and theme one by one to identify the source of the conflict.

By methodically working through these steps, you can almost always resolve issues that arise after updating the WP Statistics plugin. If problems persist, sharing specific error messages from your debug log is the most helpful way to get further assistance from the community.

Related Support Threads Support