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:

• Did away with the XPCOM object.
• Got rid of custom network monitoring code. ColdFire now leverages Firebug's network monitor, which is much more robust.
• Consolidated helper objects and functions into one lib.js file.
• Renamed source files to more closely match Firebug.

New features in this release include:

• ColdFire now has a request queue. More on this later, but for now > > check this out.
• Variables can now be defined per Firefox tab.

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!

This is major update to support variables. I'm going to blog more on this at my main blog, www.coldfusionjedi.com.

This is a minor but important update. ColdFire will now slightly modify your browser user agent when installed. This user agent change will be checked by coldfire.cfm, and if it doesn't see it, it will not return debug information. This means you can enable ColdFire on your server and other developers who dare not to use ColdFire won't have the performance penalty of having the debug information added to the header.

I'm blogging this over at my main blog, so check the details there:

http://www.coldfusionjedi.com

The last release as missing an earlier fix I had done to getQueries. It is rolled into SVN and the zip now. Sorry!

Version 0.0.4 adds support for CFTIMER. It also fixes a few bugs.

This is it! This release should fix the "big header" issue and actually display in the browser. I forgot to update the readme.txt file, so if you download it 2 seconds after reading this blog post then please ignore it.

I just updated coldfire.cfm in SVN only. This will split up headers into arrays. If you are experiencing the 'pages wont change' bug, this should fix it, but nothing will show in ColdFire. I need folks to just confirm the bug fix. Once it has been confirmed, I'll have Adam update the browser side.

Today we have released the 0.0.2 release. Please read these notes carefully.

First and foremost - this release has no new features. Our primary concern is to fix the problems people encountered and we are not going to add anything until we get past then. So let's talk about the main problem - header size.

ColdFire 0.0.2 now uses JSON to encode the data instead of XML. We now use one header per datatype (one for general, one for templates, etc.) CFC arguments are now trimmed to 250 characters. This was most helpful in Model-Glue where large HTML strings were passed back and forth. Templates and CFCs now show aggregate information. That means if the same template is run twice, you only see one line. Ditto for a cfc/method/arg call. All in all there is a lot less data being sent back, and it isn't being stuffed into one header.

But this will NOT solve the problem for everyone. This is an interim solution. The next build will take the headers and split them up even more. I just want folks to know that if they have a lot of debug information (typically true in Model-Glue or other framework apps), that this will still not help them. But if you were on the edge before - ColdFire should now work for you.

Secondly - the bug with cflocation is now fixed.

Lastly - I've added all the files to source control. Right now the plugin is checked in as a XPI, and not split up. That will happen later.

I know folks have found other problems as well, but I ask for your patience so we can get past the "big header" issue first.

Enjoy.