WPReady
Forum Replies Created
-
Hello everyone. Today we upgraded Statcomm to 1.7.20.
This version is addressing many aspects but this problem in particular is still in analysis.We hope we’ll have a solution soon.
Thanks and enjoy the day.Thanks for your observation.
The problem is caused because the User Agent database could be outdated.
A new UA database will be released this week and you can update to it from the Advanced tab.Thank for your comments. It is unlikely Jetpack cause any problem, but we will research any potential conflict before pronounce a final judgment.
Currently Statcomm is using a cache system to improve the performance. This cache records any results excluding today numbers. If the cache has is not synchronized with the current time, an inaccuracy would happen.
We’ll dig into this problem, thanks for pointing it out.
Thanks for your comments.
We are expecting to release an update to fix this and other problems.
We are delaying the new version since this would be the first one supporting multisite. This major achievement took most our resources dealing with plugin issues but also WordPress issues(!).
(see our post http://wpgetready.com/2012/06/wordpress-3-4-and-multisite/)We are conducting extensive tests to deliver an improved version. Nonetheless, is difficult to release a plugin 100% bug free, since there are changing conditions to take in account. That’s why we find invaluable your feedback to improve it.
We would like to release the new version this weekend, depending on how well the tests perform.
We’ll look into the plugin to see if there is some problem involved.
Thanks for your observation.Best regards
We’ll think the issue is related with the table creation and not about missing files.
The plugin currently is not dumping any error messages when there is a problem with the table creation, something that will add in the next version. That should also explain why is not capturing any data.The workaround is to delete the line you indicated on the uninstall.php file . This line only cleans some data , but since the plugin never worked , it has nothing to do.
You can edit uninstall.php file using Plugin->Editor and editing the file and removing the line.If you are unable to access to the site, is possible to remove the plugin accessing via FTP or using a host control panel.
Our apologies for the problem.
Thanks for your comments.
It seems for some reason the mysql class was missing. Since the plugin depends on this class, that surely was the reason it didn’t collect any visitors.It is strange though. The only actual explanation should be that the file was completely missing on the installation.
We’ll check the issue and we’ll get back to you.
Thanks for your comments.
We’ll check if there is an issue related with the counters.Thanks for your comments.
StatComm has a way to ban ips, commented on the help included on the plugin, and also discussed with some detail in the forum.
We agreed current solution is somewhat rough, and a more practical and more interactive solution is needed. However such improvement was moved to later stages, since we are currently developing the multisite version, stabilizing the code and checking the plugin against new WP version.
Nonetheless we are including your suggestion in a list and will try to publish a list of most requested features for voting.
Thanks again.Thanks for your comments. We are currently checking if there is some problem with the actual way of making the totals.
We’ll keep you updated.Ooops, we couldn’t see the image(seems it is blocked?).
Thanks for your comments. Indeed dataTable is a very good option. Coincidentally we already tested this and other libraries to implement another different plugin with success.
In our current schedule we added also multisite environment. After that we’ll invest time on the table, where there is big room for improvement and customization.
Thanks for the clarification, we need research more on that subject.
Thank you for your comments.
Part of the tests are conducted on sites using W3 Total cache and there were not problems. However we’ll try to dig more on the subject , since this a very common concern among the users.
Fixed on v1.7.10
Best regards and thanks.