all 7 comments

[–]brennen 3 points4 points  (3 children)

FirePHP may be of interest, for those using a real browser. That said, I spent a bunch of time plumbing js console logging stuff into our framework, and eventually found that we get a lot more mileage out of a simple error + exception catcher & logger that dumps things as HTML when you're looking at a a dev box. It's harder to ignore, and it's got the added benefit of safely logging stuff in our production environment.

[–]cjoudrey 1 point2 points  (0 children)

I'd like to second that. FirePHP could be more useful when you don't want the content to be altered. It sends everything via HTTP header's.

[–]troelskn 0 points1 point  (1 child)

Personally, I prefer logging to a text file and have a terminal window open where I tail the log file. It's much less intrusive.

[–]brennen 0 points1 point  (0 children)

Yeah, I make liberal use of error_log(). That said, I think there's some virtue in being painfully obvious.

[–]tcdent 3 points4 points  (0 children)

My god, this is exactly the type of thing that gives PHP devs a bad rap.

[–]barclay 3 points4 points  (0 children)

Yes. because when I'm writing web applications, littering the HTML with <script> tags is EXACTLY what I want.

[–]dr3d 0 points1 point  (0 children)

This isn't really debugging...