xiaoxiaoflood / firefox-scripts

userChromeJS / autoconfig.js and extensions
Mozilla Public License 2.0
989 stars 85 forks source link

Upgraded to FF87 Dev Edition. All the XUL addons from here got disabled. Now what? #74

Closed mzso closed 3 years ago

mzso commented 3 years ago

As well, as some others. What gives? It worked initially, but while running FF decided to permanently disable them on the fly. How do I fix this? (The message was something about them cannot be verified, but localized to my language.)

I even tried upgrading to the latest config.js, which I didn't do the last update. (yet everything worked.) As well as the files in chrome/utils. It didn't help. Do extensions that were disabled like this remain disabled, or something is still wrong?

mzso commented 3 years ago

Well, apparently I can't restart any either, because the browser claims its corrupted. Uh, nope. I made a mistake. Can I re-enable them though without reinstalling? Where are the addons' state stored?

xiaoxiaoflood commented 3 years ago

Legacy addons almost never delete settings on uninstall, so you probably can uninstall them, restart Fx then reinstall.

But make a backup of your profile folder first.

mzso commented 3 years ago

@xiaoxiaoflood commented on 2021. márc. 26. 04:29 CET:

Legacy addons almost never delete settings on uninstall, so you probably can uninstall them, restart Fx then reinstall.

But make a backup of your profile folder first.

I see. Well, I managed to do it. Though for one of them I don't have the xpi. Do you know where the permanently disabled state is stored?

xiaoxiaoflood commented 3 years ago

Do you know where the permanently disabled state is stored?

extensions.json in profile folder. If the toggle switch is not available in about:addons, you are probably looking for "appDisabled":true in each disabled legacy addon. With Fx closed, change it to false, then the toggle switch will reappear if you have fixed what caused the issue.

mzso commented 3 years ago

@xiaoxiaoflood commented on 2021. márc. 26. 14:09 CET:

Do you know where the permanently disabled state is stored?

extensions.json in profile folder. If the toggle switch is not available in about:addons, you are probably looking for "appDisabled":true in each disabled legacy addon. With Fx closed, change it to false, then the toggle switch will reappear if you have fixed what caused the issue.

Thanks!

xiaoxiaoflood commented 3 years ago

Closing this one because I guess your problem wasn't a bug caused by scripts/extensions in this repo. If you think otherwise and know the steps to reproduce the issue, please post it here and I'll reopen this.