Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Will I get my Delicious bookmarks back if I go back to an earlier Firefox version?

more options

With the new version firefox it seems I have lost my delicious sidebar. The add on seems to be blocked. How do I restore the delicious sidebar to my firefox screen?

With the new version firefox it seems I have lost my delicious sidebar. The add on seems to be blocked. How do I restore the delicious sidebar to my firefox screen?

所有回覆 (2)

more options

hi Ken-T, please get in contact with the addon's vendor to inquire how they'll make available a verified version of their addon in firefox (which is required in current versions of firefox and has been communicated to developers for months). thank you!

more options

If your Delicious Bookmarks 2.3.4 extension is disabled / inactive due to that extension not being "verified" / not being "signed" ... see this KB article.

https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox#w_what-can-i-do-if-firefox-disables-an-installed-unsigned-add-on

Override add-on signing (advanced users): You can override this setting by changing the xpinstall.signatures.required preference to false in the Firefox Configuration Editor (about:config typed in the URL bar). Support is not available for any changes made with the Configuration Editor so please do this at your own risk.

Note: That pref will be gone in Firefox 44 (Release slated for Jan 26. 2016) so user's of currently un-signed extensions should contact the developers of those extensions and prod them into getting their act together & get their extensions signed by Mozilla. Otherwise the users of those extensions will be SOL come the release of Firefox 44. Mozilla has already pushed back the version in which this new security feature was to be enabled from Firefox 40 to 44. I doubt if there will be any further reprieve.