{"id":59056,"date":"2010-09-01T09:10:53","date_gmt":"2010-09-01T09:10:53","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/stats173zip\/"},"modified":"2010-09-01T09:10:53","modified_gmt":"2010-09-01T09:10:53","slug":"stats173zip","status":"closed","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/stats173zip\/","author":6887839,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"","stable_tag":"trunk","tested":"","requires":"","requires_php":"","requires_plugins":"","header_name":"stats173zip","header_author":"","header_description":"","assets_banners_color":"","last_updated":"2010-09-01 09:10:53","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":0,"downloads":439,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":[],"tags":[],"upgrade_notice":[],"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":[],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[],"plugin_category":[],"plugin_contributors":[],"plugin_business_model":[],"class_list":["post-59056","plugin","type-plugin","status-closed","hentry","plugin_committers-asier69"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/stats173zip.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"","raw_excerpt":"

There are hundreds of plugins and services which can provide statistics about your visitors. However I found that even though something like Google Analytics provides an incredible depth of information, it can be overwhelming and doesn't really highlight what's most interesting to me as a writer. That's why Automattic created its own stats system, to focus on just the most popular metrics a blogger wants to track and provide them in a clear and concise interface. <\/p>\n

Installing this stats plugin is much like installing Akismet, all you need is to put in your [API Key](http:\/\/wordpress.com\/api-keys\/ "You can get a free API key from WordPress.com") and the rest is automatic.<\/p>\n

Once it's running it'll begin collecting information about your pageviews, which posts and pages are the most popular, where your traffic is coming from, and what people click on when they leave. It'll also add a link to your dashboard which allows you to see all your stats on a single page. Less is more.<\/p>\n

Finally, because all of the processing and collection runs on our servers and not yours, it doesn't cause any additional load on your hosting account. In fact, it's one of the fastest stats system, hosted or not hosted, that you can use.<\/p>\n

== Screenshots ==<\/p>\n

1. Your stats are displayed in a frame on your own blog's dashboard. There are graphs and several sections of charts below. You will need to be logged in at WordPress.com to see the stats. If you see a login box here, use your WordPress.com login.<\/p>\n

2. Each post has its own graph.<\/p>\n

3. You can add other WordPress.com users to the list of people allowed to see your stats.<\/p>\n

== Installation ==<\/p>\n

The automatic plugin installer should work for most people. Manual installation is easy and takes fewer than five minutes.<\/p>\n

1. Create a stats<\/code> directory in your plugins<\/code> directory. Typically that's wp-content\/plugins\/stats\/<\/code>.
\n2. Into this new directory upload stats.php<\/code> and open-flash-chart.swf<\/code>.
\n3. Activate the plugin through the 'Plugins' menu in WordPress.
\n4. It will ask you to enter your WordPress.com API key, do so.
\n5. Sit back and wait a few minutes for your stats to come rolling in.<\/p>\n

== Frequently Asked Questions ==<\/p>\n

= Can I keep using existing stat systems like Mint, Google Analytics, and Statcounter? =<\/p>\n

Of course, nothing we do conflicts with any of those systems. We're just (hopefully) faster.<\/p>\n

= How long before I start seeing stats? =<\/p>\n

It may take as long as 20 minutes the first time you use it. After that they should update every 3 minutes or so.<\/p>\n

= Does it count my own hits? =<\/p>\n

It does not count the hits of logged in users.<\/p>\n

= What if the stats don't start showing up? Do I need anything special in my theme? =<\/p>\n

Yes, your theme must have a call to <\/code> at the very bottom right before the <\/code> tag.<\/p>\n

= Can I hide the smiley? =<\/p>\n

Sure, just use display:none<\/code>. Try this code in your stylesheet:<\/p>\n

img#wpstats{display:none}<\/code><\/p>\n

= Is it compatible with WP-Cache? =<\/p>\n

The plugin collects stats via a javascript call, so as long as the JS call is on the page stats will be collected just fine, whether the page is cached or not.<\/p>\n

= Can I use the same API key on multiple blogs? =<\/p>\n

Just like with Akismet, you're welcome to use the same API key on multiple blogs. If you view your stats directly on WordPress.com, you can easily switch between all of your blogs' stats reports.<\/p>\n

