Another minor bug fix release. This is an extension only update that fixes an issue were SQL statements were not shown for queries which had text queryparam types (i.e. cf_sql_varchar) with numeric values. This fix was provided by Shane Bradley.
This bug fix release includes the following:
Thanks go to Shane "shag" Bradley for helping me debug and fix the query parameter issues.
This version is an update to both the Firefox extension and the coldfire.cfm ColdFusion debugging template. Below are the highlights for this release:
If you have recently updated FF to version 3.0.1 you will need to update ColdFire. This version is just a change to the ColdFire install manifest to indicate that ColdFire is compatible with Firebug versions 3.0.*.
The Firebug team has released Firebug 1.2.0b4 so I'm finally able to release ColdFire 1.2.
Note that the download now contains xpi packages for both ColdFire 1.1 and 1.2 so please be sure you install the correct version for your Firefox/Firebug installation. Basically if you are using Firebug 1.1 install the ColdFire 1.1 xpi. If you are running Firebug 1.2 install the ColdFire 1.2 xpi. The install documentation has more info if you need it.
Also, this is an extension update only. The coldfire debugging template has not changed with this release, so there is no need to update coldfire.cfm on your servers.
For more details on this release check out my blog: http://www.mischefamily.com/nathan/index.cfm/2008/6/29/ColdFire-12-Released.
I've had a few reports that ColdFire 1.1 does not work with Firebug 1.2, the recommended Firebug version for Firefox 3. I just wanted to let people know that I'm aware of the issue and actually have a working version of ColdFire 1.2 ready to go, but...
There is a bug in the current Firebug 1.2 beta (beta 3), which causes both the Net and ColdFire panels to break when you install ColdFire. This issue is fixed in later revisions of Firebug, so as soon as the next Firebug 1.2 beta is released I'll be releasing ColdFire 1.2. (Hopefully in the next couple of days.) If you really need ColdFire right now you have two one options: use Firebug 1.1, which AFAIK works in Firefox 3, or download and build the latest 1.2 branches of both Firebug (http://fbug.googlecode.com/svn/branches/firebug1.2) and ColdFire (http://svn.riaforge.org/coldfire/branches/1.2/).
Update: According to John J Barton, the current Firebug developer, Firebug 1.1 does not work with Firefox 3.
This extension only update was really focused on driving some of the complexity out of the extension code. To that end I:
New features in this release include:
There are some big changes under the hood in this release so if you run into any problems be sure to report them. Note that this release is an extension only update so if you are currently running 1.1.51.51 there is no need to update your coldfire.cfm.
Thanks and enjoy!
Updates in this release:
This has been a long time coming. Without going into all the details, I was having issues with the coldfire-service XPCOM object which handles setting request headers for ColdFire. This piece of the ColdFire code was very much a monkey see/monkey do effort based on the Modify Headers extension. Luckily Gareth Hunt, the author of the Modify Headers figured things out and I was able to do something similar in ColdFire.
If you want to use Firefox 3 you will have to use ColdFire with the new Firebug 1.1 beta, which you can get at http://www.getfirebug.com. The Firebug 1.1 beta is actually the recommend and supported version of Firebug, so I will no longer be testing with, or supporting, ColdFire with Firebug 1.0. (The current version of ColdFire does work with Firebug 1.0, but that will probably not be the case for much longer.) Note that ColdFire 1.1 and Firebug 1.1 both work with Firefox 2 so you don't have to use Firefox 3.
The official version number for this release is 1.1 51.51. This breaks down to major_version.minor_version.coldfusion_revision.firefox_revision. I did this in the hopes of allowing users to more easily update their ColdFire installations. The coldfire.cfm debug template now only checks the coldfusion_revision part of the version number for compatibility. This means as the coldfire.cfm stabilizes you will be able to continue updating the extension with out updating the debugging template. (For example, if we were to release 1.1.51.58 and 1.1.51.67, these would both be compatible with the current coldfire.cfm.) Also, going forward, if you are using an incompatible version of the extension you should get an error message in the general tab.
I've added Cached, Template and Timestamp columns to the DB Queries tab. The layout of this tab had to be changed a bit to fit all of the data, but I think most users will like it. Also the formatting of the query is now maintianed, which should help if you are debugging complex queries.
There were some updates to the build file to support generating the version number based on SVN revision numbers, but I'll put together a separate on those changes. For now just know that if you want to build the distribution you can just run the default ANT target in either the /trunk of /tags/1.1.51.51 branches and you should be good to go.
A few other minor updates were made to the core processing logic, but most of that was "under the hood." The only some people may notice is that I changed the variables request header name form "ColdFire-Variables" to "x-coldfire-variables."
