Skip to content

Latest commit

 

History

History
80 lines (47 loc) · 2.59 KB

README.md

File metadata and controls

80 lines (47 loc) · 2.59 KB

Ignite Firephp

CodeIgniter FirePHP third party package with helper class for outtputting PHP debug information to your browser console.

##Table of Contents

[TOC]

NOTE: the hope being that one day soon I'll log on, and this will actually be a table of contents.

Getting Started

This document quickly outlines how to get your development environment up and running using FirePHP in CodeIgniter for Google Chrome and Firefox.

Installation

Move the firephp folder from within the distribution folder into your CodeIgniter application's third party folder, manually (boring) or using your favourite package manager, for example Bower.

bower install ignite-firephp

CodeIgniter

In your application's autoload configuration file located in applications/config/autoload.php you'll want to autoload the third party package, as well as its library and helper classes.

$autoload['packages'] = array(APPPATH.'third_party/firephp/');
$autoload['libraries'] = array('fb');
$autoload['helper'] = array('fb');

Browser

To use FirePHP in Google Chrome the best solution is FirePHP4Chrome. Simply install the Chrome extension, open up Google's debugging tool by pressing ctrl+alt+i, and you'll see a message that says "FirePHP4Chrome logging activated. You may need to refresh this page.".

To use FirePHP in FireFox, simply install the FireBug and FirePHP plugins.

Usage

The standard FirePHP API has been wrapped in a few convenient PHP function for consumption in your CodeIgniter application, and your debugging pleasure.

Log

fphp_log( object|array|string|int [, string label] )

General message logging to the console.

Info

fphp_info( object|array|string|int [, string label] )

Information message logging to the console.

Warn

fphp_warn( object|array|string|int [, string label] )

Warning message logging to the console.

Error

fphp_error( object|array|string|int [, string label] )

Error message logging to the console.

Trace

fphp_trace( string label )

Backtrace indicating execution path to point at which trace is triggered.

Suggestions or Comments?

Anything to add? Any suggestions or comments are always welcome.