This forum is a discussion about improving the "Cannot remove an add-on (extension or theme)" article. If you'd like to participate, please register.

If you need help with Firefox, please ask a question.

"Uninstalling manually" needs update for fx4 ... and for Fx40: see comment 10-14-2015

  • 2 Replies
  • Last reply by AliceWyman
  1. AliceWyman 5146 posts
    Report Abuse

    I approved an update by John99 today since it improves the article but other updates are needed. Copied from John99's post: /en-US/kb/Cannot%20uninstall%20an%20a.../1681
    Quote:


    Firefox 3.5 is no longer supported. Current version even in FX5 version is displaying instructions relating to FX3.5 & 3.6, apparently due to change whereby add-ons are stored zipped. The article will need modifying, probably by use of tags and for, I have made a simple edit at least it should be a move in the right direction.


    Ref:

    Starting in Firefox 4 , XPI files are no longer unpacked when extensions are installed. Instead, the XPI itself is placed in the extensions directory, and files are loaded directly out of the package.

    I approved an update by John99 today since it improves the article but other updates are needed. Copied from John99's post: [/en-US/kb/Cannot%20uninstall%20an%20add-on/discuss/1681]<br> '''Quote:'''<br> ----- ''Firefox 3.5 is no longer supported. Current version even in FX5 version is displaying instructions relating to FX3.5 & 3.6, apparently due to change whereby add-ons are stored zipped. The article will need modifying, probably by use of tags and for, I have made a simple edit at least it should be a move in the right direction. '' ----- Ref: *https://developer.mozilla.org/en/Extensions/Updating_extensions_for_Firefox_4 *https://developer.mozilla.org/en/extension_packaging Starting in Firefox 4 , XPI files are no longer unpacked when extensions are installed. Instead, the XPI itself is placed in the extensions directory, and files are loaded directly out of the package.
    Modified by AliceWyman on
  2. Doyster 0 posts
    Report Abuse

    One update need for fx40+* relates to manual removal of extensions that are unlisted in the browser/extension folder.

    • Previously noted in this post

    https://support.mozilla.org/en-US/kb/cannot-remove-add-on-extension-or-theme/discuss/2080

    For these, user can ID the string as documented in the KB. Then, after exiting Fx, search for that string in the Win registry using RegEdit. Then delete the string. Registry location is typically: HkeyLM/Software/Mozilla/Firefox/Extensions

    Globally installed extensions Applicable here as well. However, the cited MDN article* is of little use to fx users seeking to remove such incompatible extensions from the listing within fx.

    • This one

    https://developer.mozilla.org/en-US/Add-ons/Installing_extensions

    One example -- globally installed [prior versions] Virtual Account Numbers (VAN) distributed by CitiCorp/Citibank (Citi) based on code/app developed by Orbiscom. Citi has announced a new VAN version will be released ~18 Oct 16. Even if this new VAN version auto-installs correctly in fx40-stream, coming fx releases will likely render this VAN extension incompatbile (prior experience). VAN updates through Citi are rarely issued.

    One update need for fx40+* relates to manual removal of extensions that are unlisted in the browser/extension folder. *Previously noted in this post https://support.mozilla.org/en-US/kb/cannot-remove-add-on-extension-or-theme/discuss/2080 For these, user can ID the string as documented in the KB. Then, after exiting Fx, search for that string in the Win registry using RegEdit. Then delete the string. Registry location is typically: HkeyLM/Software/Mozilla/Firefox/Extensions Globally installed extensions Applicable here as well. However, the cited MDN article* is of little use to fx users seeking to remove such incompatible extensions from the listing within fx. *This one https://developer.mozilla.org/en-US/Add-ons/Installing_extensions One example -- globally installed [prior versions] Virtual Account Numbers (VAN) distributed by CitiCorp/Citibank (Citi) based on code/app developed by Orbiscom. Citi has announced a new VAN version will be released ~18 Oct 16. Even if this new VAN version auto-installs correctly in fx40-stream, coming fx releases will likely render this VAN extension incompatbile (prior experience). VAN updates through Citi are rarely issued.
  3. AliceWyman 5146 posts
    Report Abuse

    I added this to the "Need changes" list for review and to update as needed.

    I added this to the "Need changes" list for review and to update as needed.