With these steps done, you can start using FirePHP. In PHP, this is accomplished by calling ob_start near the top of your script: Once you have the FirePHP library on your server, you need to include it in your script with a line like:īecause FirePHP sends its logging data via the HTTP headers, you’ll need to buffer your script’s output so that the response headers can include content generated further down the script. For the sake of this walk-through, I’ll focus on the stand-alone functionality. There are also versions designed to integrate with various frameworks or content management systems, such as the WP-FirePHP plugin for WordPress or the JFirePHP plugin for Joomla. After that, you simply need to include the library in your code. This is a stand-alone version of the library that can either be downloaded manually or installed using PEAR.
#INSTALL FIREBUG FOR CHROME INSTALL#
You also need to install the FirePHP server-side library, which is available here.
Click on that bug and a menu will appear allowing you to enable or disable FirePHP: Once FirePHP is installed, when you next open your Firebug panel, you’ll now see an additional blue bug. This requires that you already have Firebug installed. To start, you first need to install the FirePHP extension from Mozilla’s Firefox Add-ons site. Once you’re set up, you can log warnings and errors in your PHP scripts to the Firebug console, just as if you were developing JavaScript. But did you know it can also be used to debug PHP? Yes, thanks to an additional Firefox extension called FirePHP.īy combining this extension, which sits on top of Firebug, with a server-side library, your PHP scripts will be able to send debugging information to the browser, handily encoded in the HTTP response headers. The little ’bug is a fantastically useful HTML/CSS/JavaScript/Ajax debugger. If you’re anything like me, you’d sooner forgo water than Firebug when working on a web project.
0 kommentar(er)
