Fusebox 101: Reload fusebox URL
This is just a quick one but to reload fusebox via the URL add this to the URL:
What this is doing is requesting fusebox to:
This is just a quick one but to reload fusebox via the URL add this to the URL:
What this is doing is requesting fusebox to:
I've made another change to the tql.cfm and parameter.cfm lexicon for Transfer and Fusebox.
This now takes into account the dataType argument and it allows for the 'list' argument to be set - which is helpful if you're doing a select IN statement.
I've changed in tql.cfm line 32 to:
Love coldfusion, love the coast then we have the ideal job for you in Brighton, UK.
You will report to me and work on a wide range of CF based web sites
What we're looking for is an enthusiastic, experienced, self motivated web developer. With an minimum of 2 years experience ideally with a background of working with coldfusion frameworks. The role will entail development as well as specifying technical specifications, testing and deployment and some documentation.
The basic skills we are looking for are
Any experience with server deployment & configuration, Subversion and ANT would be a big plus.
What we look for in a person:
This position is based in Brighton but once you've settled in we are flexible.
That's all there is to it - please contact me succorJobBlogPost [at] talkwebsolutions [dot] co.uk
All AGENCIES will be cursed! (we do love you really).
As anyone following me on twitter will know I've been playing with VMware a lot recently. One of the things that it lets you do it map to a local drive on your computer. This is great as it stops your having to copy code from one place to another.
I've just been chatting with someone about the XFA in verb for fusebox and I thought I would post my thoughts.
XFA stands for eXit FuseAction - this is where you store variables to be used in your web pages. The question here is, why use it?
Well imagine this, you have a login form that is used on your website. When a user goes to certain areas, you check to see if the user is logged in. If they are, then they will continue as normal, on the other hand they will need to login.
Being a great coder you don't want to have lots of forms all over the place, so you include one login form. This form then performs different actions depending on the what you need it to do.
I was asked today what the different modes in fusebox do. For those that don't know fusebox allows you to have 3 different modes (these can be changed in the fusebox.xml.cfm file).
Here is an overview of the permissions attribute and how you can use it within fusebox.
From: http://halhelms.com/index.cfm?fuseaction=newsletters.show&issue=052203_rolesBasedSecurity
<circuit access="public" permission="useQuizBuilder">Fusebox itself does not apply any security check, but does make the values set in these attributes available to the programmer. It then becomes a simple matter of a few lines of code to write any challenge code you wish. For example, we might write a plugin to ensure that to use any fuseaction in the circuit, the user must have the useQuizBuilder permission. If the user wants to delete a quiz, s/he can now be challenged for the deleteQuiz key. The rules for permission binding can be stored and gotten from database table(s), XML files, .ini files, through the use of web services, etc.
<fuseaction name="deleteQuiz" permission="deleteQuiz">
...
</fuseaction>
One needs to create a plug-in to check if the permission set (or permissions made available) are matched by the current user – thus (plugins/listCheckSecurity.cfm):
This Thursday (2nd August 2007) Sean Corfield will be giving the world the first preview of fusebox 5.5. To find out more, and how you can attend visit cfFrameworks.com
Transfer is getting better all the time, with some recent speed improvements it keeps growing. If you've not used Transfer in fusebox yet check out this post.
Since March Transfer has supported TQL, which is transfers own scripting language:
There is also a scripting language that allows you to perform database queries based on the information and naming scheme that you set up in your transfer configuration file called Transfer Query Language (TQL). TQL is very similar to SQL, however since Transfer already knows about the relationships in your system, you don't have to write as much code to perform complicated queries against your database.
This is a fantastic addition as it allows you to quickly manipulate your data. One thing that I thought could make easy to use via fusebox was to create a lexicon, which I have done here:
I've been spending the afternoon finding out why my server has been running really slow and stopping altogether. After searching the logs i didn't get much inforamtion, so i decided to do some thread dumps and see what was happening. To do this i started CF via DOS running cfstart.bat i.e.
Looking through this I noticed that coldspring was being invoked over and over again. I thought for a while and then realised my mistake: