Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Problem(s) solved. Both symptoms – WP that page does not exist and stats discrepancies were both cause by a conflict between wp_stats and wordfence. The conflict only occurs when you use wordfence’s simple cache option. I have not tested if the conflict also occurs with wordfence’s falcon cache.

    I will cross post this as a wordfence issue. At the end of the day it is up to your guys to see if the conflict can be resolve or whether users using both plugins are warned not to use the wordfence cache option.

    Flushing the db table had no effect. Moving on to other plug-ins. I am focusing on one in particular. Won’t mention any names just yet. The two plug-in have been working together harmoniously for a year, but I have my suspicions about one of the setup options. Stay tuned.

    I have just flushed the settings from the db table and re-configured everything. We’ll see how that goes. Thanks for all your efforts. If it wasn’t such a great plug-in I would not be so piss-off about breaking it.

    @greg Ross – no such luck. I have now purge the first 4 months of data from the database. Nil impact on the problem(s). I have also been live monitoring the hosting resource usage with cPanel on the back end. The site is no where near the resource limits.

    It cannot be a coincidence that after I fiddled with the wp_stats settings to try resolving the page loading problem that reported hits search referrals tanked. Monitoring the sites backend very carefully before I started fiddling, the search referral data was not affected when I first started looking at the page loading problem.

    Snooping around the stats some more I have noticed that the daily hit count on individual pages has tanked by a similar percentage to the search engine referral count. However, the visitor hit count and visits hit count are unaffected.

    Any idea how wp_stats can record the 300 visitors and over 1,000 visits and yet not correctly record the pages being visited?

    P.S. I am holding off on deleting everything and reinstalling so that we might get to the bottom of this.



    Excellent work. Thanks Greg.

    P.S. Excellent plug-in



    Yep! That seems to have fixed it.

    I went back to some of the other sites and noticed they did not have browscap usage Activated.

    As a precaution, should we go back to all sites and force the browscap update after updating to 8.1.1?



    I have a number of WP sites I manage for clients (basically half a dozen all with the same theme and plug-in set) all hosted with godaddy. Two days ago, WP Statistics stop recording visits, visitors and search referrals on one (and only one) of these sites.

    Details as follows;


    Memory usage in PHP: 7,096,120 Byte

    PHP Memory Limit: 256M
    The memory limit a script is allowed to consume, set in php.ini.
    Number of rows in the wp_statistics_useronline table: 1 Row

    Number of rows in the wp_statistics_visit table: 171 Row

    Number of rows in the wp_statistics_visitor table: 7,273 Row

    Number of rows in the wp_statistics_exclusions table: 575 Row

    Number of rows in the wp_statistics_pages table: 1,436 Row

    Version Info

    WP Statistics Version: 8.1
    The WP Statistics version you are running.
    PHP Version: 5.4.31
    The PHP version you are running.
    PHP Safe Mode: No
    Is PHP Safe Mode active. The GeoIP code is not supported in Safe Mode.
    jQuery Version: 1.11.1
    The jQuery version you are running.
    cURL Version: 7.24.0
    The PHP cURL Extension version you are running. cURL is required for the GeoIP code, if it is not installed GeoIP will be disabled.
    BC Math: Installed
    If the PHP BC Math Extension is installed. BC Math is no longer required for the GeoIP code and is listed here only for historical reasons.

    Have spoken to Godaddy support and there is nothing but green lights on the hosting account.

    Anything else I should check? Any other ideas what could be causing this?


    @greg Ross – Never got a chance to try your fix. Just saw the 5.4 upgrade notification, upgraded from 5.3 to 5.4 and all is working.

Viewing 8 replies - 1 through 8 (of 8 total)