Now running BlogCFC without get-/setProfileString
I posted a ticket with HostingAtoZ, where I have my sites hosted. The reply was that setProfileString is a restricted function and that I must have changed my code. I wrote them back telling that I've been running BlogCFC for a long time, and that they enabled setProfileString for my just for this purpose when I first installed BlogCFC. The answer was that they were wrong enabling it the first time and could not help.
Ok - I accept that it is a restricted tag, and I would have accepted getting a warning saying something like "we've discovered that by error...yadada.....could you make the necessary changes within a week." But that they suddenly just restrict it causing my blog to just go down like that - that is harder to accept.
For some days I've been considering moving over to another host, but dreaded the thought.
So instead I decided to see if I could get BlogCFC to work without using setProfileString and getProfileString. It took some trial and error, since I cant access robust error messages either, but here is what I came up with:
In the blog.cfc file in the org/camden/blog folder I just comented out the part with setProfileString so that line 2020 and 2021 was replaced with this:
<cfset setProfileString(variables.cfgFile, instance.name, arguments.property, arguments.value)>
<cfset instance[arguments.property] = arguments.value>
--->
The slightly (but not much) trickier part is in the utils.cfc file in the same folder. But what I did was to move the configuration info from the blog.ini.cfm file into the utils.cfc file. Now this is not good programing. I could have made a xml file or some other configuration file, and I might still do, but this was a shoot at getting the blog up and running as fast as possible.
Here's part of the code (starting on line 119 in the configParam() method:
<cfset var result = "">
<cfswitch expression="#key#">
<cfcase value="dsn">
<cfset result="my_dsn">
</cfcase>
<cfcase value="owneremail">
<cfset result="trond@ulseth.no">
</cfcase>
<cfcase value="blogURL">
<cfset result="http://trond.ulseth.no/index.cfm">
</cfcase>
<!--- continue for each or the config params in the blog.ini.cfm file --->
</cfswitch>
<cfreturn result>
As I said - not the best solution, but it's working (apparently).
i still say for the $, they're a great hosting option. maybe not for a commercial site... but just to have a playground or a place to host your personal site (with CFMX 7 Enterprise and minimal restrictions on tag usage), you can't go wrong.
For the buck (about $15) I can host up to 50 sites with HostingAtoZ, and with the Helm controll panel and stuff, for that price I'll even accept not being able to use get/setprofilestring (personaly I've never used those functions in my own coding). I was a pretty anoyed when my blog went down though. They could have handeled that a bit smoother.
So enough about that as well. The next posts will be on newBee, FarCry or other more interesting topics.
PS. Sorry for the late comment, just found your blog =)
[A] the product is released - it might be the same as the public beta or it might not. Thats why you have a beta - to fully test every aspect under real world conditions - some features of the beta product might not be in the final release.
[B] a reasonable time has elapsed to tell if there are any 'gotchas' for shared hosters. We know what Adobe SAY is the recommended hardware to go with it, but what works out in practice? Are we going to have to upgrade our hardware as well to keep performance high enough?
[C] pricing is announced. At this stage we dont know if it's going to make business sense or not because we can't do any of the arithmetic yet.
[D] we can make an assessment about the customer demand. Will our customers be clamouring for it or not? How many people are clamouring for WIndows Vista? Not that many apparently. Will CF8 be like that or not? Dont forget we have a pretty substantial investment in CF7 Enterprise already. If we're going to invest in CF8 enterprise, we want to know that there was a good business case for it.
We'll do the business case when the product's released. I would almost guarantee that all the CF hosting companies are evaluating CF8 now, but few will make any announcements until the product is released.
Those are some really excellent points you make, I just wish I could fast-forward a bit =)
In particular I'm looking forward to finding a hosting plan w/ CF8 because it allows ColdFusion mappings and custom tag paths to be set per Application, which will save me from having to send a ticket every time I need a change for any of my shared hosting sites. =)
The first being The method 'init' could not be found in component C:\Inetpub\vhosts\normsblog.net\httpdocs\org\camden\blog\ping.cfc.
Check to ensure that the method is defined, and that it is spelled correctly.
The error occurred in C:\Inetpub\vhosts\normsblog.net\httpdocs\org\camden\blog\blog.cfc: line 104
102 : <!--- <cfset variables.ping = createObject("component", "ping")> --->
103 : <!--- <cfset variables.ping = cfinvoke("component","ping")> --->
104 : <cfinvoke component="ping" method="init" returnvariable="variables.ping"> </cfinvoke>
Any help would be appreciated.....
Man, I think I'll write my own CF BLOG... It weould be less coding... LOL
I retract my diss of Daily Razor. and I'll keep the BLOGCFC :)