Hi,
I would also like to address that the “WP Statistics” plugin should at no circumstances logs deprecated warnings of other plugins/themes unless you really need it into the wp_options table!!
There should also be implemented an sensible size limit and frequency limit incase you need to debug this. Please set this to “disabled” be default, and add these options in the General Settings page of the debugger to enable these features when needed!!
In complicated WordPress installations will always time to time have deprecated functions and logging this is unnecessary unless debugging is really needed.
I have added an temporary filter
add_filter(‘wp_statistics_disable_tracker_debugger_logs’, function () {
return true; // Disables tracker debugger error logging
});
Please fix this!
Hello @horgster,
Thank you for sharing your detailed feedback and concerns regarding the wp_statistics_tracker_js_errors option.
We understand how a large autoloaded option can affect site performance, and we appreciate you taking the time to explain your case and suggestions clearly.
I have forwarded your feedback and recommendations to our development team for review. We will keep you updated on any progress regarding this matter.
In the meantime, if you have any further suggestions or ideas, we’d be happy to hear them via our feedback board here:
https://feedback.veronalabs.com/boards/wp-statistics
Thank you again for helping us improve WP Statistics.
Best regards,
Mehmet
Hello @horgster,
Thank you again for your valuable feedback and for pointing out this important matter.
I’d like to let you know that the concern you mentioned has already been addressed in our development version.
It is not yet included in an official release, but you can already access it through our development branch on GitHub.
https://github.com/wp-statistics/wp-statistics/tree/development
Once the fix is officially released in the next version of WP Statistics, I will update you here to let you know.
We appreciate your patience and your contribution to improving the plugin.
Best regards,
Mehmet
Hi @gandomi
Thank you very much for taking this issue seriously and for the quick response.
Looking forward for update when new version is ready.
Best Regards
Horgster
Hello @horgster,
Thank you again for your patience and support.
I’m happy to let you know that this issue has now been resolved in the latest official release. Please update your plugin to version 14.15.14 to apply the fix.
We really appreciate your help in improving WP Statistics and your continued trust in us.
Best regards,
Mehmet
Hi @gandomi
Thank you very much for this update and quick service!
In the release notes; it states “Prevented wp_statistics_tracker_js_errors option bloat by limiting stored errors and truncating error messages.”
What has been fixed here, as it states “limiting” errors, does that mean that we will still posted error messages in the autoloader?
Hello @horgster,
Thank you for your follow-up and your attention to detail.
Regarding your question about the release note “limiting stored errors and truncating error messages”:
- We updated the code so that, no matter how many entries come in, we only keep 10 errors, removing the oldest ones from the beginning of the list.
- We also added a safeguard on error message length. Very long messages are truncated, and the limit is configurable via a filter.
This ensures the autoloaded option will no longer bloat your database, even if many errors are generated.
Best regards,
Mehmet
Hi @gandomi
Thank you for quick response and detailed explenation.
Assume that these 10 errors also includes following error types; warnings, deprecated as well, or will it only keep the Error type?
Bear in mind that many wordpress sites will have lots of “deprecated” error types due to plugins / themes etc that yet is not updated. This will continuously keeping writing unnecessary traffic to the the autoloader. Our ISP has requested us to avoid this as much as possible.
Being able to debug is important, but I think you should add an option /check box to allow the user to enable / disable this feature when needed. This feature has more value when you need to debug rather than keeping it logging and writing to the autoloader each time a page is loaded.
We have often release of ticket sales to our event, causing severe high peak traffic, and such will contribute to avoid unnecessary traffic and reduce the load.
Allow the customer to decide if they want this feature on or off. Don’t you agree?
Best Regards
Horgster
Hello @horgster,
Thank you again for your valuable input.
I’ve shared your suggestion with our development team for further review, and I’ll follow up with you once I have an update from them. For now, please continue using the filter you mentioned to keep the debugger logs disabled, as that will prevent unnecessary entries from being stored.
I’ll also make sure to explain your concerns to the team so that they can evaluate the possibility of adding a toggle option in the settings for enabling or disabling this feature.
We really appreciate your thoughtful feedback and the time you’ve taken to help us improve WP Statistics.
Best regards,
Mehmet
