Sofie Estolloso Hofmann Designs International

I have been using Counterize II WordPress Plugin for quite sometime now. Counterize II is actually a very good and a very useful WordPress Statistics Plugin. It is always handy as I see the statistics at the WordPress admin panel as it saves the statistics data in my database. This is actually my problem now, as it is not using external libs, and I don’t want to delete the data, they are occupying too much space of my database.

My dilemma now is whether I should stop using this WordPress Plugin or just delete the data before so as not to occupy too much space of my database. I am not very particular about statistics but once in a while it just makes me smile looking at the data. Although I am not a Statistics freak, I am also using WordPress.com Stats and Google Analytics. I like both WordPress.com Stats and Google Analytics but Counterize II has features which I like too which I did not find at Google Analytics nor WordPress.com Stats. Maybe I have not fully explored WordPress.com Stats and Google Analytics yet as I do not often check my statistics anyway.

While writing this, I thought, ok, I will give it a try one more time. I will check WordPress.com Stats and Google Analytics thoroughly first. If I think it is time to let go of the Counterize II WordPress Statistics Plugin, then I will just let it go.

And oh, I am hoping that one of these days, that people who developed WordPress.com Stats would try to get hold of the Counterize II Plugin developer and maybe come up of an idea of combining the other features of Counterize II with WordPress.com Stats.

Wouldn’t it be great?

Related links: Counterize II WordPress Plugin, WordPress.com Stats, Google Analytics

Several weeks ago WordPress 2.5.1 was released but it was only last week that I was able to upgrade my blog (SofieHofmann.com Blog) and all the sites (Sehdi.com, Weggis.net, Pandan.ph among others) that I manage and maintain using WordPress. I was on vacation for at least 3 1/2 weeks.

Well, upgrading the blog and the sites went fine. I just followed my 10 Steps to upgrading WordPress.

I noticed something though at the Plugins section regarding Widgets before I upgraded the blog and sites using WordPress 2.5 and even after upgrading to WordPress 2.5.1. Did you notice those remarks stating that a plugin has a new version available? Well, the link of the supposed new version of the Widget mentioned does not match to the particular Widget being used.

Let me illustrate it…

First Example:

There is a new version of Simple Recent Comments Widget available. Download version 1.2.1.20070210b here or upgrade automatically.

This text “Download version 1.2.1.20070210b here” is being linked to the Sidebar Widgets page in WordPress.org (as of this writing, the version is 1.2.1.20070210b as it may change later on) and not to the Simple Recent Comments Widget page (if there is any as I did not find the page when I search WordPress.org for it).

Second Example:

There is a new version of WP-PostViews Widget available. Download version 2.20 here or upgrade automatically.

This text “Download version 2.20 here” is being linked to WP-DBManager page in WordPress.org (as of this writing, the version is 2.20 as it may change later on) and not to the WP-PostViews Widget page in WordPress.org (as of this writing, the version is 1.20 as it may change later on). I am actually using the simple WP-PostViews (current version 1.20) and not WP-PostViews Widget.

Then I saw a discussion about WP-PostViews Widget at the Wordpress Forum, and Lester Chan (GaMerZ), the WP-PostViews and WP-DBManager Plugins developer, have explained why. Kindly click “wp-dbmanager is showing as an upgrade for wp-postViews Widget” for information.

Well, we’ll just have to bear with it, sooner or later, they’ll find the solutions for it. Creating Plugins for WordPress is voluntary and we should be grateful that we are benefiting from each developer’s work.

Kudos to the WordPress Plugins Developers!