This is just a thought,
Lately every time FF updates we get a rash of problems from people who allow FF to update itself because we can not release FFP with that function [check for updates] disabled by default due to Mozilla licensing.
see:
https://portableapps.com/news/2008-02-08_-_firefox_portable_2.0.0.12#com...
and the comments after
I understand where they are coming from. Perhaps they would understand where we are coming from.
Maybe we could ask for an "emergency exemption" until the issue is resolved. Maybe if it was explained to them, and we asked permission, they would allow us to "temporarily" ship FFP with "check for updates" disabled by default with the understanding that when the issue is fixed future releases would have it re-enabled by default.
Just a thought, don't kill me 
Tim
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
*patrick pulls out knife behind back*
great idea, but that will all take time, I think that if I have any time free over the next coulple off days I'll look through the source myself to see if I can add any more information to the report in effort to get it fixed. Actually on that note am I to assume the bug is in the installer code?
Steve,
As has been mentioned, I am the only mod that is not a developer/programmer. I don't know what the actual problem is. I know that John has reported it to Mozilla and has asked people with voting rights to support a fix.
I'm just coming from a users point of view.
While we are waiting for a fix, is it possible to allow an exception to the Mozilla license.
My guess, and only a guess, is that if it were an easy fix, they would have fixed it.
Tim
Things have got to get better, they can't get worse, or can they?
I would assume so, but if it's an update then it's the update installing.
I think it would be justified because when John and Mozilla worked out the license agreement, using the built in updated wasn't an issue because back then it would work. So there was no reason for having it disabled. But since then things changed. Now, it is an issue because they changed something (I once had a exact link to the bug report) and now the built-in updater messes with the registry.
I wouldn't go as far as saying they violated the agreement but it surely isn't nice.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate