BlogCFC requires ColdFusion 7 or compatible CFML engine and one of the following databases: MYSQL 4+, Oracle, MS Access, SQL Server 2008.
When you unzip the installation package, you will have three main directories, client, org, and install. The client folder represents the main blog application. If your web site will only contain the blog, then obviously this folder will be your web root; you may rename this folder (be sure to update this change in Administrator Settings). The org folder should be placed under web root. This folder contains the CFCs used by the blog application. The install folder contains miscellaneous files to help you install the blog. This folder should be removed from your web root.
You now have 2 choices: You can either run the new, web based installer, or you can manually configure BlogCFC. If you wish to run the web based installer, simply point your web browser to where you installed BlogCFC. BlogCFC will notice it hasn't been set up and push you to the installer. If you decided to follow the manual process, continue reading the directions below. Note that manually setting up BlogCFC will require you to add the "marker" that lets the application know it has been configured. Do not skip this step. Repeat - do not skip this step.
Next, decide which database you want to use. In the install folder you will find a mysql.sql file, a sqlserver.sql file, two Oracle files, and a MS Access database. These are the four database types supported by BlogCFC. Pick the one you plan on using it and set up a database manually, using your favorite db admin program. Set up a datasource pointing to your database. Open the blog.ini.cfm file from /org/camden/blog folder. Find the default section, dsn key, and edit the value. Set the dsn value to what you set in the ColdFusion Administrator. Set blogDBType to either MSSQL (for SQL Server), MYSQL (for MySQL), ORACLE (for Oracle), or MSACCESS (for Access). Access users should not use the "Access with Unicode" driver type. They should use the "Access" driver type.
You also need to ensure blogdbtype matches your database. This is described in the Blog Ini File section.
Note: The blog.ini.cfm file is described in more detail later in this document.
READ THIS: The blog.ini.cfm file is cached. This means if you visit the blog and make a change to the ini file, it will NOT be reflected. To refresh the blog's cache, visit your blog with ?reinit=1 at the end of the URL or use the Administrator.
You have two choices for placement of the org folder. If there will only be one blog on the box, you can simply place the org folder inside the client folder. If you will have multiple blogs, you should place the org folder in any location you want, but then set up a mapping called "org" that points to the folder you placed the org files. To repeat - no mapping is necessary if you place the org folder under the client folder.
The last thing you should be when performing a manual set up is to flag BlogCFC that it has been installed.
The last key in the blog.ini.cfm file,
installed, should be set to true. If you do not do this, BlogCFC will think it has to run it's own installer. I recommend deleting the installer folder as well.
At this point, your blog should actually be working, but obviously you will have no entries. In order to add entries, you should go to the BlogCFC administrator. If your blog URL is: http://localhost/blog, then the administrator would be http://localhost/blog/admin. You will be prompted to logon. Use admin for the username and admin for the password. You should change this password immediately or sometime soon. There is no interface to do this so you will have to manually edit the password in the database.
Unix users should make the /blog/images/captcha folder writeable by ColdFusion.