I've been so head down, on several projects professional and personal, that I only just noticed a few weeks worth of error messages in Cutter's Crossing's email box. A very odd error about missing a captcha-hash-variable kinda thing (don't have one handy). So, I get my next door co-worker to pull up my blog and ask him to post a comment, any comment. Low and behold, in place of the captcha there was a broken image icon. That wonderful clear box with the red X going through it, that we all know and love. Simply reinitializing BlogCFC took care of the issue, but I realize I've missed out on valuable feedback.

If you're reading this, and you tried to comment earlier, please try again, and I'm sorry for the trouble. I'll try to keep a more vigilant eye.

In the meantime, I'm looking for some really outstanding (public) examples of a drag-and-drop page content editor interface. Some experimenting with some of the Ext (2.1) sample code says I should be able to do it, but I'm looking to see some clear cut, and tested, solutions. BTW, if you haven't looked at the extended examples that they put out with the 2.1 update, then you should. There's some very nice stuff in there, particularly dealing with layouts.

OK, if I had hair I would have pulled it out by now. For several months I've been getting this error from BlogCFC, but I can't track the true source to remove the offender:

Script Name: /rss.cfm?mode=full&mode2=cat&catid=9856ECF2-3048-71C2-17879EB46D54D46F Detail: An invalid XML character (Unicode: 0x19) was found in the element content of the document.

I can't find this character anywhere. No clues at all. But, it's playing havoc with some RSS readers, apparently, and loading my inbox. So, anybody have some suggestions how I might find this?

OK, last night I upgraded to BlogCFC 5.9, which Ray released the other day. Pretty heavy update, with over 30 file changes in the readme, but very smooth when using WinMerge (thanks to Mark Drew for that little tip).

One item of interest, though. Ray mentions in the readme that he's stopped logging the changes in the document headers, stating that it's redundant to place them there and within the readme doc. He also states "I decided I'd skip that since BlogCFC 6 will have new files." I also noticed, while reviewing the changes, that he has code in place for checking the server version. CF 8 specific changes on the way? We'll have to wait and see.