Zend Framework 1.6 RC2 and FirePHP
After I had upgraded from Firebug 1.2.0b7 to 1.2.0b15, my web apps were no longer throwing any kind of logs into the Firebug console. I'm using the Zend_Log_Writer_Firebug class for that.
Luckily, just earlier today I noticed a new release of Firebug 1.2.0. And with that, FirePHP 0.1.1.2. But now there was a new problem:
["There was a problem writing your data from the Wildfire Plugin http://meta.firephp.org/Wildfire/Structure/FirePHP/FirebugConsole/0.1", Array(4)]
That, of course, wasn't helping any. So I checked the release notes and noticed issue #14, which is a copy of ZF-4020. Since I'm stuck with ZF1.6 RC2 and would rather not pull from the trunk, I figured I'd test to see if I could fix it myself. Followed the code through to Zend/Wildfire/Protocol/JsonStream.php line 203 and replaced $part); with '|' . $part . '|'); Works great!
And I just noticed that ZF1.6RC3 was released. And it includes the fix, of course. Quite a chain reaction. A bug in Firebug's tabWatcher.js gets fixed, causing a refresh issue with FirePHP, which fixes the issue and also adds a workaround for a problem with whitespace disappearing, which requires a new ZF release candidate. All is well at last.
Posted: August 25th, 2008 under Development, PHP, Zend Framework.
Tags: firebug, firephp, PHP, wildfire, zend
Comments
Comment from marcus
Time August 28, 2008 at 1:23 am
Thanks for stopping by! And indeed, I didn't mean to imply that this issue was the sole reason for RC3, although it does sound that way, now that I'm reading it again.
And thank you for FirePHP/Wildfire, it's become an important part of my tool box.
Comment from Christoph Dorn
Time August 25, 2008 at 11:49 pm
Great summary for the chain of events!
Unfortunately the FirePHP fix was delayed a bit because I was unavailable for a while.
I am working with the Firebug team on a closer integration and a co-testing setup for Firebug 1.3 that will allow me to verify the integration between FirePHP and Firebug before new Firebug versions get released. There is also a unit-testing framework planned for 1.3 which should help a lot in preventing issues like this.
Also wanted to note that ZF1.6RC3 was not released just because of FirePHP/Wildfire. There were a dozen other critical fixes that had to make it into 1.6 but it all was great timing and the FirePHP integration did factor into the decision.