I just posted a new version of ColdFire, 1.4.207.218, which should work with Firefox 3.5 and Firebug 1.4. Since Firefox 3.5 is only a release candidate and Firebug 1.4 is still in beta, I think it is safe to consider this release a beta as well. That said, all my tests passed so please give this new release a try and let me know how you make out. (Comments are still disabled here, so please report any issues to the bug tracker or via the contact project page.)

Note that the download .zip now contains two installations, one for ColdFire 1.3 and one for ColdFire 1.4. ColdFire 1.4 only works with Firefox 3.0 - 3.5 and Firebug 1.4.

Today I started to look at updating ColdFire to work with Firefox 3.5/Firebug 1.4. Unfortunately it is not working out of the box, so I'll have to take some more time to try to figure out what it is going on.

In the meantime I'm releasing this extension only update that fixes a bug with query parameter formatting. This was a bug I introduced a couple of releases ago which caused cf_sql_bit types not to be converted to 0/1 and cf_sql_varchar types not to be quoted. This should be working again as expected.

Comments are still disabled, but if you have issues please use the bug tracker or contact project pages.

I just posted a new version of ColdFire which has support for Railo. This is a very early beta release so there are no installation instructions yet.

If you want to give ColdFire a try on Railo just copy the debugging-coldfire.cfm template found in the railo folder of the new installation zip to your WEB-INF/railo/context/templates/debugging folder and then select it as your debugging template in the Railo Admin. You can then follow the install.txt instructions to install the Firefox extension.

A few things are not supported with the Railo debugging template:

• Exceptions Tab
• Parese Query Params Option
• Enhance Trace Option
• Enable CFAJAX Debugging Option

If you find any problems please let me know.

I've just posted a new extension only release which fixes a stored procedure related issue with the DB Queries tab. From the release notes:

• fixed stored procedure domplate to support procedures with no parameters or resultsets.

A new extension only update has just been released. Here is what's new/fixed:

• fixed component domplate to support components with no methods.
• added option to show execution time totals at top of tab.
• fixed issue with preference persistence.

Comments have been disabled for this blog. I'll still use this blog to announce releases, but if you have issues please use the project's bug tracker. Thanks.

The latest version of ColdFire has one new feature and a few bug fixes. From the release notes:

• added Copy SQL context menu option.
• fixed issue with reported start and end times with enhanced trace tag.
• changed CFAJAX JS injection so that more requests can be debugged.
• fixed issue with build that resulted in corrupted image files.

I just posted the first non-beta ColdFire 1.3 release. From the release notes:

• removed dependency on custom cfajax library.
• added exceptions tab.
• added ColdFireAdvice for ColdSpring AOP.

With this release you can now debug CFAJAX requests by selecting the "Enable CFAJAX Debugging" option and, unlike the previous 1.3 beta release, you do not need a custom cfajax.js file to use this feature. Out of the box, this option will only work for CFAJAX controls bound to CFM templates. However, this release also includes a new ColdSpring AOP after returning advice, ColdFireAdvice.cfc, which can be used in conjunction with ColdSpring remote proxies to debug CFAJAX requests bound to CFCs. The ColdFireAdvice can also be used to debug Flex Remoting requests. Finally, this release adds the Exceptions tab, which should display the same exception information you are used to seeing using the classic.cfm debugging template.

A new version of ColdFire 1.2 has been rolled into the download zip. This version incorporates fixes to the trace.cfm custom tag that happened in the 1.3 branch. If you were using the enhanced tracing feature in 1.2.117.117 or 1.2.117.126 you can simply update your trace.cfm with the version included in this download and you should be good to go.

The problem with earlier version of the trace.cfm tag was that it didn't always fallback to the Adobe version of trace.cfm when it should, particularly if you didn't close your cftrace tag. (i.e. you wrote <cftrace text="hi"> instead of <cftrace text="hi"/>.) This was fixed in the 1.3 branch so I decided to go ahead and put it in the 1.2 release as well.

A new beta is available for download. From the release notes:

• updated coldfire.cfm to address variable dump issue due to variable scope pollution.
• fixed issues with execution times (Thanks Ray Camden).
• added cfajax.js to support new "Force Debugging" option for CF AJAX requests.
• enhanced white space suppression (Thanks Ray Camden and John Hartmann).
• updated variable name validation in Variables tab to allow dot notation.

The biggest feature in this release is the new "Force Debugging" option. This allows you to debug CF 8 AJAX requests that are bound to URLs. Unfortunately, due to issues with adding headers to remote component invocations this feature does not work with AJAX calls bound to CFCs. Be sure to check out the install.txt file for more info on how to set up and use this feature.

I just posted a new ColdFire release. This version is beta as it is built on Firebug 1.3, which still in beta. That said, I think this is the most solid release of ColdFire yet. So what's new?

• fixed issues with trace.cfm custom tag.
• new UI for selecting files from request queue.
• added suppress query white space option.
• toggling parse query params option now updates UI immediately.
• updated query tab to use Firebug domplate.

To use this release you need to using Firebug 1.3, available on the firebug site.

Also, because this is beta the download contains both ColdFire 1.2.117.126 and ColdFire 1.3.142.145. Be sure to install the correct version for your version of Firebug. (But again, I highly encourage you to try Firebug 1.3.)