280348 - ForecastFox not showing up after it's been installed

Status: RESOLVED INVALID

(Toolkit :: Add-ons Manager, defect)

Description

[yanis]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I installed the ForecastFox extension but when I attempt to change the options
of this extension, to choose the Code, Unit of Measure, ForecastFox Location, I
cannot do so. Even if I complete the fields, I press the OK button several
times, but it just wont do anything. Also, in the Forecast Location dropdown
field, the available options to place ForecastFox do not show up. I tried to
unistall and install the extension several times but the same problem appeared.

Reproducible: Always

Steps to Reproduce:
1. Install ForecastFox
2. Restart Browser
3. Attempt to fill in the Options for this Extension
Actual Results:  
The weather forecast did not show up in the browser and I was unable to change
the options of the Extension even though it appeared as a normal extension
installed in the extensions list.

Expected Results:  
The weather icons should have appeared in the browser.

Comment 1

[Mats Palmgren (inactive)]

Did you have weatherfox installed earlier? (bug 275554)

Comment 2

[yanis]

No, I didnt. I thought weather fox was for thunderbird not for firefox.

Comment 3

[Jon Stritar]

This is actually a problem with Forecastfox (which is fixed in the next
version). You can get around it by deleting the forecastfox directory in your
Firefox profile. When files in there get corrupted, Forecastfox gets errors
trying to save the new profile settings. If you're on windows, the Firefox
profile directory is usually something like c:/documents and
settings/<user>/Application Data/Mozilla/Firefox/Profiles/<yourprofile>/ ...
then delete the forecastfox directory. You can post on
http://forecastfox.mozdev.org/ if you have more questions.

Comment 4

[Nickolay_Ponomarev]

invalid per comment 3.