I've mentioned on this blog a few times that CMSReport.com was never really meant to be a business or publication. It just happened. Six years ago, I started this journey I'm on with just my fascination for information systems and the little knowledge I had obtained on my own about content management systems. I was hungry to learn more and I started this site simply as a place to store my personal notes, bookmarks, and possibly share ideas with a few others. As many of you know, a lot has happened since the early years and I've been at crossroads for how to take CMS Report to the next level.

Last December, I received a call from someone that wanted to bounce some ideas off me and potentially partner with me to make this site something more than it is now. For a myriad of reasons, I'm not ready to name who I talked with so lets just call him "Mike". Mike's solution was not only for him to partner with me but also for me to become a client of the company he co-founded. While I liked the ideas Mike was bringing to the table, I have to tell you that I was a little apprehensive about letting someone else build a new site for me.

When it comes to information technology, I've been blessed with many talents. Six years ago I wisely picked Drupal as the CMS to run my site on. Not only was this open source solution the perfect fit for me to manage my content, Drupal also gave me the freedom and control I needed to run the site the way I saw fit. Over the years Drupal has allowed me to pick and modify my own themes, choose my own modules, and host my site on servers of my own choosing. The problem with the "all me" and "full control" approach is that it consumes a lot of valuable time that I could be using more productively elsewhere.

As expected, this week the Drupal development team released Drupal 7.3 and Drupal 7.4. 

Drupal 7.3, a maintenance release which fixes security vulnerabilities is now available for download.

Drupal 7.4 also fixes other issues reported through the bug tracking system.

Upgrading your existing Drupal 7 sites is strongly recommended. There are no new features in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement.

I usually don't mention upgrades of content management systems that introduce no new features to the user. However, this particular upgrade was personal as it rolled back some previous changes that were causing a lot of grief for a number of contributed modules I want to use on this site.  Needless to say, I upgraded my sites to Drupal 7.4 within hours after the new version was made available to the public.

Lots of changes are starting to take place here at CMS Report. We're now running on a new version of the Drupal content management system!

Over the weekend, I decided to pull the trigger and upgrade CMSReport.com from Drupal 6 to Drupal 7. It's hard for me to believe that it has been almost half a year since Drupal 7 was released. This was a frustrating upgrade for me as I've traditionally upgraded CMS Report shortly after any new release of Drupal is out. In fact, I have sometimes upgraded a site before the release is official. As a content management system, my five-year hate-love relationship with Drupal is still going on strong.

Despite the usual learning curve associated with a major Drupal upgrade, I ran into two additional problems I've never had to face with this site. First, the CMSReport.com of today is a much more complex site to run, maintain, and upgrade then it was in 2008. With the number of readers and sponsors this site now sees, I just don't have the luxury of blowing up the site and say "oh well" lets start again. Secondly, the selection of premium or contributed themes available for Drupal 7 just plain sucks (there, I said it). I must have spent half of my upgrade time just searching for and then tweaking a Drupal 7 theme. People often complain about the lag time between a Drupal release and the availability of third-party modules. In my opinion, it is the lack of theme development going on with Drupal that is the real problem with Drupal upgrades.

It was five years ago that I posted in programmer tradition here at CMS Report, "hello world". At the time, I expected CMSReport.com to be around for only a couple years which was more than enough time for it to fulfill my purpose. At the time, I had an academic interest in information systems and found that Web-based content management systems were a nice way to put theoretical ideas into practical know-how. This site focused on content management systems in hopes of meeting the few other people out there that shared my interests in CMS.

In that first post, I actually wrote more than "hello world". The full title of the article was "Hello World, New Version". The phrase "new version" was in reference to CMSReport.com not being the first site I created to focus on the CMS.  A couple years earlier, I had tried to start up a website called WebCMS Forum. The online forum was intended to be a "place for those with a passion for web-based applications such as portals, blogs, and forums". I spent a lot of time and money on that site, but in the end few visitors joined in as members to talk about content management systems with me. If Twitter had existed back then I would have easily tweeted "WebCMS Forum RIP #failed".

Looking back at it now, I'm convinced CMS Report is a success because of my experience from failing so miserably with WebCMS Forum. Previously, I had tried to build a site for others to express their passion and obsession for their favorite content management systems. Here at CMSReport.com, I took the opposite approach and built the site for the sole purpose to talk about my passion for content management systems. It was a crazy idea to put my opinions at the center of CMS discussions as even now I do not consider myself an expert in content management systems. It was only by circumstance that I later realized people are attracted to other passionate people that ask questions and are willing to go at great lengths to find the answers. If you're looking for the facts you go to Wikipedia but if you're also looking for great discussion from people asking the same questions as you are; it is the blogs you seek.

Slowly but surely, CMSReport.com has turned into a nice side business for me. The problem is that this site has grown to a point that it demands more of my time than I can currently offer it. The future of CMS Report is now sitting at crossroad. I plan to be spending the next few months deciding where this site should go from here.

Some of the options I am considering for this site include:

• Partnering with others to build a bigger and better CMSReport.com. I wouldn't mind seeing this site become more of a community driven site.
• Selling CMSReport.com, both domain and site, to a company or someone whom can take this site to the next level.
• Returning CMSReport.com back to its roots as a personal blog.

Five years ago, I started CMS Report by wanting to build a website focused on reporting today's news in the world of content management systems (CMS). At the time, I was obsessed with information systems and realized that a CMS is one of the best vehicles to putting the ideals of information systems into practice. My goal was to either blog here at the site about content management or to refer others to CMS stories posted elsewhere. My strategy was to make this site my personal bookmark for stories that would interest me and perhaps a few others that might share my interest in this emerging market of Web content management.

Like most website administrators, I have a long history of fighting spammers and protecting my sites from unwanted content. Over the years I've used a lot of tools and services to block spam from reaching the pages of my sites. In recent years, the service I've relied on most heavily is Mollom.  Mollom is a web service that helps you identify content quality and, more importantly, helps you stop spam on your blog, social network or community website

Overall I've been very happy with the spam filterering Mollom provides for my sites. However, occasionally Mollom can be too aggressive and remove legitimate story and comment submissions. And when I say "remove" I most definately intend to use the word in the literal way. You see, up to now, Mollom had an "all or none" approach to rejecting or accepting spam. When your stories or comments were rejected, the content submission was simply discarded without review by a human.

If you've ever submitted good clean content to CMSReport.com or another site only to only have it identified and discarded as spam, you have every right to be upset with spam filters. Over the past couple months, I've had a number of people upset that the spam filtering CMS Report has been using rejected their story submission. This may not be all the fault of Mollom either as I was also using the Bad Behavior module too. My apologies to everyone that has gone through this experience when they've submitted legitimate comments and stories to this site. Unfortunately, without spam filtering the content on this site would not be good to view. Spam filtering is a necessary part of maintaining a site open to the public.

Luckily, there has been some improvements in the Mollom for Drupal module that should keep your posts and comments from getting discarded while continuing to protect this site from spam. The module has now been improved to to retain spam comments as unpublished posts in a site's moderation queue. So we're giving the new module a try. I won't promise that your content will not be identified as spam, but I do promise you that every intent is being made to review your comments and stories for publication.