Mehmet
Forum Replies Created
-
Hello @develis,
Thank you for reaching out.
In the newer updates, the
wp_statistics_visitstable is no longer created in the database.
The data has been merged with other tables for better performance and organization.You can still access your visit data through the other export files provided by the plugin.
This way, you can get all the information you need without any loss.I hope this helps and makes things easier for you.
Thank you for your understanding and support.
Best regards,
MehmetForum: Plugins
In reply to: [SlimStat Analytics] PHP Warnings after updating to 5.3.0Hello @qerghgfjkgk,
Thank you for reporting the PHP notices and the broken “At a Glance” widget.
Sorry for the trouble this has caused.For the Dashboard styling issue: please clear all caches (plugin/server/CDN) and your browser cache.
This should restore the “At a Glance” widget to normal.Regarding the PHP errors (
Undefined variable $unpackedon lines 2087–2088 and the array offset notice):
We are actively investigating this and have queued a fix.
We will notify you as soon as an update is available.
No additional action is required on your side for this part right now.If the widget still looks broken after clearing caches, please let us know.
We appreciate your patience and cooperation.Best regards,
MehmetHello Manuel,
Thank you for reaching out and for the details you’ve already shared.
To better identify the source of the slowdown, could you please install the Query Monitor plugin temporarily?
Once activated, it will show you which queries or processes are taking the most time to load.If possible, please share the details or a screenshot of the slow queries with us.
This will help us pinpoint what is causing the delay and suggest the best solution.We appreciate your cooperation and look forward to your update.
Best regards,
MehmetHi @shqipcinema,
I’m glad to hear everything is running smoothly now.
You can also use Statistics > Optimization > Data Clean Up to further manage your database and improve performance.
Best regards,
MehmetHi @shqipcinema,
Thank you for sharing the detailed information.
You are correct, for websites with very high traffic (for example, around 1,000 concurrent users), WP Statistics can put additional load on the database, especially when monitoring online users.
The good news is that starting from version 14.16, we have addressed this database performance issue, and the plugin will run much more efficiently in such scenarios.
As a temporary workaround, we recommend disabling online visitor monitoring if possible:
Go to Statistics > Settings > General > Monitor Online Visitors and turn it off.This should help reduce the immediate load until the new release is available.
We appreciate your patience and thank you for using WP Statistics.
Best regards,
MehmetForum: Plugins
In reply to: [SlimStat Analytics] Invalid Date NaN in year-view graphs since 5.3.0Hello @toxicum,
Thank you for sharing the console and PHP log details.
To help us investigate this further, could you please also provide the following information:
- Operating system date type (Gregorian, Hijri, Jalali, etc.)
- Browser name and version
- Timezone (from WordPress → Settings → General)
- Date format (from WordPress → Settings → General)
- Time format (from WordPress → Settings → General)
- Are you using any plugins or tools that convert or customize WordPress date formats?
This information will allow us to better replicate the issue and provide you with an accurate solution.
Best regards,
MehmetHello Nils,
You are correct that for WP Statistics to function properly, the following file must not be cached:
/wp-content/plugins/wp-statistics/assets/js/tracker.jsRegarding WP Super Cache, it is not causing the issue, as this plugin does not cache JS files.
The problem is likely related to your other caching plugins.Most caching plugins offer a way to exclude specific files.
For example, in Autoptimize, you can go to:
Settings > Autooptimize > JS, CSS, HTML > Exclude scripts from Autoptimize
and add /wp-content/plugins/wp-statistics/assets/js/tracker.js there.This guide provides detailed instructions that may help:
https://wp-statistics.com/resources/how-to-exclude-wp-statistics-tracker-js-from-caching-minification/Kind regards,
Mehmet- This reply was modified 9 months, 3 weeks ago by Mehmet.
Forum: Plugins
In reply to: [SlimStat Analytics] Invalid Date NaN in year-view graphs since 5.3.0Hello @toxicum,
Thank you for your message and for sharing the screenshot.
I’ve checked the plugin on my side, and everything appears to be working correctly.
To help us identify the cause of this issue on your site, could you please share:
- Any related PHP error logs
- Any console errors from your browser
With these details, we’ll be able to investigate further and provide a precise solution.
Thank you for your cooperation and patience!
Best regards,
MehmetHello @zilliq,
I hope you’re doing well.
I wanted to give you an update regarding the memory issue you experienced with longer date ranges in WP Statistics.
Our development team has made some improvements in the plugin to help reduce memory usage for statistics over longer periods.
These changes are not yet officially released, but they will be included in an upcoming update.In the meantime, if you’d like to try the improved version, you can access the development version here:
https://github.com/wp-statistics/wp-statistics/tree/developmentOnce the official update is released, I will make sure to notify you so you can update your site safely.
Thank you again for your patience and understanding.
Best regards,
MehmetHi @erpol53,
Thank you for sharing the details and explaining what you tried so far.
The reason the login page still appears in the “Most visited pages” widget is that its record remains in the database. To remove the login page from the “Most visited pages” widgets, you can safely delete its records directly from the
wp_statistics_pagestable.Here is the query you can run in phpMyAdmin (or any MySQL client):
DELETE FROM wp_statistics_pages WHERE type = 'loginpage';Once executed, the widget should no longer display the login page entry.
Please make sure to back up your database before running the query.
Let me know if this solves the issue for you.
Best regards,
MehmetHi @maltmann,
We’re happy to inform you that the export and import functionality has now been added to the plugin.
You can use this feature through the Customization Add-on to transfer plugin settings between sites.
We hope this helps streamline your workflow.
Best regards,
MehmetHi @foroughi,
Thank you for your kind feedback!
We’re happy to know that you’re pleased with the plugin.Best regards,
MehmetHi @infodale,
Thank you so much for your kind words!
We’re glad to hear that you’re satisfied with the service.Best regards,
MehmetHi @mansourikhah,
We’re glad to let you know that the issue with notification variables not being parsed correctly has been fully resolved.
The fix has already been included in the latest release of the plugin.
We kindly recommend updating to the most recent version to ensure everything works as expected.
Thank you once again for your patience and for bringing this to our attention.
Best regards,
MehmetHi Mohammad Ali,
Thank you for following up.
The issue you reported has now been resolved, although the fix has not yet been included in an official release.
In the meantime, you can access the patched version directly from our GitHub development branch:
https://github.com/wp-sms/wp-sms/tree/developmentAs soon as the official release is published, I will notify you right away.
Thank you for your patience and continued support.
Best regards,
Mehmet