Firefox2 Beta 2 - Page 2

**Chris** · 01-09-2006, 11:57

Quote:

Originally Posted by nffc

It installs to a different folder than 1.x so you have 2 versions on the system.

Mac apps are handled somewhat differently.

Basically though, yes, it does install separately.

However the Mac version at least must still interact with the application pref file because FF1.5 thought it was being run for the first time after I closed 2.0 and restarted 1.5. The 'portable' version of 2.0 I am trialling also had a full list of extensions loaded on the computer so it is definitely interacting with my existing install somewhere or other.

---------- Post added at 10:57 ---------- Previous post was at 10:52 ----------

Quote:

Originally Posted by Electrolyte

I like having the browser open all windows from the last time it was run, but since there is no shortcut to close the entire browser, I have to keep going to File > Exit. If it was in the task tray I could either just minimise all the windows to it or close it straight from that icon.

In my experience, extensions are normally updated reasonably soon after a full release of the browser. Once FF2 is out for real, you won't have to wait long.

I don't imagine it is worth the developer's time updating the extension while FF2 is still in Beta, in case any last-minute changes break it again.

Skatoony · 01-09-2006, 13:45

Quote:

Originally Posted by Chris T

In my experience, extensions are normally updated reasonably soon after a full release of the browser. Once FF2 is out for real, you won't have to wait long.

I don't imagine it is worth the developer's time updating the extension while FF2 is still in Beta, in case any last-minute changes break it again.

I don't think the developer has had the chance to test it yet since it works on FF2 B1.

ben1390 · 02-09-2006, 17:13

A theme to get the look of Firefox 2.0 can be downloaded from here for people that don't want to use the Beta because extensions aren't compatiable etc.

Mal · 03-09-2006, 00:07

Don't forget Nightly Tester Tools extension to make your extensions compatible.

Only one of my extensions has failed since trying the Beta's, when I changed to Beta 2.

The rest work as with v1.5. I've even got 2 extensions which supposedly are only for pre v1.0.

ben1390 · 03-09-2006, 23:58

Quote:

Originally Posted by Mal

Don't forget Nightly Tester Tools extension to make your extensions compatible.

Only one of my extensions has failed since trying the Beta's, when I changed to Beta 2.

The rest work as with v1.5. I've even got 2 extensions which supposedly are only for pre v1.0.

Very good extension a rep point form me

Mal · 04-09-2006, 00:15

Another thing is to visit the extension's website to see if there is an update there.

There has been a couple of updates which have not come through the "Find update".

AndrewJ · 04-09-2006, 00:54

Quote:

Originally Posted by Mal

Don't forget Nightly Tester Tools extension to make your extensions compatible.

Only one of my extensions has failed since trying the Beta's, when I changed to Beta 2.

The rest work as with v1.5. I've even got 2 extensions which supposedly are only for pre v1.0.

Thanks helped a friend out did that

mart44 · 07-09-2006, 11:26

Regarding extension compatibility and making them compatible with the Nightly Tester Tools extension. The extension is the answer to the problem but one annoying thing can still happen when you check for Firefox updates (Help Menu) to Firefox 2 beta 2.

The update gets downloaded and before automatically installing itself, an extension compatibility check is carried out. The check seems to take no notice of the fact that incompatible extensions have been made compatible using Nightly Tester Tools. Extensions that have been made compatible may become disabled after the update. This can be overcome by right-clicking on the disabled extensions and enabling them again. It can be a nuisance to do that though, since updates to Firefox 2 beta 2 are sometimes quite frequent.

If you find this happening, there is something that can be done to prevent it:

* Type about:config into the address bar (or find it in the Help Menu once Nightly Tester Tools is installed).

* Type (or copy and paste) this into the 'Filter' box: extensions.checkCompatibility

* Double-click the entry in the list to change the value to false

Saves a bit of hassle.

basa · 07-09-2006, 12:52

Sheesh .. when I upgrade to final or beta I just install to the same directory and all my settings and everything just appear exactly as before ??????

Oh hang on .............

I'm using Opera

Mal · 07-09-2006, 14:55

Quote:

Originally Posted by mart44