= How do I add a Top Posts widget to my blog? =<\/p>\n

We opened our database for developers to retrieve stats. The API is at http:\/\/stats.wordpress.com\/csv.php<\/code> and the plugin includes a handy function, stats_get_csv()<\/code>, which you can use to get your most popular posts. Here is code you can add to your theme based on the work of Ben Gillbanks:<\/p>\n

Currently Hot<\/code><\/pre>\n
== Changelog ==<\/p>\n
= trunk =
\n* Add domain to gettext calls and load_plugin_textdomain (props nbachiyski)
\n* Add POT file and Text Domain
\n* Change some escaping functions (props nbachiyski)
\n* Remove delete_option from deactivation hook<\/p>\n
= 1.7.2 =
\n* Remove footer test pending investigation of errors.<\/p>\n
= 1.7.1 =
\n* Add real-time test to check footer immediately prior to displaying notice. Should help automatic upgraders.<\/p>\n
= 1.7 =
\n* Remove support for hard-coded API key as $stats_wpcom_api_key
\n* Update admin screen after API key entry to add Recommended Action and clarify instructions
\n* Add option to disable wp.me shortlinks
\n* Add option to select roles with stats report visibility
\n* Add option to enable tracking logged-in users
\n* When activated for entire network, do not show admin notice about missing API keys
\n* When plugins.php disabled, move stats admin page to options-general.php
\n* Add check for footer code and display a helpful notice if not detected<\/p>\n
= 1.6.3 =
\n* Add support for shortlink API in WordPress 3.0
\n* Add CSV usage example to readme
\n* Remove .htaccess
\n* Remove all-time stats from dashboard widget<\/p>\n
= 1.6.2 =
\n* Fix infinite loop when shortlink function dec2sixtwo called with a negative number. Thanks to Andrew Mattie for identifying this bug.
\n* Fix unescaped Top Searches section in dashboard module. Thanks to Kobi for the report.<\/p>\n
= 1.6.1 =
\n* Fix attachment titles in post stats list.
\n* Fix chart not appearing due to .htaccess directive installed by some users. Thanks to Sean at growingmoneyblog.com for access to his affected system.<\/p>\n
= 1.6 =
\n* Add shortlink generator. Now wp.me shortlinks are available on the Edit Post screen from a button next to View Post.<\/p>\n
= 1.5.4 =
\n* Work around core API change in plugins_url. Different code for 2.7. Fixes missing charts in 2.7.*. No changes for 2.8+.<\/p>\n
= 1.5.3 =
\n* Restore backward compatibility for WordPress 2.7. Fixes "Call to undefined function plugin_dir_url()..."<\/p>\n
= 1.5.2 =
\n* Fix dashboard chart missing due to omitted line of code.<\/p>\n
= 1.5.1 =
\n* Include Open Flash Chart SWF. Faster and more reliable than proxying it. Should fix missing graph for many users.
\n* Move change log out of source code.
\n* Fixed an XMLRPC encoding issue that resulted in "malformed" error when entering API key. Thanks to Oscar Reixa for helping.<\/p>\n
= 1.5 =
\n* Kill iframes.
\n* Use blog's role\/cap system to allow local users to view reports. (No more switcher.)
\n* Thanks to Stefanos Kofopoulos for helping to debug encoding issues.<\/p>\n
= 1.4 =
\n* Added gmt_offset setting to blog definition. (Stats in your time zone.)<\/p>\n
= 1.3.8 =
\n* Fixed "Missing API Key" error appearing in place of more helpful errors. Hat tip: Walt Ritscher.<\/p>\n
= 1.3.7 =
\n* If blog dashboard is https, stats iframe should be https.<\/p>\n
= 1.3.6 =
\n* fopen v wp_remote_fopen CSV fix from A. Piccinelli<\/p>\n
= 1.3.5 =
\n* Compatibility with WordPress 2.7<\/p>\n
= 1.3.4 =
\n* Compatibility with WordPress 2.7<\/p>\n
= 1.3.3 =
\n* wpStats.update_postinfo no longer triggered by revision saves (post_type test)\n<\/p>","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/59056","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=59056"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/asier69"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=59056"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=59056"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=59056"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=59056"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=59056"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=59056"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}