Major Blog Update

This post is more than 2 years old.

Welcome to Blog 2.0. Lots and lots of changes, so let's get to it.

Ability to support multiple blogs. This is done via a simple ini script. Ben Forta added this to his version of the blog and I've rolled it into mine. A future version will also allow for defining the blog via a struct passed to init().

assignCategories() added. Allows for adidng N categories at once.

removeCategories() added. Guess what this does.

New admin! Many people asked about my blog editor. I didn't normally include it because my blog editor was included as part of my general web site editor. I didn't like not including the editor, and I didn't like my editor as well, so I rebuilt the editor and it's now part of the blog client. You can now add/edit your blog straight from the blog itself. This is my favorite new feature.

DB schema upgraded a bit, again thanks to Forta.

Note: You may notice a few extra UDFs in udf.cfm. These are functions I'm adding to make it easier to edit the Current Media portion of my blog. I ran into some bugs with that, so I decided to just wait on it.

Enjoy. I'm very, very happy with this new version and I hope you like it as well.

Raymond Camden's Picture

About Raymond Camden

Raymond is a senior developer evangelist for Adobe. He focuses on document services, JavaScript, and enterprise cat demos. If you like this article, please consider visiting my Amazon Wishlist or donating via PayPal to show your support. You can even buy me a coffee!

Lafayette, LA https://www.raymondcamden.com

Archived Comments

Comment 1 by William Dent posted on 7/6/2003 at 5:46 PM

Thanks again for the update! Haven't used your blog publicaly anywhere, but plan to one day. I installed this and got a few errors you might want to check. It seems you have one hardcoded instance of dsn in the application.cfm file. However after I updated that I still get error messages that say "name can't be empty" on line 370 blog.cfc. Strange. Anyways I thought you might want to know about the Application.cfm file. Cheers!

Comment 2 by Jacob Reider posted on 7/7/2003 at 7:12 AM

Hmmm
I also got an error on line 370 of the cfc initially .. but it's not from hardcoding (#dsn# on line 370) .. its a problem with the .ini settings .. users should be sure to leave default-camden and [camden] ... or change them to wahtever they would like.. but they must tbe the same.

Comment 3 by Raymond Camden posted on 7/7/2003 at 3:13 PM

1) Hard coded dsn in application.cfm: This is used by the authenticate udf, which is not directly part of the blog. Maybe it should be actually.

2) line 370? My line 370 doesn't mention anything about name. You sure you have all the new files? Ah, just read Jacob's post. Yes, right now we kind of assume that your ini file is set up 100% right. I'm going to add a 'verify' style function later that might check for stuff like that.

Comment 4 by Jacob Reider posted on 7/7/2003 at 4:14 PM

Yeh ... I am now having a problem with the <cfquery name="q" datasource="#application.dsn#"> on line 113 of the application udf (called from line 19 of application.cfm) since the application.dsn gets set above as "camdenblog" ... so .. I would agree that this needs to be dynamically set from the .ini file ..

Comment 5 by William Steiner posted on 7/7/2003 at 4:17 PM

Looking at the new version am I correct that multiple blogs would still need their own dsns?

I can think of some cases where allowing multiple blogs to share the same dsn would be beneficial. Some examples would be a personal blog and a programming blog. Or a user group allowing it's "board members" to have blogs on the user group's site.

Does anyone else see this as a plus?

Comment 6 by Jacob Reider posted on 7/7/2003 at 11:36 PM

Yeh ... I am now having a problem with the <cfquery name="q" datasource="#application.dsn#"> on line 113 of the application udf (called from line 19 of application.cfm) since the application.dsn gets set above as "camdenblog" ... so .. I would agree that this needs to be dynamically set from the .ini file ..

Comment 7 by Raymond Camden posted on 7/7/2003 at 11:38 PM

I'm a bit confused... I know it's hard coded, but can't you just edit it? Or are you saying it's a problem in that you have to modify application.cfm? I guess I'm saying, I know I need to look into it, but you _do_ have stuff running, right?

Comment 8 by Nathan Dintenfass posted on 7/8/2003 at 2:19 AM

Any plans to create SourceForge project and start managing this from there? Might be nice to have CVS, release management, etc.

Comment 9 by William Dent posted on 7/8/2003 at 4:17 PM

OK. My error in the ini file. You didn't see the [camden] above the configuration inforamation. Sometimes the obvious is often overlooked! Thanks again.

Comment 10 by Peter Tilbrook posted on 7/9/2003 at 6:19 AM

The script for SQL Server appears to be corrupted.

Comment 11 by Raymond Camden posted on 7/9/2003 at 1:23 PM

Nathan - no, no plans. I want to maintain control over the codebase, so I don't see how a sourceforge project would help. Do you think it would?

Comment 12 by Raymond Camden posted on 7/9/2003 at 1:24 PM

Peter, what do you mean? It looks ok to me. If you mean the wierd spacing, I think that's something you can ignore.

Comment 13 by Raymond Camden posted on 7/9/2003 at 1:30 PM

Guys, I posted another blog update. Please check the new entry.