Page 1 of 1

FlagFox extention is Broken ! [OBSOLETE]

Posted: Sat Nov 11, 2017 3:44 pm
by Darker

My FlagFox extention has been broken I lost everything I made there
I mean what inside
user_pref("extensions.flagfox.useractions", "....")

Anyway the error message

Code: Select all

Sorry, the Flagfox extension has encountered a problem. It is recommended that you reinstall Flagfox and restart Firefox to attempt to repair the problem. The following error output and a Flagfox preferences dump has been sent to Tools -> Error Console.

FLAGFOX VERSION: 5.2.3 (2017-11)

ERROR MESSAGE: Failed to init options window

EXCEPTION THROWN: Error: Actions not loaded!


BROWSER: Mozilla Firefox 56.0.2 (Gecko 56.0.2 / 20171024165158)
OS: Windows NT 6.1 (WINNT x86-msvc windows)
LOCALE: en-us content / en-us UI / en-us OS

Select and copy the error report above. In order to fix this problem for you and others, please read and follow the troubleshooting and bug reporting instructions on the Flagfox support forums. Please post an abundance of information with any error reports, namely what you were doing at the time that may have triggered this. (English please)

Re: FlagFox extention is Broken !

Posted: Sun Nov 12, 2017 6:02 am
by DaveG
You probably didn't lose anything. Mozilla is just banning old APIs, so we've had to transition to WebExtensions, and they've provided zero post-transition migration. Flagfox 5.2.x just stores data in a different place... that Mozilla said they might actually providing a UI for at some point, but never have. Flagfox 5.2+ data is stored in a separate file in your Firefox profile. The path is OS dependent, but it's somewhere under your OS user main folder, in wherever application settings are, then in a Mozilla folder will be your Firefox profile(s). Your Firefox profile folder will be somewhere like one of these, depending on OS:
<OS user folder>/.mozilla/firefox/<Firefox profile>/
C:\Users\<OS user folder>\AppData\Roaming\Mozilla\Firefox\<Firefox profile>\

WebExtension storage gets its own new folder called "browser-extension-data", and then each addon can get its own folder in that named using its addon ID. For Flagfox, that's "{1018e4d6-728f-4b20-ad56-37578a4de76b}". The storage.js folder in that has all the stuff, now. It's probably fine; a few people have reported this odd new error, which I'm thinking is either a race condition or Firefox dropping the ball on actually following through with the load it was tasked with. I found that SeaMonkey got this 100% of the time, so I had to disable the new pref backend there. I've been fighting against various Mozilla bugs in this area recently, and unfortunately their response is that they don't care, because everyone has to switch to their 3rd new API in 4 years, soon, so nobody cares about the old one. I'll hopefully have the new version of Flagfox finished for the full transition in the next couple days, which should hopefully not have this problem.

Re: FlagFox extention is Broken !

Posted: Sun Nov 12, 2017 8:16 pm
by Darker
Thanks for replying me I solved the problem of installation and that error message by deleting the extention from the profile folder and reinstalling it via xpi file.
The problem now is in each firefox restart all my flagfox settings and what ever get reset and I loose everything again !
The "prefs.js" File loose user_pref("extensions.flagfox.****************") data only ?

Re: FlagFox extention is Broken !

Posted: Tue Nov 14, 2017 7:43 am
by DaveG
The settings other than user actions are just the little switches of turning favicons on or off, picking whether to open actions in new tabs or windows, and some bits remembering your "don't tell me again" settings. The only thing you really are likely to care about is the user actions pref. That, and everything else, are in the storage.js in the current version with a current version of Firefox (as of yesterday), and in the prefs.js it's all under "extensions.flagfox.*" (per Mozilla's insistence for all addons). Anything currently set to default is omitted (the entire actions list must be (re)set to default to omit).

That said, the Firefox 57 addon-apocalypse is now uipon us... and dear lord I hate CSS, as it's caused me to miss the date to get a compatible version out before the Firefox update. If you don't stick with Firefox 52 ESR (the security/stability updates only version, and with at least one fewer bug...), Firefox 57 will have no Flagfox for the time being. :(