Add option to use ChromePHP instead of FirePHP in DebugKit

Created by Chris Cinelli, 1st Aug 2011. (originally Lighthouse ticket #62):

---

FirePHP extension for Firebug seems not to work anymore in Firebug 1.8. The author of FirePHP seems to go for the not-free route with the DeveloperCompanion (new FirePHP client side).
Someone implemented an extension for Google Chrome that is similar to FirePHP but the protocol is not 100% compatible. It would be good to just use chrome as developer environment.
Please add support for it.

Extra: It would be nice to to be able to switch between ChromePHP and FirePHP. Even better CakePHP could autoselect if using one or the other based on user agent value.

For more info on ChromePHP see https://chrome.google.com/webstore/detail/noaneddfkdjfnfdakjjmocngnfkfehhd?hl=en-US

21st Aug 2011, Mark Story said:

---

I'll have to take a look at how ChromePHP works. Kind of sucks that chrome extensions can't get at the response headers, and the extension author had to use cookies instead.

19th Jan 2012, James Coletti said:

---

As a temporary workaround, there's a new Chrome extension called FeverPHP which can parse FirePHP data from the response headers, although it only displays data in a separate tab, not the debug console. DebugKit only seems to output FirePHP data if the User-Agent shows Firefox and FirePHP, so grab the dev or canary release of Chrome that includes the new User-Agent Override feature in the Developer Tools settings panel and mimic the User-Agent of your Firefox+FirePHP setup. Hey, it works :)

[markstory]

Closing there are multiple browser extensions that work with the existing code.