Regarding extension compatibility and making them compatible with the Nightly Tester Tools extension. The extension is the answer to the problem but one annoying thing can still happen when you check for Firefox updates (Help Menu) to Firefox 2 beta 2.

The update gets downloaded and before automatically installing itself, an extension compatibility check is carried out. The check seems to take no notice of the fact that incompatible extensions have been made compatible using Nightly Tester Tools. Extensions that have been made compatible may become disabled after the update. This can be overcome by right-clicking on the disabled extensions and enabling them again. It can be a nuisance to do that though, since updates to Firefox 2 beta 2 are sometimes quite frequent.

If you find this happening, there is something that can be done to prevent it:

* Type about:config into the address bar (or find it in the Help Menu once Nightly Tester Tools is installed).

* Type (or copy and paste) this into the 'Filter' box: extensions.checkCompatibility

* Double-click the entry in the list to change the value to false

Saves a bit of hassle.

I have never had that problem before when using nightly tester tools...good to know though.

---------- Post added at 13:55 ---------- Previous post was at 13:54 ----------

Quote:

Originally Posted by basa

Sheesh .. when I upgrade to final or beta I just install to the same directory and all my settings and everything just appear exactly as before ??????

Oh hang on .............

I'm using Opera

Strange, that's what happens with us as well

...install into the same directory and the extensions are stored in the profile and reused.

basa · 07-09-2006, 14:58

Quote:

Originally Posted by Mal

...........Strange, that's what happens with us as well

...install into the same directory and the extensions are stored in the profile and reused.

Ahh .. that's if they are compatible with the new version

Mal · 07-09-2006, 15:02

Quote:

Originally Posted by basa

Ahh .. that's if they are compatible with the new version

When I tried to get a new theme for Opera, I think only 1 was compatible with Opera 9, so stick that in your pipe!

That prevented me from changing the user agent, as that option didn't appear on the menu.

At least there is an extension there to sort it out on FF

basa · 07-09-2006, 16:04

Quote:

Originally Posted by Mal

When I tried to get a new theme for Opera, I think only 1 was compatible with Opera 9, so stick that in your pipe!

That prevented me from changing the user agent, as that option didn't appear on the menu.

At least there is an extension there to sort it out on FF

I found at least 15 skins for Op 9.xx.

At least it tells you it is / is not compatible

Usually when you do a one click skinning (i.e. from within Opera) it will tell you immediately if it is compatible.

Personally I have now used the same skin through Opera 7.xx up to 9.xx

PS BTW I was winding all you FF users up

mart44 · 07-09-2006, 18:08

I found the beta version of Firefox 2.0 initially grabbed hold of the existing 1.5 Profile and disabled a few extensions. It was OK after a separate Profile was created for Firefox 2.0. After that, one Profile or the other could be selected in the Profile Manager when starting up each version of the browser.

Alternatively, a couple of .bat files can be used to make the browsers start up independantly of each other without the need to use the Profile Manager. Firefox 1.5 and Firefox2 Beta 2 can even both run at the same time (if you want them to), each one using its own Profile. I found that best in the end. Instructions here on how to set it up.

Mal · 07-09-2006, 18:46

Quote:

Originally Posted by mart44

I found the beta version of Firefox 2.0 initially grabbed hold of the existing 1.5 Profile and disabled a few extensions. It was OK after a separate Profile was created for Firefox 2.0. After that, one Profile or the other could be selected in the Profile Manager when starting up each version of the browser.

Alternatively, a couple of .bat files can be used to make the browsers start up independantly of each other without the need to use the Profile Manager. Firefox 1.5 and Firefox2 Beta 2 can even both run at the same time (if you want them to), each one using its own Profile. I found that best in the end. Instructions here on how to set it up.

Yes Firefox will use the existing default profile and check to see if they are compatible. If not, it will disable them. It's what it's supposed to do.

The annoying thing about using 2 profiles was when trying to open a link from an email or from a separate application. With the FF shortcuts, you had to put the "-P" profilemanager suffix, to tell FF which profile to use, but you can't with the above. So with me anyway, it must have tried to open the 1.5 profile and went through the compatibility test.

Alternate to using the profile manager, just keep a backup copy of your profile, uninstall 1.5 and install 2.0. If you want to go back to 1.5, uninstall 2.0, swap the profiles over and then install 1.5.