[GH-ISSUE #152] New commit 01721704fd causes FireBug to break #49

Closed
opened 2026-03-04 02:11:41 +03:00 by kerem · 12 comments
Owner

Originally created by @InputOutput on GitHub (Jan 22, 2013).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/152

ErrorException: Notice: Undefined property: Symfony\Bridge\Monolog\Handler\FirePHPHandler::$sendHeaders in /vagrant/vendor/symfony/symfony/src/Symfony/Bridge/Monolog/Handler/FirePHPHandler.php line 66

Originally created by @InputOutput on GitHub (Jan 22, 2013). Original GitHub issue: https://github.com/Seldaek/monolog/issues/152 ErrorException: Notice: Undefined property: Symfony\Bridge\Monolog\Handler\FirePHPHandler::$sendHeaders in /vagrant/vendor/symfony/symfony/src/Symfony/Bridge/Monolog/Handler/FirePHPHandler.php line 66
kerem closed this issue 2026-03-04 02:11:41 +03:00
Author
Owner

@tristanbes commented on GitHub (Jan 22, 2013):

+1 caused by d8d5f96760

ping @Seldaek It's crashing the whole application

<!-- gh-comment-id:12546084 --> @tristanbes commented on GitHub (Jan 22, 2013): +1 caused by d8d5f96760425e7870992e0001576dcc56e82eff ping @Seldaek It's crashing the whole application ![](http://alltheragefaces.com/img/faces/png/neutral-whyyyyy.png)
Author
Owner

@tristanbes commented on GitHub (Jan 22, 2013):

Thanks ;-)

<!-- gh-comment-id:12547870 --> @tristanbes commented on GitHub (Jan 22, 2013): Thanks ;-)
Author
Owner

@Seldaek commented on GitHub (Jan 22, 2013):

OK I added some BC layer, which I think will work. I don't have a symfony 2.2 project at hand so please run composer update and confirm if it worked :)

If it doesn't work, as a workaround you can require monolog in "1.3.1" explicitly for now.

<!-- gh-comment-id:12547875 --> @Seldaek commented on GitHub (Jan 22, 2013): OK I added some BC layer, which I think will work. I don't have a symfony 2.2 project at hand so please run composer update and confirm if it worked :) If it doesn't work, as a workaround you can require monolog in "1.3.1" explicitly for now.
Author
Owner

@tristanbes commented on GitHub (Jan 22, 2013):

i'll do this right now.

<!-- gh-comment-id:12547894 --> @tristanbes commented on GitHub (Jan 22, 2013): i'll do this right now.
Author
Owner

@tristanbes commented on GitHub (Jan 22, 2013):

@Seldaek PHP Fatal error: Cannot redeclare Monolog\Handler\FirePHPHandler::$sendHeaders in /Volumes/Elao/workspace/6board/vendor/monolog/monolog/src/Monolog/Handler/FirePHPHandler.php on line 59

<!-- gh-comment-id:12547959 --> @tristanbes commented on GitHub (Jan 22, 2013): @Seldaek PHP Fatal error: Cannot redeclare Monolog\Handler\FirePHPHandler::$sendHeaders in /Volumes/Elao/workspace/6board/vendor/monolog/monolog/src/Monolog/Handler/FirePHPHandler.php on line 59
Author
Owner

@Seldaek commented on GitHub (Jan 22, 2013):

I am a moron, please update again :)

<!-- gh-comment-id:12548134 --> @Seldaek commented on GitHub (Jan 22, 2013): I am a moron, please update again :)
Author
Owner

@tristanbes commented on GitHub (Jan 22, 2013):

Fixed. ;-) 👍

<!-- gh-comment-id:12548205 --> @tristanbes commented on GitHub (Jan 22, 2013): Fixed. ;-) :+1:
Author
Owner

@Seldaek commented on GitHub (Jan 22, 2013):

OK thanks. If you can please check that it also still disables it properly, like if you view the headers in chrome it shouldn't contain the firephp headers for example. But I think the patch is alright now.

<!-- gh-comment-id:12548271 --> @Seldaek commented on GitHub (Jan 22, 2013): OK thanks. If you can please check that it also still disables it properly, like if you view the headers in chrome it shouldn't contain the firephp headers for example. But I think the patch is alright now.
Author
Owner

@tristanbes commented on GitHub (Jan 22, 2013):

I can confirm that :
headers

<!-- gh-comment-id:12548586 --> @tristanbes commented on GitHub (Jan 22, 2013): I can confirm that : ![headers](https://f.cloud.github.com/assets/346010/86645/3b695d6e-64a6-11e2-82c4-328e311ae692.png)
Author
Owner

@InputOutput commented on GitHub (Jan 23, 2013):

Fixed the problem on my side too, thanks!

<!-- gh-comment-id:12583420 --> @InputOutput commented on GitHub (Jan 23, 2013): Fixed the problem on my side too, thanks!
Author
Owner

@hasryan commented on GitHub (Jan 24, 2013):

Terribly sorry to see the issues caused by my original commit. We use Monolog in isolation and I was unaware of the impact it could have elsewhere. Apologies for the trouble.

<!-- gh-comment-id:12631548 --> @hasryan commented on GitHub (Jan 24, 2013): Terribly sorry to see the issues caused by my original commit. We use Monolog in isolation and I was unaware of the impact it could have elsewhere. Apologies for the trouble.
Author
Owner

@Seldaek commented on GitHub (Jan 24, 2013):

No worries, I should have been more cautious with removing protected properties too, anyway everyone is back on track. It's part of the risks (and fun?) of using unstable versions :)

<!-- gh-comment-id:12641184 --> @Seldaek commented on GitHub (Jan 24, 2013): No worries, I should have been more cautious with removing protected properties too, anyway everyone is back on track. It's part of the risks (and fun?) of using unstable versions :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/monolog#49
No description provided.