Hi @seanst3r,
Thanks for reporting this and sharing the details—much appreciated.
Apologies for the inconvenience caused. I’ve passed this on to our dev team for review.
To help us dig deeper, could you share a bit more?
– What caching plugin (if any) are you using?
– Any sample of the repeated JS errors would be helpful.
We appreciate your input, and we’ll do our best to get this addressed.
I’ll keep you updated as we make progress on this.
Best regards,
Mehmet
Hello,
Thank you for opening the topic, can you please take a screenshot of the Tracker Debugger page?
Hi. Sorry I kinda forgot about this having moved on to other maintenance issues. I checked my binary logs and it’s started up again since reactivating your plugin. Since my initial report I updated to Version 14.13.4
Could not find any Tracker Debugger page. I checked WP-Admin ▸ Statistics ▸ Settings ▸ General ▸ Open Debugger Maybe because I am using server side?
I don’t have any specific cache plugin installed. It’s not about the cache. The cache permissions simply caused a ton of extra js errors which your plugin seems to want to log incessantly. At least, I assume this is being logged by your plugin. Correct me if I am wrong. I don’t see any option to turn it on or off.
The javascript errors it’s logging are now 160kb of repeated “Function _load_textdomain_just_in_time was called incorrectly” This is a lame plugin causing this and it’s of no consequence.
I think you guys are missing the bigger picture. No plugin has any business writing unlimited kilobytes into the options table repeatedly. Especially “‘wp_statistics_tracker_js_errors'” … which is hidden from view and of no practical use to me unless I direct you to debug something. If you must store these, implement a sensible size limit and a frequency limit. The stuff it’s logging has nothing to do with your plugin. Maybe at least filter it to your own tracker’s errors.
Any complex wordpress site is going to have javascript warnings for all kinds of things. Plugins are always using deprecated or soon to be deprecated functions sometimes for years. I don’t turn off reports because I need to see what’s going on and eventually fix it.
Thanks,
Sean
Hi @seanst3r,
Thank you for your detailed feedback and for following up.
To quickly stop the logs from being written into the database, please use the following filter in your theme’s functions.php file or a custom plugin:
add_filter('wp_statistics_disable_tracker_debugger_logs', function () {
return true; // Disables tracker debugger error logging
});
This will disable the Tracker Debugger log storage entirely.
Regarding the Debugger page, the path you followed is correct:
WP-Admin ▸ Statistics ▸ Settings ▸ General ▸ Open Debugger
After clicking the Open Debugger button, it should redirect you to:
yoursite.com/wp-admin/admin.php?page=wps_tracker-debugger_page
Could you please confirm whether the page is not loading at all or if you’re encountering a specific error?
We appreciate your insights, and we’ll take your suggestions seriously as we review and improve how these logs are managed.
Thanks again for your feedback and patience.
Best regards,
Mehmet
Hi. Thanks for the filter hint. I already hacked the plugin code but I will put this in so it survives updates.
There is no “open debugger” option anywhere on my settings, general screen. I have Tracking options, and Tracking Configuration.
Dear @seanst3r,
The Tracker Debugger feature has been available since version 14.12.
You should be able to access it by navigating to Statistics > Settings > General, as shown in this screenshot: https://i.vgy.me/h0O3kj.png.
— Matthew
Maybe because I am using server side? My screen doesn’t have all that extra stuff on it.
Since my initial report I updated to Version 14.13.4
Could not find any Tracker Debugger page. I checked WP-Admin ▸ Statistics ▸ Settings ▸ General ▸ Open Debugger
Dear @seanst3r,
Thank you for the update.
Yes, you are absolutely right — the reason you’re not seeing the extra options, including the Tracker Debugger, is because you’re currently using Server Side Tracking.
If you switch the Tracking Method to Client Side Tracking (Recommended), the Open Debugger button will become visible in the General settings tab.
Please let us know if you need any assistance with this change or if you have any other questions.
Best regards,
Mehmet
Dear @seanst3r,
I hope you’re doing well.
I’m following up to see if everything is working as expected on your end.
If you still notice any irregularities, it might be helpful to check the log file and share any relevant error messages with us.
Also, if the tracker/debugger is now functioning correctly, we would appreciate it if you could send us a screenshot.
Thank you very much for your continued cooperation — we truly appreciate it.
Best regards,
Mehmet
