Home/ Questions/Q 695625
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T02:58:44+00:00

I’m using require_once() in header.php to include the FirePHP library. In the page.php I’m

  • 0

I’m using require_once() in header.php to include the FirePHP library. In the page.php I’m doing the usual…

$firephp = FirePHP::getInstance(true);
$firephp->log($categories);

Getting these errors..

'Headers already sent....'

and

Cannot send log data to FirePHP. You must have Output Buffering enabled via ob_start() or output_buffering ini directive...

I figured the using require_once in the template’s header.php (above all HTML output) would be safe (pre header output). Guess this is not the case.

Anyone have experience with this? (P.S. I tried the WP FirePHP plugin, wasn’t working right)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    FirePHP uses the output headers to transfer debugging data to the browser. So the require_once() statement is not the problem, but the fact that you do logging in page.php, at which point HTML has already been output. Not only do you need to include FirePHP before any content has been sent – you need to also do all logging before sending content as well.

    The usual workaround is to hold any output to the browser using output buffering and the ob_* family of functions. That enables you to send out headers even though echo() commands (and the likes) have already been issued.

    I am guessing doing all this safely is what the WP_FirePHP plugin was made for. I would recommend taking a second look at that plugin.

    • 0