Firefox 10 is not aware of its FireBug/FirePHP add-on setting

[Fluorine]

Hi,

I've got two computers featuring two different dev configs.
A allows FirePHP debugging. B doesn't.

A: Windows 7, FF 3.6.17, FireBug 1.7.3, FirePHP 0.5.0

B : Windows 7, FF 10.0.1, FireBug 1.9.1, FirePHP 0.6.2

With B, it looks like FF is unaware of FireBug/FirePHP.
I suppose it's the case as FF doesn't even send the proper UserAgent string termination, with the FirePHP stamp, like A does.
B sends: "Mozilla/5.0 (Windows NT 6.1; rv:10.0.1) Gecko/20100101 Firefox/10.0.1"
Whereas A sends "[...] FirePHP/0.5"

That's one point.

Second point:
if I tweak Firefox UserAgent B so that it sends the proper UserAgent string to the server, with, e.g. FirePHP/0.6, then server-side, FirePHP detects it ok, and returns back its X-Wf... headers with the proper serialised stuff, ok.
But, it's pointless anyway, as FF can't interpret them.
In the FireBug console, I get this error:

TypeError: node is undefined
chrome://firebug/content/lib/domplate.js
Line 515


* * *
My questions obviously are:
- "how can I make FF to send the proper string, without tweaking it?",
and - "how can I make the FireBug console to interpret then display the FirePHP information right?"

* * *

What I have tried so far:
- create a new FF profile, didn't fix anything.
- uninstall both add-ons, restarted, reinstalled both add-on, restarting FF between each, didn't do anything.
- uninstalled FF, reinstalled FF. didn't do anything.

Thank you for your participation.

[Christoph Dorn]

Firebug 1.9 requires FirePHP extension 0.7. See: http://www.firephp.org/

[Fluorine]

Huh, I swore I had the latest one at the time of my question. I normally do look at the specs and requirements. Anyway...

Just tried, and no cigar, even after the upgrade of FirePHP, restarted FF, did a GET /, the User Agent header sent still did not have the FirePHP stamp at the end of its value string. A bit as if FF hadn't registered it properly.

Don't tell me I've got to try the uninstall-plugin / uninstall FF- / restart Windows / reinstall-FF / reinstall plugin / retry ridiculous pilgrimage again? Arghh...

[Christoph Dorn]

Just try with a fresh Firefox profile first. That usually fixes it.

You can also try DeveloperCompanion on the client (free to use for FirePHP extension equivalent features): http://developercompanion.com/

[Fluorine]

New profile worked (firefox -p for our readers).

Thank you very much for your time Christoph.

The profile thing is far from being obvious. I'm not sure "my parents" would think of doing it.
Either there's something to be done at install time, or some message of some kind's got to be displayed. What a waste of time to get it right. So many other users are still searching, hopefully they'll see this post.