Updates from January, 2011 Toggle Comment Threads | Keyboard Shortcuts

  • Andy Skelton 3:06 pm on January 17, 2011 Permalink  

    WordPress.com Stats 1.8: Sparkline 

    Just ahead of WordPress 3.1, we released WordPress.com Stats 1.8. The new Stats plugin includes some small fixes that will make it easier for us keep the plugin’s reports in sync with the reports seen on WordPress.com. The plugin’s reports are a few versions behind so look for rapid improvement in the coming weeks. But what’s most exciting about Stats 1.8 is how it works with a new feature in WordPress 3.1: the admin bar.

    screen shot of admin bar

    The admin bar on my self-hosted blog.

    Stats 1.8 adds a tiny bar chart (called a “sparkline”) to the admin bar. To make this chart more interesting, and not just a copy of what you can already see in your stats report page, we zoomed in on the time axis. Rather than show one data point per day we show each of the last 48 hours. Following your blog’s time zone setting, lighter and darker bars represent daylight and nighttime hours.

    Design credit goes to Joen and MT. The sparkline design seems simple and obvious now, but it took a lot of tries to get it that way. It wouldn’t have happened without their contributions.

    Of course, we intend to bring the new sparkline to the WordPress.com admin bar as soon as possible. Remember how we said the plugin’s stats reports are a few versions behind the WordPress.com reports? With the admin bar it’s the reverse. Self-hosted bloggers are the first to get this upgrade. Everyone on WordPress.com will have it soon.

    • Tony Hue 12:32 am on January 18, 2011 Permalink | Reply

      It’s not the same plugin for WordPress hosted sites, right? The user interface looks much better on WordPress.com blogs.

      • Andy Skelton 11:09 am on January 18, 2011 Permalink | Reply

        The self-hosted stats plugin is a few versions behind the WordPress.com version. That will be remedied in the coming weeks.

    • Edward Dale 1:08 am on January 18, 2011 Permalink | Reply

      Looks a lot like my plugin ImmerStat. Great minds think alike!

    • Chris Brennan 3:25 pm on January 21, 2011 Permalink | Reply

      Did you guys decide to revert back to lines instead of bars? I just updated the self-hosted plugin and noticed it went back to that, which I quite like, although I’m somewhat surprised since I remember Matt trying to defend the switch to bars not long ago.

  • Andy Skelton 2:05 pm on July 27, 2007 Permalink  

    Stats Plugin Vulnerability 

    Anyone hosting their own blog and running the WordPress.com Stats plugin should update the plugin to version 1.1.1 immediately or apply the patch below. A critical SQL injection vulnerability was found and fixed. The bug could allow an attacker to steal administrative credentials. (WordPress.com bloggers are not affected.)

    Most users will want to download the latest version and simply copy the new files directly over the old ones. Subversion users may do `svn up`. Advanced users may apply the patch manually.

    Thanks to Alex Concha who found and reported the bug to me. He also provided the fix.

    • Moey 5:03 pm on July 27, 2007 Permalink | Reply


    • Jonathan 5:09 pm on July 27, 2007 Permalink | Reply

      Question: what if we didn’t upgrade to 1.1? Are we at risk?

    • machmoth 11:03 pm on July 27, 2007 Permalink | Reply

      Is it just me, or is there a tiny smile watching over me on the side of the new iframe? I see you smiley!

    • Jenny 9:01 am on July 28, 2007 Permalink | Reply

      I upgraded :D

    • alex 11:50 am on July 28, 2007 Permalink | Reply

      @Jonathan: yes, unless you manually fix the problem.

    • alder 5:54 am on July 29, 2007 Permalink | Reply

      is it intended that i dont see the ‘Blog Stats’ link in my dashboard when i’m not logged in as administrator? as normal user (even editor) i still just have the ‘Visit your Global Dashboard to see your blog stats.’-link there.
      actually i dont want to be logged in as admin all the time :/

  • Andy Skelton 12:33 am on May 7, 2007 Permalink  

    Automattic Stats, Day One 

    In its first twenty hours or so, Automattic Stats was blogged more than 50 times and downloaded more than 1,500 times. That’s not bad for a Saturday night launch!

    I heard it from a number of users that they couldn’t see their stats due to a “403” message. I’ve replaced that message with something more helpful. Victims of the 403 should try again now.

    While reading the many blog posts about Automattic Stats, I found the most common complaints to be about the way we serve the stats reports on your WordPress.com dashboard rather than your self-hosted dashboard. I’m still pretty sure we made the right decision for the following reasons:

    • It’s central. You can check the stats for all of your blogs in one place.
    • It’s easy on your host. Your server doesn’t have to ask our server for raw data each time you browse the reports.
    • It’s faster for you. Our servers can talk directly to the stats database and display the results unaffected by the loads and limits of your server. Sometimes handling all that data requires more system resources than shared hosting setups allow.
    • It’s quite reliable. See Barry’s latest post about our infrastructure.
    • It’s future-proof. Whenever we update the reporting interface, add features, improve graphs, fix bugs, etc., you don’t have to upgrade your plugin.
    • It’s ready now. We already spent a lot of time developing one reporting interface. It wouldn’t make sense to make you wait while we develop another one.
    • It’s not always going to be this way. We’re planning to expose API’s to let plugin developers query the stats database. This will open the field for anyone to create and share new reporting tools, even ones that live in your own dashboard.

    I think that’s enough justification. A few users have suggested ways to make the reporting more convenient. The most common suggestion, and the easiest to implement, was to add a link back to the blog’s own dashboard. You’ll find this new link near the top of every report page.

    Some folks have asked whether Automattic Stats can be used with WordPress versions prior to 2.1 or WordPress MU. Broad compatibility would be nice but it is not my goal.

    Use of the Automattic Stats plugin with WordPress 2.0.x is untested and strongly discouraged. I have not tested the plugin against any versions in the 2.0 branch because the plugin relies on some things that were not implemented in 2.0. Off the top of my head, $wp_the_query is required and admin_notices is recommended.

    Use of the Automattic Stats plugin with WordPress MU is untested and strongly discouraged. Of course, nothing prevents hard-core hackers from testing and updating the plugin for use with MU. I just don’t support it.

    Either of these causes could see a champion appear, in which case I may be interested in seeing the results of your research. I will not answer questions about the source code. If you can’t read it, you are not the champion.

    Now let’s give this stats thing a few more days and then we’ll see where it stands.

    • Rich Tatum 3:08 am on May 7, 2007 Permalink

      Andy, I have zero complaints about this. The only improvement I could think of while looking through my first day’s stas was that when I look at the traffic report/graph for individual posts, it would be nice to have sub panels under the graph showing me:

      – referrers for this item (not from my blog)
      – search engine keywords for entries to this item
      – exit clicks for this item (external to my blog)
      – next page clicks for this item (internal to my blog)

      That would tell me how each item is performing in terms of search engine optimization and conversion as well as whether others are linking to individual posts.

      All in all, a fine, fine tool. Thank you so much for providing it!

      BTW: I have blogged on it at my site.

      Blog Stats: Get your info-jones on with weblog traffic metrics



    • Chantal Coolsma 5:08 am on May 7, 2007 Permalink

      I like them a lot! Thanks!

    • adam 6:43 am on May 7, 2007 Permalink

      it is a strange objection, since most stats providers require you to visit their sites to view stats. it is, i suppose, atypical for a wordpress-only plugin to require it, though.

    • nursers 9:32 am on May 7, 2007 Permalink

      A superb plugin – thanks!

    • nerrad 10:06 am on May 7, 2007 Permalink

      I’m glad you chose to serve the stats on the WordPress.com dashboard. Having the stats of all my blogs located in one central location is a bonus. I only have two suggestions that would kick this stats plugin to the “uber” level:
      1. On our local dashboard along with the link to the global dashboard, display a minimal list of stats (such as total visits, total pages viewed etc.)
      2. Any chance of a feed tracker coming online in the future?

    • lasertargeted 11:00 am on May 7, 2007 Permalink

      For what it’s worth, stats seems to work perfectly fine in WPMU. Of course I only have a half dozen blogs under it right now, and there’s not any traffic yet to speak of, but it does appear to work fine from a technical perspective at least.

    • ma2t 6:44 pm on May 7, 2007 Permalink

      Great work and a great launch, I am using it on a few of my blogs and very much enjoying it.

      Less work for my server, more nice graphs :)

      Any thoughts about adding in feed stats data?

    • Ruff 8:50 pm on May 7, 2007 Permalink

      Actually, it won’t work with any theme that doesn’t have the

      I found my blog didn’t have that. I added it and now I can see the stats

    • HvI 6:08 am on May 8, 2007 Permalink

      Centralized collecting and reporting is a deal breaker for me. I have quite reliable and very well connected servers myself. I never use wordpress.com, so wordpress.com it is not that central for me. Most of all, just like I prefer to use WP on my own servers and not wordpress.com, I prefer to collect and report my own stats. – Free as in free speech. – Plus I don’t want the (visitor) data of my site been collected somewhere else.

      Why not give people the freedom to choose?

    • awallin 11:02 am on May 8, 2007 Permalink

      thanks Andy, very nice plugin.

      any idea of when the API will be made public. Would be nice to have “top posts” etc. listings in my sidebar based on these stats.

    • stygiansonic 6:52 pm on May 8, 2007 Permalink

      Thanks a lot for this, Andy. While I used Google Analytics for a while now, I’m finding that the WordPress.com stats are more relevant for blogs. I look forward to an API!

    • drmike 4:58 pm on May 9, 2007 Permalink

      Seemed to work fine on WPMu. Removed it though as I had hardcoding in my own API for testing and didn’t want to leave it in there due to lisencing issues. If we had, folks would have to log in to wp.com under my own account.

    • drmike 5:00 pm on May 9, 2007 Permalink

      Why not give people the freedom to choose?

      Folks have freedom to choose. Just use another stats system. Urchin/ Google Analytics is the same way. All the data resides on Google’s servers. I just use out own stats program.

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc

Get every new post delivered to your Inbox.

Join 2,058 other followers