mirror of
https://github.com/Seldaek/monolog.git
synced 2026-04-26 16:15:49 +03:00
[GH-ISSUE #513] FirePHPHandler bubles errors and ChromePHPHandler disable FirePHPHandler #180
Labels
No labels
Bug
Documentation
Feature
Needs Work
Support
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/monolog#180
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BlackScorp on GitHub (Feb 25, 2015).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/513
Hello everyone,
maybe i didn't understood what bubbling means, but following code display all log messages in firebug console
but i expected to see only debug message, in my code i use info and warning logs with different handler and the debug schould be a replacement for var_dump
maybe i used it wrong?
also if i add ChromePHPHandler
there are no logs anymore in FirePHP Console, only in ChromePHP, however if i add the chrome handler to buffer handler
then i see the log messages in Chrome and Firefox but still all messages are displayed, while bubbling is deaktivated.
is this a real bug? or just wrong usage?
Cheers
@stof commented on GitHub (Feb 25, 2015):
Well, given you pushed a ChromephpHandler on the stack and it disables bubbling, no messages will go to the next handler in the stack. So it is expected that firefox does not receive log messages anymore.
when you use the BufferHandler, you see logs in firefox because the BufferHandler itself allows bubbling in your code.
And the level they accept is the min level for which they handle messages. Setting the level to debug will accept anything.
If you want to display only debug messages in chrome and firefox, there is 2 solutions:
@BlackScorp commented on GitHub (Feb 25, 2015):
@stof thanks, everything is working now so it was a bad usage after all