Page 1 of 1

Firefox 7 Available

Posted: Tue Sep 27, 2011 12:04 pm
by jpa
Just got Firefox 7 prompt while running in Windows 7 as Admin user so apparently it's now available.

I guess I should have set app.update.enabled = false in the pref\firefox.js.

Re: Firefox 7 Available

Posted: Tue Sep 27, 2011 4:16 pm
by DraconPern
Noted! Will be updating the packages in a bit.

Re: Firefox 7 Available

Posted: Wed Sep 28, 2011 3:39 am
by MarkErrington
CE 3.6.23 as well please

Re: Firefox 7 Available

Posted: Thu Sep 29, 2011 12:06 pm
by ShakespeareVet
Today I found users attempting to update to 7.0 from the release channel. It appears updates were not disabled in the 6.0.2 release...?

Re: Firefox 7 Available

Posted: Thu Sep 29, 2011 6:11 pm
by kloostec
Mozilla has just released 7.0.1 to fix a bug with addons disappearing from the addon dialog:

http://www.mozilla.org/en-US/firefox/7. ... easenotes/

Re: Firefox 7 Available

Posted: Fri Sep 30, 2011 3:59 am
by DraconPern
Skipping 7.0 and going to 7.0.1 instead.

Re: Firefox 7 Available

Posted: Fri Sep 30, 2011 12:58 pm
by Blake
ShakespeareVet wrote:Today I found users attempting to update to 7.0 from the release channel. It appears updates were not disabled in the 6.0.2 release...?
I'm seeing the same thing here. Updates are supposed to be disabled by default, correct?

Re: Firefox 7 Available

Posted: Sun Oct 02, 2011 6:47 am
by marc.bau
Same issues here. All my users have been auto-upgraded to 7.x :( :( :(. The main reason why this upgrade has worked - seems to be that the Firefox folder has CHANGE permissions for Users from past non-MSI setups. Can you remove the completer application folder if we "re-install", please? Then I will try to remove and install via AD next time (no upgrade install).

Re: Firefox 7 Available

Posted: Sun Oct 02, 2011 7:02 am
by DraconPern
I messed up with the 6.0.2 version.. the update didn't get disabled. I am a bit hesitant to do a removal since machines will have plugins installed, and wiping the directory is probably bad.

Re: Firefox 7 Available

Posted: Sun Oct 02, 2011 7:42 am
by marc.bau
No, you must wipe on uninstall. The main reason is "cleanup" the application folder to start with a clean directory from scratch on next install (maybe something is cluttered). Additionally I see no reason to keep outdated addons. Maybe you deploy 7.0 and your addon is only 5.x. If addons are not packaged with the MSI than they need to be removed.

Re: Firefox 7 Available

Posted: Mon Oct 03, 2011 5:42 am
by DraconPern
I just realized... If your user installed 7 via the built in mechanism, the V7 MSI will notice this as an exe install and clean the directory. However it doesn't change the permission.

Re: Firefox 7 Available

Posted: Tue Oct 04, 2011 5:11 am
by marc.bau
That may be the update mechanism of Firefox... but ok, not our to do here.

I'm not sure what happens here on my side but I have very many users that have a broken Firefox now after they have been upgraded automatically to 7.0.1.

See screenthot attached. If they wouldn't have permission (if you would remove the folder itself - not only cleanup) than they wouldn't have permission to replace files and users wouldn't see XULRunner errors like mine.
XULRunner_error.png
Error message after auto upgrade to 7.0.1
XULRunner_error.png (10.58 KiB) Viewed 5575 times
I still see no reason at all to keep the %Program Files%\Mozilla Firefox folder if I uninstall Firefox. The folder need to be wiped from disk! If you would use WiX you can use RemoveExFolder on uninstall...

Re: Firefox 7 Available

Posted: Tue Oct 04, 2011 5:25 pm
by DraconPern
The 7.0.1 will do a cleaning if your users installed the .exe update. I'll have to check to see if there's any issues with doing a cleaning even on a regular install, I am just affraid that it may remove extensions that other people deploy.

Re: Firefox 7 Available

Posted: Sat Oct 08, 2011 9:37 am
by marc.bau
Only as a note, I have added a file permission policy to the Program Files\Mozilla Firefox folder that removes the previous CHANGE permission and inherits the main folder permissions. By this addition I'm back to read-only on Mozilla folder and users will not be able to upgrade again as they do not have permission to replace files. The upgrade applet may fail than (untested).