So after spending way too much time fighting XML-RPC, I've decided I just don't want to deal with it. Unfortunately, I know some of my users love it. Dan Switzer sent in some interesting XML-RPC mods. I've checked these into source control. If folks who use XML-RPC can test it, I'd greatly appreciate it. You can find details of his changes here:

My BlogCFC mods for Windows Live Writer

If I can get a few of you guys to A-OK it, I'll make it part of the official zip.

I'm going to be lazy and just paste in the release notes. I'm watching the trampoline event at the Olympics while I do this - and you know what? The trampoline is freaking cool. Anyway, here is the 001 release for 5.9.1:

/client/stats.cfm - Oracle fixes (thanks to Steven Tomcavage)
/client/index.cfm - Forgot to use #application.rooturl# in podcasting support - thanks to Marion Bass
/org/camden/blog/blog.cfc - Include author name in emails
/install/mysql.sql - Changed the text fields in entries (body, morebody) to longtext. It may be a good idea for you to manually update your table.
/xmlrpc/xmlrpc.cfm - when deleting, clear cache
/client/tags/textarea.cfm - make the custom tag correctly handle a closing tag
/client/admin/page.cfm - Use the textarea custom tag. For those who modded textarea to use an RTE, it adds RTE to the page editor.

BlogCFC isn't me. It may have been me - back in the 1.0 days, but for a very long time now BlogCFC has had the help of numerous people in the community. This has helped BlogCFC grow incredibly, and for that, a lot of praise goes to those of you reading this blog.

I've mentioned many times why V6 is taking so long, but I've decided that I really need to stop making excuses and recognize the fact that BlogCFC needs to change formally in order to grow.

So I asked for help to a set of friends and colleagues who I thought would be a good addition to the team. The idea here was simple. Set up roles and responsibilities and then step out of the way. I ensured they all had all the access they needed and now I will no longer be a stop gap to BlogCFC development. BlogCFC is no longer me. Thank God.

So who are the foolsvaliant volunteers? Meet the Management Team:

• Architect/Team Leader: Me. Basically I'll spend most of my time at the model layer and serve as the development director.
• Website Manager: Charlie Griefer. The idea is to change BlogCFC from a blog into a real product site. Things like docs, release notes, screen shots, etc.
• Installer: Scott Pinkston. Yes, there will be an installer for BlogCFC. Now stop asking! (Or keep asking, but bug Scott. ;)
• Admin: Scott Stroz. I don't have huge changes planned here, but I do want to make it a bit prettier. My #1 goal though is to ensure that writing blog entries is as quick and simple as possible.
• Themes: Dan Vega. As folks know, Themes are a part of V6. Partial theme support is already done. Dan will be responsible for more of the maintenance side of this - and some of that is going to be revealed in later builds of V6.
• Testing/QA: Brian Kotek. This is two fold - writing unit tests and massaging incoming bugs (removing dupes, etc). This will be easy since BlogCFC has no bugs and runs perfectly all the time.
• Documentation: Lola J. Beno. Lola has already helped with the docs before, so she was a natural fit.

So - there ya go. The team. Let me personally say thank you to them all!

I've just checked into the V6 SVN repo the new render support for BlogCFC. This is a major new way to do plugins for BlogCFC. I've long had a way to dynamically add support for <foo> type tags. This was done via CFCs, yet no one actually ever used this feature. I didn't really document it so that's my fault.

In V6, you can now add support for tags via custom tags. Let me give you an example. In the render/content folder you will find a custom tag named code.cfm. The mere existence of this tag will make BlogCFC entries (and pages) recognize <code> in your data. You can pass any arbitrary argument in the code tag, <code style="sql">, and they will be passed as arguments to the tag. Also, if you do:

(FYI, "fcode" is there because I just realized I probably can't use the code block in BlogCFC to demo a code block. ;)

Anything inside the tag will be passed to the custom tag as the content argument. So here is the code support as it stands now:

Where it gets cool is - in the next update, I'll add support for:

This will make it so you can include JS files and even if 2 instances of the tag are run, the JS files are included only once.

Anyway, the point of all of this is to make doing plugins/add-ins for BlogCFC significantly easier.

Comments welcome.

That's it. 5.9.1 is done and in SVN. This is really the final release. No more mods. I'll do a more formal blog post tonight, but if you want the bits, get the latest.

Changes:

• Brian Kotek added the ability to moderate (approve) comments via email. This now means you can delete or approve comments via email w/o logging in.
• Bug fix in entry editing and related entries.
• A minor thing that annoyed me - if you search for fOo, and match on foo, the display on the search page showed fOo, not the original case.

The title says it all. The final build of BlogCFC 5.9.1 is now checked in. This includes:

• Brian Meloche's Podcasting support
• Ability to manually set the enclosure
• A few bug fixes

Note - this "final" build really isn't final per se. I need to update the DB install scripts and update the instructions for some of the new features. Please give it a test guys!

The initial work for BlogCFC 5.9.1 is checked into the SVN repository at RIAForge. This is not the complete 5.9.1 build. The plan is to release 5.9.1 by the 15th. Included in this build is:

• One click comment kills. Now when the admin gets an email, he can click a link in the email to instantly kill the comment. No need to logon.
• Ability to subscribe to entries without writing a comment.
• Small thing that bugged me - the Entries link in the admin now uses the SES url.

Please see the readme for more detailed information and please note you must modify your database. I included a txt file about the upgrade. The SQL scripts aren't updated yet.

What's coming for the rest of 5.9.1? Podcasting support.

Checked in:

1) We now support pages (dynamic, simple CMS stuff) and the pages used our template system.

2) Comments are now displayed. Please note the RED template was updated, not the green template. The comments.html works much like entries.html, giving you the ability to put stuff on top, between comments, and before the end. Also note the token $$NAME, $$URL, and $$NAMEURL. Name means the commentors name. URL is their website. NAMEURL means: "Return a linked version of the name if they supplied a web site." Most folks will want to use nameurl.

Next up is the comment form, which frankly will be the hardest part of the template system - but also the last.

Oh - and if you look at template.cfc - yes - I have duplicated code in there. I plan a total rewrite of the CFC. I'm happy with the _outside_ user of the code, just not the code inside.

Lastly - has anyone tested BlogCFC5 under MX/MX7 yet? Specifically in regard to this blog entry. Please and thank you.

The last release of BlogCFC added ColdFish support for code coloring. Unfortunately I didn't think to check if it was CF6/7 compatible. Jason has helpfully provided a new version that should work in MX and higher. I've checked in the new code to SVN.

Would those of you on 6/7 please get latest from SVN and tell me if code coloring is working?

I'm working on v6 again. The "project from hell" is over and I'm at a job now that doesn't crush my soul, so I've been a lot more excited about working on BlogCFC again. I hope folks have not given up. The most recent changes to V6 SVN include:

• The settings file now includes a reloadkey value. This is the key you use in the URL to reload the application. I'm still reloading the app on every hit for now, but this was an old request to help improve security.
• The application name now uses a hash of the current template path. You do not have to edit the application if you have multiple blogs on your box now. You should edit the settings file to set a proper blogname if you share a db, but you don't have to edit Application.cfc anymore.
• The red template was updated to demonstrate a 'home' link using $$HOMEURL.
• Comment support has begun. A new CFC just for comments was added. Comment display isn't done yet. Currently I just dump the query on the page.

Any questions, please let me know. After I get comment display working I'll do another checkin. Then I'll work on the comment form itself. That will be "the end" of templating pretty much and I'll start working back on core functionality again.