Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin no loner works after FireFox upgrade to v51.0.1 (32-bit) #28

Closed
sionp opened this issue Feb 3, 2017 · 8 comments
Closed

Plugin no loner works after FireFox upgrade to v51.0.1 (32-bit) #28

sionp opened this issue Feb 3, 2017 · 8 comments

Comments

@sionp
Copy link

sionp commented Feb 3, 2017

Cannot see any output in the console window, despite FirePHP data being available in the HTTP response headers.

@sionp
Copy link
Author

sionp commented Feb 7, 2017

Update on this issue - it does still work, however, it now requires that the 'Show CSS Errors' option is switched on in the console options.

@morosanuae
Copy link

No, it still doesn't work even with that option turned on. No output to the console. Too many unresolved problems with this extension. It's seems to be abandoned. Maybe I should look elsewhere...

@lorenzos
Copy link

lorenzos commented Mar 4, 2017

@morosanuae Same feeling here, and also Firebug itself is going to die, since developers and developing moved efforts into to the Firefox internal dev tools (which btw it's not so bad, I think recently it became better than Firebug). Fortunately I found this:
https://github.com/ErikKrause/chromephp

It works well, and this fork in particular supports the same firephp API, so it should be easy for you to move on. I already did.

@jdlx
Copy link

jdlx commented Mar 4, 2017

@lorenzos … doesn't Chrome have an issue with (too) large headers?
I tried FirePHP4Chrome once, but it was fairly useless due to the header size restrictione …

@lorenzos
Copy link

lorenzos commented Mar 4, 2017

You don't have to use Chrome! You can use ChromePhp on Firefox too, and you don't have to install any extension!

That said, I don't know if Firefox have the same issue with headers too large. You can try.

@ianchanning
Copy link

@sionp I had tons of CSS warnings, so turning on 'Show CSS Errors' wasn't a good solution. However I have found that it also works by turning on 'Show JavaScript warnings'.

@cadorn
Copy link
Member

cadorn commented Jul 29, 2019

A new FirePHP extension has been released that works for Firefox >= 56.0.2.

It also supports the ChromePHP/ChromeLogger protocol.

See: http://firephp.org/

@cadorn cadorn closed this as completed Jul 29, 2019
@jdlx
Copy link

jdlx commented Jul 29, 2019

This is great news! THX Christoph!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants