Amir
Forum Replies Created
-
We’re glad to hear that the issue has been resolved. We apologize for any inconvenience caused during this time and truly appreciate your patience.
If you have any questions or face any issues in the future, please don’t hesitate to reach out to us.
Kind regards,Hi @j1nakayama @u3aredcliffe @jonfabritius
We’re pleased to inform you that the issue mentioned in this thread has been addressed in version 14.10.2, which was just released. Please update the plugin to the newest version, and don’t hesitate to let us know if you experience any further issues.
We truly appreciate your patience and support!
Best regards,Hi @ulim
We wanted to inform you that the issue you reported has been resolved in version 14.10.2, which was released just a few minutes ago. Please update the plugin to the latest version, and let us know if you encounter any further issues.
Thank you for your patience and understanding!
Best regards,Thank you. It is possible that this has caused the difference in the statistics..
We’ve made updates to the Client Side in version 14.10.2, which will be released soon. After the update, please test it again and share your results.
Also, ensure that the Bypass Ad Blockers option is enabled in Client Side.
Regards,Thanks for your message!
Could you please check if Mod Security is enabled on your server?
We look forward to your response.
Regards,Thank you for reviewing and informing us about this matter.
We will investigate this issue and update you with the results soon.
We appreciate your patience.
Could you please send us the list of plugins installed on your site?
You can obtain the complete list by clicking on the “Copy site info to clipboard” option in Tools – Site Health – Info. This will help us identify and resolve the issue more quickly.
Looking forward to hearing from you!
Regards,I hope you’re doing well! I wanted to check in and ask if the issue you were facing has been resolved. Were you able to identify the plugin that was causing the conflict?
If not, please go to Tools – Site Health – Info and click on “Copy site info to clipboard.” Then share that information with us so we can help you better.
Looking forward to hearing from you!
Best regards,Hi @lodree
Thank you for following up and informing us about this matter.
If you are using the latest version of our plugin, please send us the Site Health info of your site by going to Tools – Site Health – Info and clicking on the “Copy site info to clipboard” option.
This will allow us to examine the exact settings applied in the plugin and thoroughly review the items in the Filtering & Exceptions section.
We appreciate your patience and cooperation.
We’ve attempted to replicate the issue using the default configuration but were unable to reproduce the problem. To assist us in diagnosing this further, could you please double-check the configuration you’ve applied?
Additionally, providing any relevant Apache error logs generated during the occurrence of this issue would greatly help us in pinpointing the cause.
Best regards,
I hope you’re doing well. I just wanted to follow up and ask if you’ve been able to test the suggested steps. Were you able to identify any plugin conflicts, or did updating the plugins and clearing the cache resolve the issue for you?
If the problem persists, could you please share the list of installed plugins? You can easily do this by going to Tools – Site Health – Info and clicking on Copy site info to clipboard. This will help us better understand your setup and provide further assistance.
Thank you!
Best regards,Dear @lodree
Thank you for the update and for following the suggested steps.
We’re currently analyzing data across several websites, and so far, client-side tracking generally provides more accurate data, while server-side tracking can sometimes inflate view counts. This difference often comes from how caching, bots, and ad blockers affect each method.
Also, please go to Statistics – Settings – Filtering & Exceptions and check the URL Exclusions section. Make sure that both Excluded RSS Feeds and Excluded 404 Pages are enabled. On the server side, some bots and crawlers can bypass detection and visit these pages, which may lead to higher view counts compared to client-side tracking.
We’re continuing to investigate this to ensure your tracking setup is as accurate as possible.
Sincerely,Dear Johan,
I’m really sorry to hear about the issues you’ve run into.
We always do our best to ensure the plugin works smoothly and provides accurate reports, but sometimes conflicts with other plugins, especially caching ones, can cause problems that are beyond our control.
After looking into your case, we noticed you’re using a caching plugin. To fix this, it’s important to clear your cache after every update, so the new Tracker file can replace the old one, allowing the stats to be logged correctly.
We’re actively working on improving how these scenarios are handled in future updates to minimize such conflicts and make everything run as smoothly as possible.
Again, I’m truly sorry for the inconvenience, and I’ll personally reach out to you via our dedicated support soon to make sure we resolve this and prevent it from happening again.
Thank you so much for your patience and understanding, we really appreciate it.
Sincerely,We apologize for the delay in our response.
This issue is due to a conflict with another plugin, which results in the widget not displaying correctly or causing the following errors.
Please make sure to clear the cache of your site and browser completely after updating to the latest version, and check which plugin is causing the conflict by disabling other plugins.
We are also investigating this issue and will fully resolve it in future versions.
Thank you for your patience.
Dear @j1nakayama @jonfabritius @u3aredcliffe
We have identified an incompatibility between WP Statistics v14.10.1 and WordPress v6.5.5. Our development team is actively working on a resolution, which we plan to include in an upcoming release.
In the meantime, we recommend ensuring that WordPress and all plugins remain up to date, as updating WordPress will resolve this issue.
Additionally, if you prefer not to update WordPress right away, you can temporarily resolve the issue by disabling the “View Stats in Editor” option. To do this, navigate to Statistics > Settings > Display Options. This will prevent the error from displaying until we release a complete fix in the next minor update.
We sincerely apologize for any inconvenience this may have caused and appreciate your continued support and understanding.
Best regards,