What steps will reproduce the problem? 1.create 2 pages each with a firePHP log. Verify that both work as expected indipendently 2.add a redirect header('Location: /request2.php'); to the first page after the firePHP log call. 3. request the page with the redirect via browser.

What is the expected output? What do you see instead?

Expect to get logs from both pages. Instead seeing no logs from first page and logs duplicated for 2nd page.

What version of the product are you using? On what operating system?

0.3.1 library. 0.4.3 extension os x

Please provide any additional information below.

console network tab shows appropriate requests.

test code: request1.php <? require_once('FirePHPCore/FirePHP.class.php'); $firephp = FirePHP::getInstance(true);

$firephp->log('firephp says.... request 1'); header('Location: /request2.php'); echo "request 1"; ?>

request2.php <? require_once('FirePHPCore/FirePHP.class.php'); $firephp = FirePHP::getInstance(true);

$firephp->log('firephp says.... request 2');

echo "request 2"; ?>

calling request1.php outputs 'firephp says.... request 2' twice to the console.

Test Page: http://reference.developercompanion.com/Tools/FirePHPCompanion/Run/Examples/TestRunner/

Classic FirePHP to Firebug Console -> Redirect

Comment deleted

Any word on this (i've checked commits on github but non mention this bug)?

Your extension is great - it only shows how much when i return to old debug mode (i'm also troubled with above error ;/ ).

Big TIA ;-)

Also see: http://firephp.842658.n2.nabble.com/messages-not-shown-if-header-redirect-td5320120.html

Comment deleted

This will be fixed as part of FirePHP 1.0 and the FirePHP Companion client extension.

FirePHP 1.0: http://upgrade.firephp.org/

Issue: http://github.com/cadorn/firephp-libs/issues#issue/2

No hope to get this fixed for classic PHP lib, outside DeveloperCompanion extension?

Possibly yes, but not anytime soon since Firebug resets on every new page load.

It'd be helpful if this bug would be fixed - especially since FireConsole doesn't seem to be near in any way; the last commit on it was 3 years ago and its alpha isn't compatible with the latest Firefox 21.