Complete statistics for your WordPress site.
The admin manual is installed as part of the plugin, simply go to Statistics->Manual to view it. At the top of the page will also be two icons that will allow you to download it in either ODT or HTML formats.
Disable / Enable the plugin. You may also want to remove and re-install it.
Make sure you've downloaded the GeoIP database and the GeoIP code is enabled.
Also, if your running an internal test site with non-routable IP addresses (like 192.168.x.x or 172.28.x.x or 10.x.x.x), these addresses will come up as unknown always.
The webcrawler detection code has been fixed and will now exclude them from your stats, don't worry, it now reflects a more accurate view of actual visitors to your site.
The GeoIP code requires several things to function, PHP 5.3 or above, the bcmath extension, the cURL extension and PHP cannot be running in safe mode. All of these conditions are checked for but there may be additional items required. Check your PHP log files and see if there are any fatal errors listed.
This depends on how many hits your site gets. The data collection code is very light weight, however the reporting and statistics code can take a lot of memory to process. The longer you collect data for the more memory you will need to process it. At a bare minimum, a basic WordPress site with WP Statistics should have at least 32 meg of RAM available for a page load. Sites with lots of plugins and high traffic should look at significantly increasing that (128 to 256 meg is not unreasonable).
Be very careful to set the subnet mask correctly on the subnet list, it is very easy to catch too much traffic. Likewise if you are excluding a single IP address make sure to include a subnet mask of 32 or 255.255.255.255 otherwise the default subnet of 0 will be used, catching all ip addresses.
Make sure you have WordPress configured correctly for SMTP and also check your WP Cron is working correctly. You can use Cron View to examine your WP Cron table and see if there are any issues.
WP Statistics hasn't been tested with multi-site and there have been some issues reported with getting it enabled correctly on all sites in a network.
Yes, version 6.0 has introduced page hit statistics!
This means that MaxMind has block the IP address of your webserver, this is often the case if it has been blacklisted in the past due to abuse.
You have two options: - Contact MaxMind and have them unblock your IP address - Manually download the database
To manually download the database and install it take the following steps:
You can also ask MaxMind to unblock your host. Note that automatic updates will not function until you can successfully download the database from your web server.
WP Statistics requires PHP 5.3, if it has detected an older version of PHP installed it will active cleanly in WordPress but disable all functionality, you will have to upgrade to PHP 5.3 or above for it to function. WP Statistics will display an error on your plugin list just below the WP Statistics entry to let you know.
If there is no error message there may be something else wrong, your first thing to try is disabling your other plugins as they can sometimes cause conflicts.
If you still don't see the menus, go to the support forums and open a new thread and we'll try to help out.
Pretty much every plugin/service is going to give you different results for visits and vistors, there are several reasons for this:
Services that use centralized databases, like Google Analytics, for spam and robot detection have better detection than WP Statistics can. The trade off of course is relaying on an external service.
Since WP Statistics 8.0, PHP 5.3 or above has been required. If you are using an older version of PHP it cannot understand the new syntax included in WP Statistics 8.0 and generates a parse error.
Your hosting provider should have a newer version of PHP available, sometimes you must activate it through your hosting control panel.
Since the last release of PHP 5.2 is over 3 years ago (Jan 2011) and is no longer supported or receiving security fixes, if your provider does not support a newer version you should probably be moving hosting providers.
If you have done an upgrade and you can no longer access your site due to the parse error you will have to manually delete the wp-statistics directory from your wordpress/wp-content/plugins directory, either through your hosting providers control panel or FTP.
Do not use older versions of WP Statistics as they have know security issues and will leave your site vulnerable to attack.
Don't, upgrade immediately to the latest version of WP Statistics.
You can manually disable plugins in WordPress by simply renaming the folder they are installed in. Using FTP or your hosting providers file manager, go to your WordPress directory, from ther go to wp-content/plugins and rename or delete the wp-statistics folder.
We use several libraries and use a utility called Composer to manage the dependencies between them. We try and keep our Composer library up to date but not all plugins do and sometimes we find conflicts with other plugins. Try disabling your other plugins until the error goes away and then contact that plugin developer to update their Composer files.
Search Engine Referrals and Words are highly dependent on the search engine providing the information to us and that often is not the case. Unfortunately there is nothing we can do about this, we report on everything we receive.
There can be many reasons for this, but the most common reason is a botnet has decided to visit your site and we have been unable to filter it out. You usually see your visits spike for a few days and then they give up.
Visits is the number of page hits your site has received.
Visitors is the number of unique users that have visited your site.
Visits should always be greater than Visitors (though there are a few times when this won’t be true on very low usage sites due to how the exclusion code works).
The average number of pages a visitor views on your site is Visits/Visitors.
This is usually caused by a PHP fatal error, check the page source and PHP logs.
The most common fatal error is an out of memory error. Check the Statistics->Optimization page and see how much memory is currently assigned to PHP and how much the overview is using.
If it is a memory issue you have two choices: - Increase PHP's memory allocation - Delete some of your historical data.
See http://php.net/manual/en/ini.core.php#ini.memory-limit for information about PHP's memory limit.
To remove historical data you can use the Statistics->Optimization->Purging->Purge records older than.
Unfortunate we're completely dependent on the search engine sending use the search parameters as part of the referrer header, which they do not always do.
Probably not, most caching plugins don't execute the standard WordPress loop for a page it has already cached (by design of course) which means the WP Statistics code never runs for that page.
This means WP Statistics can't record the page hit or visitor information, which defeats the purpose of WP Statistics.
We do not recommend using a caching plugin along with WP Statistics.
Do you have eAccelerator installed? If so this is a known issue with eAccelerator and PHP's "anonymous" functions, which are used in the user agent parsing library. As no new versions of eAccelerator have been released for over 3 years, you should look to replace it or disable it.
This is because something has gone wrong during the installation.
At the end of the message will be a list of tables that are missing, you can use the provided link to re-run the installation routine. If that does not resolve the issue and the visitors table is the only table listed, you may want to check your MySQL version. Some older versions of MySQL (in the 5.0.x series) have issues with complex compound indexes, which we use on the visitors table. If this is the case, check with your hosting provider and see if they can upgrade to a newer version of MySQL.
If you still have issues open a new thread on the support forum and we'll try and resolve it for you.
Requires: 3.0 or higher
Compatible up to: 4.3.1
Last Updated: 3 weeks ago
Active Installs: 200,000+
37 of 43 support threads in the last two months have been resolved.
Got something to say? Need help?