April 2008

Hello Magento, Goodbye Mambo

MagentoLast week marked the official release of Magento 1.0, an open source ecommerce platform. Magento has been on my radar scope for some time thanks to those who have left comments about it here. Since, I likely will have need of a good shopping cart this year for a planned project, I've decided to put some focus on Magento. I will be removing Mambo from my top 30 "CMS Focus" list to make room for Magento. My apologies to Mambo fans.

Technorati ignoring vulnerable Wordpress blogs

A couple months ago, Technorati announced that users of Wordpress needed to upgrade to the latest available version (now at Version 2.5). This week, Technorati announced that blogs remaining vulnerable to identified security exploits may no longer be indexed by their service.

Because of this ongoing problem, we're discontinuing processing crawls of blogs that exhibit common symptoms of being compromised. We strongly recommend upgrading your WordPress installation. Even if you haven't been afflicted by a compromise, by the time you are aware that you have been a number of negative consequences may have already occurred (for instance, flagged spam by Technorati, Google or Yahoo!) -- this has been reported by many WordPress users.

By not upgrading your software, the search engine services may block your site from being listed. I can't think of a greater incentive to update your content management software to the latest version than the threat of being delisted. This is a bold move by Technorati. I'm personally glad Technorati is taking a stand against sites hosting older versions of Wordpress with the known security holes. In my opinion, there really isn't a good reason you shouldn't be upgrading your Wordpress site to the latest version.

The Dangers of Reviewing Open Source CMS

The April issue of Adobe Edge contains the article, Review of open source content management systems. The article provides an overview of what the author describes as "five of the top open source software (OSS) solutions". The five open source CMS included in the author's list are CMS Made Simple, Drupal, Joomla!, WordPress, and XOOPS. After reading the article, I found myself wondering how we "reviewers" can actually improve our reviews of open source CMS. More importantly, I've come to the realization that I can no longer claim to be non-biased in which CMS I believe is the best out there.

The author does a fine job in the article describing the similarities and differences between the CMS being reviewed. However, one of the issues I have in this article and many others I've read that review CMS is the big jumps in the conclusion:

Drupal, Joomla!, and XOOPS are best for building an e-commerce site because all three offer:

  • Inventory management
  • Support for third-party payment processing mechanisms (such as PayPal)
  • Modules for shipping and sales tax calculators
  • Shopping cart functionality

While it is true that Drupal, Joomla! and XOOPS can do e-commerce, none of these CMS can do that straight out of the box. I can just imagine a shop owner or design company trying Drupal, Joomla!, or XOOPS for the very first time and wondering, "how the heck do I get a shopping-cart into the CMS?". While the author does hint in the article that third-party modules are needed to make the e-commerce work, I think the author would have been better off better explaining that "some work is required" to get those features into the CMS.