hi moz101mo, i don't think that it is a good idea to use unbranded versions as your daily driver - they are intended for extension developers to test their addons on a codebase that is the same as firefox release, but they undergo limited to no qa, don't automatically update and might lag behind with security updates as publishing them is a manual process.

if you want to use unsigned addons in your productive firefox version i think you are far better off by using firefox developer edition: https://www.mozilla.org/firefox/developer/

Thanks, Phillip! As I understand it, somebody (Kev Needham?) at Mozilla was capturing the Nightly Firefox that matches the final, or building a nightly that matches?, and updating this page. Look at stats at bottom of page - lot of customers using it??? that are going to be unhappy like me??  :-( This page was last modified on 14 October 2016, at 10:58. This page has been accessed 562,385 times. https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds

It installs into my Developer Preview folder, but is named Nightly. It was working well, but seems to have gone by the wayside?

There are "unbranded" builds that we were promised, and that had been being delivered via the above page, from 48 something, then 49, then 49.0.1. This had been working as promised to those with old plugins that can't be signed. It was what we needed.

This is supposed to be a documented facility. But 49.0.2 has not been added. Here is Kev's page... https://blog.mozilla.org/addons/2016/07/29/extension-signing-availability-of-unbranded-builds/

The Fx 48 unbranded build, which uses the "Nightly" branding package, did update for me - but it turned into the Release version 48.0.1. And when I installed the unbranded 48.0.1 version it updated to Firefox 48.0.2. Didn't update to the next unbranded version as users expected.

Yes, the unbranded version "promised" and delivered - but IMO Mozilla reneged on that promise a bit by inserting a "channel changer" bit of code. Like what is used on the RC versions as Beta is being made ready for Release.

See this page for an alternative to using the unbranded or Dev Edition builds: http://www.largrizzly.net/firefox.html

Thanks for the info. I'll try that if it looks ok. Actually I searched for something like that for ages over weeks, and never found it. Poor comments or keywords on that page that google can't find?? Uh, x86 should be 32 bit, and x64 should be 64 bit, right?

Did you turn off autoupdate? Did those you mention all say Nightly? Or did it install the standard version because you had autoupdate? Just asking.

I used the webpage (see above) that was being kept updated by somebody in "signing", and I manually installed each time from that link. I had notify of new updates, but don't install, but I figured out to not let it auto update, just use the updated link, from the web page, that WAS being updated.

They were delivering. Worked for me. Up through 49.0.1. I have a shortcut to that web page on my desktop, and click on it every day to see if there is a new update. Small price to pay IMHO.

What is "a "channel changer" bit of code"?

x86 should be 32 bit, and x64 should be 64 bit, right? Yes.

Did you turn off autoupdate? Yes, but when I did a manual update the unbranded Nightly became the Release version.

Did those you mention all say Nightly? The unbranded version of Release carries the "Nightly" branding wording an icons (aka "theme"). I was real disappointed that Mozilla didn't create a unique "theme" for this unbranded version; also, I think Mozilla was disingenuous in having the unbranded version "jump" to the Release channel if the user updates it.

What is "a "channel changer" bit of code"? I guess I misspoke by coining and using that terminology. It doesn't really "jump" or change channels; but to the uninformed that may seem to happen.

When the Beta version development gets to the last week of its cycle a RC version (Release Candidate) becomes available for download and testing. The RC version is actually a Release version in the Mozilla program servers as a Beta, but it is coded internally for app.update.URL as a Release - to get future updates from the Release version server address. So basically the user installs the last of the Beta version as an RC, then the RC "jumps" or becomes Release the next time it is updated.

And the "unbranded Nightly" version is coded similarly for app.update.URL - when it updates the user ends up with a Release version and "signing" is required for extensions. Obviating the whole reason a user installed the unbranded version to begin with - IMO.)

"Firefox" has been available in 4 channels for a number of years now. (Not counting the ESR version, which is a "whole different story" as far as updates go.) Nightly > Web Developer (used to be named Aurora) > Beta > Release Each channel updates within each respective channel; Release updates to the next Release version, Beta always stays on the Beta channel thru all the b# versions (6 to 12 Beta versions over the 6 week development cycle); Developer Edition and Nightly also stay on their respective channels.

RC and "unbranded" will become a Release version when either gets an update. RC will look the same, as Beta used the Release icons, but "unbranded" will change the icons / branding with the first update.

Check the PM that I just sent to you.

Thanks, To be clear, you used the link on the Unbranded page each time you "manually" installed?

Yes I used this page - https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds - but I went to the "build directory" page. http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/1474569299/

Overall, I have given up using the unbranded version altogether, too much "work" to keep using it. I'm gonna stick with ESR 38.7.1 and Release 47.0.1 for awhile; like maybe until Firefox 53 or 55 when all the extensions that I currently use will need to be rewritten or be defunct. Without extensions Firefox is "just another web browser" and poorer than the average. Too many faults that are getting harder and harder to correct. The final implementation of this "unbranded" scheme and it updating to Release has me seriously reconsidering how long I'll be using Firefox.

I had auto update turned off, and whenever the Unbranded page was updated, I just clicked on the Latest release Windows 32-bit installer, downloaded, and clicked that. WAS working fine for me, although I had to adjust Norton Internet Security to add the folder that Nightly (the Unbranded Firefox name) was installed into - Mozilla Developer Preview.

I was happy with it. It was working. Now if "whosoever" will update the Unbranded to 49.0.2, I will be able to have the new security fixes it contains. I have finally gotten into a discussion by direct emailing somebody that is replying. Wish us luck!