This blog turned one year old on Sunday. The inaugural entry, My First Blog and How To Install WordPress, was posted on October 18th, 2008.

Happy Birthday Blog!

For some reason, it feels like I’ve been at this a lot longer than one year.

Some statistics related to this blog during the past 365 days:

• 224 posts
  • 195 Virtualization related
  • 30 Non-virtualization related (typically other technologies and a few personal)
  • Average of one post per every 1 1/2 days
  • Using a very conservative estimate of 2 hours spent writing each post, total time spent writing:
    • 448 hours
    • 19 days
    • Almost 3 weeks
    • Doesn’t include any lab time
• 179,389 Unique visitors
  • Generating 5,399,277 Hits
  • Consuming 71.36GB Send (upload) traffic
  • Costing $1,199.88 in bandwidth
  • Plus another $1,800 estimated in rack electrical/cooling
• 743 legit comments (approved)
  • Average of 2 legit comments per day
• 7,873 spam comments (blocked and IP banned)
  • Average of 22 spam comments per day
• 90 Tags
• 14 Active WordPress plugins
• 7 Inactive WordPress plugins
• 4 Sponsors
  • VMPeople.net
  • Hyper9
  • vWire
  • TrainSignal
• 1 Theme change
• 3 VMware exams passed
  • VCDX Enterprise Administration exam
  • VCP4 exam
  • VCDX Design exam
• 2 VMworlds attended
  • VMworld Europe 2009
  • VMworld 2009
• 7th most popular virtualization blog as rated by the VMware community
• 1 vCalendar idea
• 1 vExpert award
• 0 VMware NFR licenses received
  • Out of a dozen or so requests
  • Over the course of 2+ years
• Established about a million virtualization industry
  • Contacts
  • Friends
  • Acquaintances
• Through
  • Blog
  • Twitter
  • VMworld
  • LinkedIn

Thank you for reading. I look forward to another great year with more VMware virtualization information to share! A special thank you also goes out to other bloggers and VMware virtualization community members for sharing your time and knowledge and continuing to inspire me to do the same.

I received the feedback that the blog was not easily readable on mobile/handheld devices (Blackberry, iPhone, etc.)  Taking the suggestion from a few friends to install the MobilePress plugin for WordPress, the blog was mobile friendly within five minutes. While I had always “dealt” with the blog’s rendering on my own Blackberry, I hadn’t realized it could be improved (with so much ease).  I like it much better now as a lot of the “noise” has been removed. Thank you for the suggestions and feedback! Update:  The MobilePress plugin has been disabled for the time being due to a bug.

Blog maintenance tonight:

• Upgraded the Pixeled theme from version 1.1 to version 1.5.
  • This theme appears to be compatible with WordPress 2.7.
  • Had to re-hack a few of the theme files for blog customizations I made.
  • No known cool improvements other than bug fixes.
• Major WordPress upgrade from 2.6.5 to 2.7.
  • Followed this guide. Fairly straight forward. Maybe a bit advanced for the less technically inclined. Theme/plugin compatibility is the big deal here.
  • Some plugins listed on the compatible list. Some were not listed at all. Proceeded with upgrade anyway.
  • Before upgrading, backed up database and entire blog directory. Disabled plugins (re-enabling plugins retains plugin settings thank God).
  • Widgets seem to be unaffected.
  • After all was said and done, one plugin isn’t working: WP Super Cache. The plugin configuration page is blank and I don’t see any cache directory on the server nor do I see a “delete cache” link in the admin console. I went ahead and disabled this plugin until this can be worked out. The blog will still run without it, however, each page will now be dynamically rendered by the PHP engine thus chewing up quite a bit more CPU cycles on the web server. I host my own blog so there is no risk of being evicted by a web host for utilizing too much CPU which has happened to the more popular bloggers like Scott Lowe at VMworld 2008 and Rich Brambley. Honorable mention, Mike Laverick of RTFM Eduction was also shut down due excess bandwidth utilization. These web hosts obviously don’t know who they are messing with
  • Initial observations:
    • I knew it was a major upgrade and unfortunately for the readers, most of the cosmetic improvements happen behind the scenes in the admin console which the reader doesn’t see.
    • Ok, the new console is refreshing and cool (literally cool with a cool-like blue theme – I’m getting the chills as I write this…)
    • Everything is moved around completely. It’s the Windows 3.1 Program Manager to Windows 95 interface migration all over again. However, the concepts and building blocks of WordPress don’t really change, so seasoned WordPress veterans should be able to adapt quickly just as experienced Windows administrators did in 1995.
    • If the redesigned UI doesn’t entice you, the promised future ease of WordPress upgrades should be enough to justify the jump to version 2.7.
    • I hope the WYSIWYG editor is fixed and doesn’t randomly garf bulleted lists and font formatting like the 2.6.x versions did. I often had to use the HTML tab to manually fix things in source view using my old school HTML tag skills.
    • The WYSIWYG editor seems a tad bit more sluggish but in fairness that is probably because I’m on my slower computer right now. I write most of my blog posts on my faster computer.
    • The Dashboard now has something called “QuickPress” which reminds me a bit of Twitter micro-blogging with tag functionality. It’s basically a fast track method to post quickly from the Dashboard view without the bells and whistles that the WYSIWYG editor provides.
    • There’s a Word Count display underneath the WYSIWYG editor. For those who are paid to blog, this should come in handy. I wish there was also a Quality Count. I could use that to help me with some of my posts.

That’s all for now. I waited for the suckers… ahem… the early adopters… to upgrade to 2.7 first so I could watch for fallout. Not much fallout to speak of really. 2.7 went through many beta and release candidate revisions. It was cooked pretty good and the quality shows. Just make sure you back up your database and content directories before the upgrade so you have a good recovery point. I’m off to the couch to watch a few more of my Twilight Zone Xmas DVDs (seasons 1 through 3). Tomorrow morning I go out to breakfast with friends and then to the Metrodome to watch the clueless Minnesota Vikings lose to the New York Giants.

Update: Flickr Manager 2.1 doesn’t work after the upgrade to WordPress 2.7. When I click on an image to insert, the Flickr Manager hourglass just spins its wheels and never returns to the blog post inserting the image. I’ve restarted IIS services a few times to no avail. For my blog entries that have inline images, this really sucks because now inserting images is a much more manual process where I have to go out to Flickr, find the picture within the correct set, click on it, view all sizes, then copy the image URL location.

Update: The Flickr Manager 2.1 issue has been resolved.  I found this gem on the support forums.  Apparently the author fixed the issue and slipped it back into a re-release of version 2.1 (download the updated 2.1 version here) without telling people who downloaded the original broked version of 2.1 before January 2009.  My personal and professional opinion is the version should have been incremented from 2.1 to 2.2 but nonetheless I’m happy now.

Update:  Fixed WP Super Cache not caching and blank configuration page issues:

• The enabling of the WP Super Cache plugin was not creating the wp-content\advanced-cached.php and wp-cache-config.php files like it was supposed to.  This FAQ lead me to the manual creation (copy) of these files which fixed the blank configuration page problem.
• Once the config page was working I thought all was well, but it wasn’t.  The plugin wasn’t caching.  I was able to witness this by no cache files being created in the wp-content\cache\ directory.  Upon further examination, a default setting for the plugin is to reject caching of pages with the string index.php in the URI.  This is ridiculous because every blog page served up by WordPress on the web server has the string index.php in it!  This essentially told the plugin not to cache any of the blog posts.  Simply removing index.php and saving the configuration jump started the whole thing and now everything is working correctly.