Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

why do my add-ons keep getting disabled?

  • 3 件の返信
  • 0 人がこの問題に困っています
  • 7 回表示
  • 最後の返信者: cor-el

more options

why do my add-ons keep getting disabled?

ff keeps disabling add-ons that i have used for years and even keep a v. 5 to use the older add-ons and use the latest ff developer to use w/ more modern websites. ff even disables add-ons that worked perfectly well in ff developer and does not even give me the opportunity to re-enable them like i could before.

is there any way to force my old version to let ME decide what i want disabled/enabled?

why do my add-ons keep getting disabled? ff keeps disabling add-ons that i have used for years and even keep a v. 5 to use the older add-ons and use the latest ff developer to use w/ more modern websites. ff even disables add-ons that worked perfectly well in ff developer and does not even give me the opportunity to re-enable them like i could before. '''''is there any way to force my old version to let ME decide what i want disabled/enabled? '''''

すべての返信 (3)

more options

Extensions can become disabled if the path of the profile folder changes. Try clearing extensions.databaseSchema in about:config then restart the browser.

more options

thanks for the suggestion!

however, when i followed your instructions, all i saw was "34" and i have no idea what that means. tried putting i a 0, but that was disallowed, so i left it at 34. i had assumed there would be a list of some sort and i did not see way to "clearing" it.

how do i clear it?

thanks, wolfgang

more options

What meant is to click the trashcan at the far right on the extensions.databaseSchema line to reset the pref and let Firefox create a new pref. In my Firefox 123.0.1 version the pref is 35, but you shouldn't change this pref to another number.

The Developer Edition version uses a dev-edition-default profile while the release update channel uses default-release (i.e. default-<update_channel>; DE is an exception as it predates the dedicated profile conception).