[firebug] Re: PHP server messages

Am 06.03.2017 um 17:03 schrieb Lawrence San: I don't understand why people are ​now ​ saying you ​_have​_​ to use Chrome Logger ​ to log PHP from Firefox. Sorry, I was not clear enough: My version of chromePHP acts as a drop-in replacement for FirePHP (at least the part I regularly use). You

Re: [firebug] Re: PHP server messages

Please forgive me my forgetfullness and ignorance, Lawrence and Erik! Indeed, you provide good alternatives for Chrome Logger. After all, server-side logging works through HTTP headers, so if somebody wants to, he or she can implement their own tool to create those headers, or use the simple

Re: [firebug] Re: PHP server messages

I don't understand why people are ​now ​ saying you ​_​ have ​_​ to use Chrome Logger ​ to log PHP from Firefox.​ That's not true . In this discussion list, ​see the thread entitled "replacement for firephp (devtools)" ​ from late September to early December 2016 (sorry, I don't know how to link

[firebug] Re: PHP server messages

Am 04.03.2017 um 10:21 schrieb Pedro Bastos das Neves: The crhome logger is the only choice? This one doesn't work well too? I've modified chromePHP such that it is a bit more FirePHP-like: https://github.com/ErikKrause/chromephp -- Erik Krause -- You received this message because you are

[firebug] Re: PHP server messages

Yes, Chrome Logger is what you need to use. If you have issues integrating it into your PHP code, you should open an issue for Chrome Logger . If you integrated it into your PHP code, but the output is not shown or incorrectly shown in the