If you have issues with the latest update (v.1.4), keep those feedback coming; please add them in the comments section below. I am currently working on the fix as of this moment.

The latest version is up at WP.org’s plugin repository. As mentioned in the README file:

1. Added the Award option which will display image or icon of a medal/badge once a commentator reaches a certain number of comments determined by blog owner.
2. Modified the form to allow default values to be entered automatically when initialized (i.e. widget’s Save button is pressed).
3. Added support for setting default Gravatars to 404, Mystery Man, Identicons, MonsterIDs or Wavatars.
4. Repaired the query statement for filtering e-mails.

Thanks to Konsti for the award/gaming suggestion. For now it only takes into account a single range. Hopefully in the future the widget can scan based on how active a commentator is, then award these users based on different levels of comments contributed.

Change number 2 is mainly for those who’ve complained that the top commentators wasn’t showing even after the widget is installed. Remember to go to the Widgets option, add the TCW in, and click the Save button to initialize its values. The widget won’t display anything if you do not press the Save button and get those default values entered into your WordPress options database.

A year ago, user iferg requested that the TCW supports other default Gravatars like Identicons, MonsterIDs and Wavatars. I finally had a chance to read up on this, and added that option into this widget.

Last, but not least, user ostin654 contributed a fix to the e-mail filtering bug, so I really appreciate that!

If you would like me to keep updating this WordPress plugin, I would like to ask just one thing from you – if you have a bug and/or a fix to report, or if you have modified the codes in any way that would benefit the TCW users, please share it with us. I’ll be sure to credit you and add those modifications in the next update. This would be the best way to continue making Top Commentators Widget useful and fun to use.

Please skip the rest of my post below; these are just notes to self so that I’ll remember how to update the TCW repo next time.

For new projects (Tortoise 1.7)

1. Create a new folder in your computer.
2. Download and install TortoiseSVN.
3. Right-click on the new folder and select TortoiseSVN -> Create repository here.
4. Right-click on the new folder and select SVN Checkout.
5. Set the WP.org Subversion Repository URL (remember, this is NOT your WP.org plugin URL; find the link in the Developers tab) and WP.org login info.

To edit code

Change the stuff under the Trunk folder within the new folder you created.

To update code

Right-click on the new folder or the Trunk folder itself, and select SVN Commit to check the files in. Add in the message “Version #.#” in the message section.

To tag code

1. Create a new folder within the Tags folder, naming it with the same version number as your current HEAD/trunk.
2. Copy all files in Trunk and paste it in the Tags folder with the version number.
3. Right-click on the Tags folder and select SVN Commit.
4. Add in the message “Tagging version #.#” in the message section for housekeeping purposes.

No related posts.

I am way behind schedule on the TCW update, I know (and thanks for reminding me, Konsti!). Yes, I’m actually done with the changes – 3 of them, in fact – and I am ready to put it up into TCW WordPress.org’s Extend at latest by tomorrow.

I got to be honest here. My delays are almost always (99.99% of the time) caused by two things – one: finding the time to do some coding, and two (a more embarrassing fact): I have little to zero clue how to use Subversion.

I know, right?! How could I, after more than three years developing TCW, still not get a handle of using it? More shameful is the fact that I’m a programmer by trade. Boo me.

It was suppose to be easy, this check-out, edit, commit, check-in thing. There’s a myriad of how-to posts specifically on using TortoiseSVN for WordPress.org. And I’m a programmer, for heaven’s sake! I should know code versioning!

The truth is, I’m a solo programmer and I don’t have to share my code with anyone. So all I needed to do was to create a new folder and dump my latest codes in there. That’s my versioning. Even if I did need to use versioning, it ‘ssuppose to be as easy as using Google Code.

So why is it that every time I tried to commit using Subversion, it Just Didn’t Work ™? I didn’t see the change in trunk to the latest version number. My changelog sometimes reflected the change in WP server, then suddenly I didn’t see it anymore. Went through the steps again, from1 to 10 (or 11, or 20… I lost count of the many how-to I followed).

After nothing seemed to work, I went off the beaten path, and tinkered those options out of frustration. Then suddenly, Eureka! It’s there in WP.org, my latest version of TCW in all its glory! My heart sings Hallelujah as I typed down what I’ve done the best I could, hopeful that whatever I’ve typed would become my next blog post on my stagnant WebGrrrl blog.

But alas. This problem feels like a nasty cycle of procrastination and/or forgetfulness and/or carelessness. Take your pick.

You’ve read my previous post on how “active” I was these past couple of years. So tonight, I shall once again go through the process of committing my latest Top Commentators widget update, typing those steps again into a draft post, crossing my fingers and hope that this time, that post won’t disappear into thin air and I’ll not only have the latest TCW up for you, but also my next Post Of The Week ready for primetime viewing.

BTW, here are some blog posts from WebGrrrl.net readers who are taking on the PostAWeek 2011 challenge:

• Like giving up on sex! by LaViaP The Geek

No related posts.

Yes, my friends, the Top Commentators Widget is now officially part of WordPress.org Plugin Directory. I was driven to finish the setup for the widget’s hosting to WordPress.org, especially after seeing the built-in plugin update notifier in WordPress 2.3.

I am SO GLAD I finally completed what I had planned to do since June, but as you have read in my previous post, the tedious work that is Subversion was what made me chickened out of doing so sooner. I’m grateful that Ronald at Weblog Tools Collection did that tutorial on TortoiseSVN and explained in painstaking details how I should go about setting everything up. The slightly intimidating part of hosting in WordPress.org was actually the preparation of the ReadMe file — I’m glad the WordPress team prepared a readme validator to make sure I formatted it well.

Of course, I’ll still be maintaining the Top Commentators Widget page in my blog, but I’ll recommend everyone to start visiting the Top Commentator Widget in WordPress.org as the information in that page is more easy on the eyes.

No related posts.