BlogCFC will never have an installer. Ever. Until today...

Posted At : January 19, 2010 9:01 AM | Posted By : Raymond Camden
Related Categories: BlogCFC

Ok, so the title is a bit misleading. I'm not releasing an installer today in any formal sense, but I do have the bits ready for testing. The installer handles prompting for a DSN, running import scripts (MySQL and SQL Server only, and be warned - this drops tables), and asking for basic settings to help get you started. It also auto-kills itself so it can't be run again. Some screen shots (sorry for how small they are):

Before testing, add the following line (to a virgin BlogCFC install) to your blog.ini.cfm file:

installed=no

Enjoy!

Comments (14) | Print | Send | Download | del.icio.us | Digg It! | Linking Blogs | 1331 Views
Comments
[Add Comment]
Gary Funk's Gravatar I think I found a bug. blogname is undifined in session.
# Posted By Gary Funk | 1/19/10 1:02 PM
Raymond Camden's Gravatar Ah shoot - I forgot to mention another mod. Modify Application.cfm to ....

   <!--- Do we need to run the installer? --->
   <cfif not application.blog.getProperty("installed") is 1>
      <cflocation url="./installer/index.cfm?blog=#urlEncodedFormat(blogname)#" addToken="false">
   </cfif>

Add this right after this line:

   <!--- load and init blog --->
   <cfset application.blog = createObject("component","org.camden.blog.blog").init(blogname)>
# Posted By Raymond Camden | 1/19/10 4:27 PM
Gary Funk's Gravatar How about:

installed is not a valid property.

The error occurred in D:\www\jacfb\org\camden\blog\utils.cfc: line 62
Called from D:\www\jacfb\org\camden\blog\blog.cfc: line 1867
Called from D:\www\jacfb\Application.cfm: line 42

60 :             hint="Throws errors.">
61 :       <cfargument name="message" type="string" required="false" default="">
62 :       <cfthrow type="blog.cfc" message="#arguments.message#">
63 :       
64 :    </cffunction>
# Posted By Gary Funk | 1/19/10 4:54 PM
Gary Funk's Gravatar I added:
<cfset instance.installed = variables.utils.configParam(variables.cfgFile, arguments.name, "installed")>

at the end of the init in blog.cfc
# Posted By Gary Funk | 1/19/10 5:03 PM
jester's Gravatar worst installation instructions/documentation i have ever experienced. sql script fails, spent more time trying to get it working than than 4 other pieces of software combined, and it still fails...
# Posted By jester | 2/5/10 7:36 AM
Raymond Camden's Gravatar Worst ever? Do I win a prize? Seriously though - I want this to work well. I'm sorry you spent so much time on it with it failing. Why didn't you report back earlier? Are you still willing to work with me to get through the bugs you had?
# Posted By Raymond Camden | 2/5/10 8:01 AM
Skip's Gravatar @Jester - I had no issues getting it installed. Worked like a charm when I followed the instructions.

Operator error maybe?
# Posted By Skip | 2/5/10 8:14 AM
Joe Rinehart's Gravatar > worst installation instructions/documentation i have ever experienced

Teaches you to try to be helpful, Ray. Maybe you should just release half-built frameworks with no documentation, then, if they get popular, pawn off their maintenance on other...I mean, it works for me :).
# Posted By Joe Rinehart | 2/5/10 8:26 AM
jester's Gravatar >>Operator error maybe?
never heard that one before....

running the script right out of the box
Server: Msg 170, Level 15, State 1, Line 8
Line 8: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 4
Line 4: Incorrect syntax near '('.

yup, definitely "operator error"
>>Teaches you to try to be helpful, Ray. Maybe you should just release half-built frameworks with no documen...
if you are going to be facetious at least put some effort in to it

@ray, thank you for the offer, i apologize if my previous post came across offensive, but i worked on the install for over an hour and finally gave up, i tried two other potential blogging options and had them both up and running in under 10 minutes, so yea, an hour on just one was frustrating
# Posted By jester | 2/5/10 9:31 AM
Raymond Camden's Gravatar Your not even saying _what_ script though? You ran the SQL script by itself? If so - which one? MySQL? SQL Server? Also, why did you run the script yourself? This installer runs it for you. Also, didn't this blog post make it -very- clear that the installer was a work in progress and that I needed help with testing?
# Posted By Raymond Camden | 2/5/10 9:33 AM
jester's Gravatar started over from scratch, fresh extraction of all files
ran installer
installer/step3_runscripts.cfm

Line 6: Incorrect syntax near 'max'.

in reviewing this it seems the script is MSSQL 2005+, my local test environment is 2003, therefore, the base script is incompatible with my test environment, however the script indicates that it is mssql compliant, sqlserver.sql, perhaps including a 2005+ and an "other" script would be beneficial for those testing on older systems.

manually running the script in 2005 results in no errors.
# Posted By jester | 2/8/10 5:58 AM
Raymond Camden's Gravatar @Jester: Ah, perfect. Now we're getting somewhere. I'm not sure why you didn't provide this level of detail up front. Much more constructive. :)

Edit mssql/script.txt and replace all nvarchar(max) with ntext.

Does that help? I don't have SQL Server 2003 to test on so I need your help here.
# Posted By Raymond Camden | 2/8/10 7:56 AM
jester's Gravatar changing the nvarchar(max) to ntext allowed the tables to be created without error, however it still errors on the indexing code

eg
CREATE NONCLUSTERED INDEX [tblusers_blogUsers_blog] ON [dbo].[tblusers]
([blog])
WITH (
PAD_INDEX = OFF,
DROP_EXISTING = OFF,
STATISTICS_NORECOMPUTE = OFF,
SORT_IN_TEMPDB = OFF,
ONLINE = OFF,
ALLOW_ROW_LOCKS = ON,
ALLOW_PAGE_LOCKS = ON)
ON [PRIMARY]
GO

gives error
Line 3: Incorrect syntax near '('.

the samples i have been be to review for this code block do not have a ( after the WITH keyword
http://msdn.microsoft.com/en-us/library/aa258260%28SQL.80%29.aspx

again this seems to be an MSSQL 2003 issue as 2005 works
# Posted By jester | 2/8/10 9:53 AM
Raymond Camden's Gravatar Does removing the ( and ) in the WITH clause make it work?
# Posted By Raymond Camden | 2/8/10 9:55 AM
[Add Comment]
BlogCFC was created by Raymond Camden. This blog is running version 5.6.001.