Mehmet
Forum Replies Created
-
Forum: Plugins
In reply to: [SlimStat Analytics] PHP Warnings after updating to 5.3.0Hello @qerghgfjkgk,
The issue you reported has been fixed in the latest release version 5.3.1.
Please update to the newest version, and the problem should be fully resolved.Thank you once again for your helpful feedback and patience.
Best regards,
MehmetForum: Plugins
In reply to: [SlimStat Analytics] Invalid Date NaN in year-view graphs since 5.3.0Hello @toxicum,
The issue you reported has been fixed in the latest release version 5.3.1.
Please update to the newest version, and the problem should be fully resolved.Thank you once again for your helpful feedback and patience, it really means a lot!
Best regards,
MehmetForum: Plugins
In reply to: [SlimStat Analytics] PHP Warnings after updating to 5.3.0Hi @qerghgfjkgk,
The styling issue has been fixed, but it hasn’t been officially released yet. It will be available in version 5.3.1. In the meantime, you can download the 5.3.1 release from this link:
https://github.com/wp-slimstat/wp-slimstat/tree/release-5.3.1Once the official release is out, I will follow up with you again.
Best regards,
MehmetHello @rubenreyes,
I’m reaching out from the support team. I wasn’t able to locate your previous ticket in our system. Could you kindly submit it once more so we can review the issues promptly and assist you as quickly as possible?
Best regards,
MehemtThanks a lot for your feedback! Glad to hear it was easy to set up and is working well for you.
Best regards,
Forum: Plugins
In reply to: [SlimStat Analytics] PHP Warnings after updating to 5.3.0Hi @qerghgfjkgk,
Apologies for the delayed response. We are currently addressing this issue in responsive mode and will follow up with you once it has been resolved.
Best regards,
MehmetHello @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,
MehmetHi @sfrueh,
Thank you for reaching out.
The message you see is completely legitimate and safe. Here’s why it appears:
- The plugin has detected that a small database update is required.
- This update is necessary to keep your statistics accurate.
- Only administrators of the site can see this notice.
You can safely click the “Update Now” button; it’s part of the WP Statistics plugin itself and not a scam or third-party injection.
Best regards,
MehmetHello @juaancmendez,
Thank you very much for your suggestion and for providing the code.
Instead of applying this change via jQuery on the frontend, it would be cleaner and more reliable to implement a PHP filter on the server side. This way, the password maxlength can be enforced before rendering the form, reducing reliance on client-side scripts and improving compatibility and security.
Could you consider adding a filter in the plugin to set the password maxlength directly in PHP?
Thank you again for your help and guidance.
Best regards,
MehmetHello @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,
MehmetHello @zilliq,
Please update WP Statistics to version 14.15.4. This release includes performance improvements that reduce memory usage for longer date ranges and should resolve the critical errors on the ‘Visitor Insights,’ ‘Category Insights,’ and ‘Content Insights’ pages.
After updating, clear your cache and reload the pages. If issues persist, let us know for further guidance.
Best regards,
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,
MehmetHello Juan,
Thank you very much for your quick response.
Yes, I would really appreciate it if you could share the snippet to set a character limit for the password field.Best regards,
MehmetHello @mosimages,
Thank you for reaching out.
I’ve shared your report with our development team for review.
We are currently looking into this and will follow up with you soon.
Rest assured, we’ll keep you updated as soon as we have more details.We appreciate your patience and support.
Best regards,
Forum: Plugins
In reply to: [SlimStat Analytics] Invalid Date NaN in year-view graphs since 5.3.0Hello @toxicum,
I just wanted to follow up with you regarding the issue you reported.
We have identified the cause of the problem and are currently working on a fix.
As soon as the issue is resolved, we will make sure to notify you immediately.Thank you for your patience and understanding.
Best regards,
Mehmet