Assegnate 2 su 5 stelle

di sweetcera il Ago. 22, 2012 ·

I keep having to downgrade to 2.0.5 because the new version is throwing the same error. :-(

Questa recensione riguarda una versione precedente (2.0.7.1-signed) del componente aggiuntivo. 

di Mime Čuvalo (Sviluppatore) il Ago. 23, 2012 ·

Sorry that you've run into this issue. The new version of FireFTP is doing migration of an old account format to a new one. Unfortunately, there are some illegal characters that make it difficult to upgrade to the new format that Mozilla now requires. (specifically, the combination of trying to convert international characters and the '%' character creates problems).

If 2.0.7 isn't working for you, you can try the following:
- find your profile folder, here are instructions: http://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data (if you're on a Mac it'll be under: ~/Library/Application Support/Firefox/Profiles)
- find the file in your profile folder called fireFTPsites.dat
- remove the '%' characters found in the file.
- install version 2.0.7 and readd the % characters back in later as needed. (not directly into the file, but via the regular FireFTP interface).

Again, sorry for the inconvenience,
Mime

Assegnate 4 su 5 stelle

di sweetcera il Ago. 17, 2012 ·

Usually Great, but this update has an error!

It won't let me use it at all now. Every time I try to click Connect or the drop down to do anything, it gives me this error message.

Error message= TypeError: gSiteManager is undefined
URL= chrome://fireftp/content/js/etc/sessionsPasswords.js
Line Number= 303

Screen Shot!
http://i44.photobucket.com/albums/f22/sweetcera/Screenshot2012-08-17at85332AM.png

Questa recensione riguarda una versione precedente (2.0.6.1-signed) del componente aggiuntivo. 

di Mime Čuvalo (Sviluppatore) il Ago. 17, 2012 ·

Sorry for the bug in the first place. It is fixed in the next version (2.0.7) which can be found here: https://addons.mozilla.org/en-US/firefox/addon/fireftp/versions/
(until it is officially reviewed by the Mozilla add-on team)

I appreciate your patience and understanding with the bug - sorry again for the inconvenience.