Own add-ons blocked
Since some latest fx version my personal add-ons are blocked. I know about all this 'signing' changes but it really annoys me. Before that I can just change the 'xpinstall.signatures.required' flag in about:config and live in peace with this new politic. Now I can't use my own add-ons. I know they will work on ESR version but only for some time (till next ESR version I guess) and I'm not satisfied with temporary solutions. I don't want to sign my add-ons because it's no one's business what I made by myself for myself (plus it's annoying).
So I wonder what should I do to avoid signing my personal add-ons and still use newest firefox (which I love, but lately not as much as before).
Valitud lahendus
Developer Edition gets updated almost daily, whenever there is a new check-in. It is an alpha-2 level piece of software that is 6 weeks before the Beta stage of development and 12 weeks before Release.
tom3454 said
... I have a question. If I use this unbranded fx will I still have auto update? I don't want to constantly check if new version is on the server...
When the unbranded version does get updated manually it will become the Release version - doesn't stay as unbranded. I don't know if it does auto update, but I figure that if it does it won't be unbranded any longer.
I installed the unbranded version; then when 48.0.1 was released did a manual update; ended up on the Release channel. Reinstalled it and when 48.0.2 came out the same change to the Release channel. Gabe up after that.
See this for a "fix": http://www.largrizzly.net/firefox.html
Loe vastust kontekstis 👍 0All Replies (8)
hi tom3454, in this case firefox developer edition is for you - you can still set the xpinstall.signatures.required preference there. https://www.mozilla.org/firefox/developer/
Hi philipp, dark skin and additional tools slowing down my browser doesn't sound great. I found "unbranded" firefox edition but it's only in us english and as you can see english isn't my strength. But let's say it's ok. I have a question. If I use this unbranded fx will I still have auto update? I don't want to constantly check if new version is on the server...
please stick with firefox devedition, it's the better choice than the unbranded builds. if you don't like the dark theme then just switch back to the regular one in the firefox menu ≡ > addons > themes panel. none of the dev tools will slow your browser down if you don't use them - they are included in normal firefox release builds as well, but get just a bit more advertised in devedition.
Two more questions: is developer edition auto-updated? And is it build with stable version and released same day or is it unstable or delayed?
yes it is auto-updating and receives updates daily. it is also a pre-release build (like an early beta) which means it receives new features earlier which might make it a bit more unstable than release builds but i've never had a major issue with it and am using it for years now.
So I have to choose between private add-ons and stability (I don't have such good experiences with firefox beta as you and it seems dev edition is build upon nightly builds which doesn't augur well for stability - it's going to be my primary browser).
Backing to unbranded edition, is it just stable version of firefox with all features and auto-update but without logo and duty to signing add-ons or are there some other differences?
Valitud lahendus
Developer Edition gets updated almost daily, whenever there is a new check-in. It is an alpha-2 level piece of software that is 6 weeks before the Beta stage of development and 12 weeks before Release.
tom3454 said
... I have a question. If I use this unbranded fx will I still have auto update? I don't want to constantly check if new version is on the server...
When the unbranded version does get updated manually it will become the Release version - doesn't stay as unbranded. I don't know if it does auto update, but I figure that if it does it won't be unbranded any longer.
I installed the unbranded version; then when 48.0.1 was released did a manual update; ended up on the Release channel. Reinstalled it and when 48.0.2 came out the same change to the Release channel. Gabe up after that.
See this for a "fix": http://www.largrizzly.net/firefox.html
Thank you the-edmeister, this bypass works great (for now). I don't really get why you have to choose one from freedom (own add-ons), stability and convenience (auto updates). Quo vadis Mozilla?