Yes, another challenge for those of us that work in the IT department! Just what we wanted, right? We're spending all this time reworking the corporate Intranet so everyone can collaborate better. What happens when we're done and no one shows up?

It could be tempting to conclude that because your employees enjoy keeping a personal blog or spending time with contacts on social networking sites like Facebook and LinkedIn, that they would want to participate in an internal corporate version of those sites. But don't be so sure.

PC World recently released their list of the 15 biggest disappointments of 2007. Two of the items on that list didn't surprise me, but two other items were shocking to see on the list but in reflection absolutely true.

I wasn't surprised to see that both Apple's "Leopard" OS 10.5 (#8) and Microsoft's Windows Vista (#1) on the list. I've been talking about my disappointment on the state of the computer desktop for sometime now. I'm just glad to see others have noticed the problem so I don't look like Mr. Glum to everyone.

However, I was surprised to see two content management system related items that made the list.

The latest review I've read on the KDE desktop is from Ars Technica, A first look at KDE 4.0 release candidate 2. While the author notes that a lot of improvements still need to be made to KDE 4.0, overall it should be an impressive desktop. I'm contemplating that my next laptop will be fully Linux and hoping KDE 4.0 will bring enough Wow to impress others on why I didn't choose to go the Windows or Mac route.

As a teenager in the 1980's, I mowed lawns for three reasons. I mowed lawns to save money for college. I mowed lawns for spending money on the weekends. Finally, I mowed lawns to buy the Commodore Vic-20 and eventually I purchased the Commodore 64. I was neither envious of the school's Apple II's nor my neighbor's TI-99/4A. I had a Commodore 64 and I was cool even before geeks were cool.

I felt fear, awe, and even some admiration when I read at CNET about the latest social engineering attack dreamed up by those ingenious Russian hackers.

Those entering online dating forums risk having more than their hearts stolen.

A program that can mimic online flirtation and then extract personal
information from its unsuspecting conversation partners is making the
rounds in Russian chat forums, according to security software firm PC Tools.

Drupal 6.0 Beta 3 was released just before the Thanksgiving holiday. As in the past, I wanted to use CMSReport.com as a "live" test site for the beta/release candidates of Drupal as I did with Drupal 4.7 and Drupal 5. However, as this site has matured, so has my reliance on too many contributed modules currently not supporting Drupal 6. So for now, I've decided to place Drupal 6 in a subdomain, drupal6.cmsreport.com.

I am excited with what I have already seen in Drupal 6. I consider version 6 to be Drupal on steroids. Drupal 6 has a lot of performance and power improvements that are already apparent even in the Beta. Put it this way, the day the Views module is ready for Drupal 6, is the day I go live with running CMS Report on Drupal 6.

Yesterday, I upgraded the PHP version on my server from 5.2.4 to 5.2.5. PHP 5.2.5 brings improved "stability of the PHP 5.2.x branch with over 60 bug fixes, several of which are security related". I also reintroduced eAccelerator back onto the server. I stopped using eAccelerator last spring, not so much because I had any real issues with it, but because I spent the summer months hosting my sites on the cheap.

A couple months ago, I experienced a number of errors at my Drupal site that all pointed to a corrupted database. I believe the problem likely was the caused by a sloppy export/import I performed with the MySQL database while moving the site to a new server.

While my particular database problem was an easy fix, if you really don't know much about databases you may find that you really need some guidance on how to solve problems like these. This article is the process I went through to correct this particular MySQL database problem in Drupal 5 and some general database rules that show why this problem occurred in the first place.