Talk:Uninstalling add-ons

From MozillaZine Knowledge Base

Hao2lian: overlayinfo and chrome.rdf changes are not optional. extensions.rdf is optional, but if you don't change that, the extension would still be listed in the EM. Not sure about components.ini/defaults.ini (bet you're not sure either). prefs.js/other files are optional, but I don't think we should create a separate section for them. I fixed these problems. Asqueella 09:16, 9 Jan 2005 (PST)



If I am incorrect in saying that themes are treated in the same way as extensions as far as the Extension Manager is concerned, then we need to change that example of a locked extension (currently the default theme).Mozcerize 03:26, 10 Jan 2005 (PST)

I am not sure how themes are treated by other parts of Firefox, but locked theme and locked extension are very similar. The problem is, there are no locked extensions in default install, so I added the theme example. Thought that the theme example is better than no example. Feel free to remove that if you think it is confusing. Asqueella 09:13, 10 Jan 2005 (PST)
I agree that an example is needed, and the default theme example is fine. The only question is whether there are subtle aspects of the manual uninstall procedure which are different for themes than for extensions.Mozcerize 16:41, 10 Jan 2005 (PST)

alternative fix for "...will be removed after...restart..."

I have found that another way to get rid of that message (for a single uninstall attempt). Once I get that message, I reinstall the extension (drag the downloaded xpi file to the extensions manager window). Once it finishes installing, I restart Firefox and the extension finally gets uninstalled.

Unlocking extensions

Okay, so to remove a locked extension I have to unlock it. That's nice to know. Any chance someone could actually consider explaining how, exactly, one might actually go about this mysterious act? The linked article contains nothing but some crap from some equally frustrated commentator, which is worse than useless.

Locked extensions--uninstalling

It would be nice if someone could explain exactly how to unlock a locked extension manager. However, a workaround, which I'm sure is NOT a great thing to do, is to install the latest beta version of Firefox, uninstall the extension you're having problems with, and then reinstall the current non-beta version of Firefox. Not pretty, but it works. The extension manager remains unlocked after reinstallation In the meantime, does anyone know how to unlock a locked extension manager? Please tell us.

Disabling Extensions

I wanted documents explaining what right-clicking an extension in Extension Manager and clicking "Disable" does.

This is what I think.

Disabling is the same as unistalling except for these differences:

  • The extension is not actually uninstalled, therefore it remains in the extensions folder.
  • Firefox does not know that extension exists, although Extension Manager does know.

Is this right? A "Disabling Extensions" page in the knowledge base would be helpful.

--Agent007bond 21:20, 24 February 2006 (UTC)

Global extensions

This article currently implies that global extensions for Firefox 1.5 live inside the default profile folder, and may be active even if a non-default profile is being currently used. I was not aware of that, but certainly the "traditional" place for global extensions is inside the extensions subfolder of the installation directory. This is true of 1.5 and 1.0.x. (See Installing extensions#Global_installation.) I believe this applies to all Moz apps. Also, as it stands, the article doesn't actually mention a global uninstallation procedure for Firefox 1.0.x and Thunderbird 0.8--1.0.x, and so I think we need to rewrite the section on global uninstallation for older versions to make it applicable to these apps too. (Currently it implies that the procedure described for the Mozilla Suite will also apply to them, but doesn't explicitly say so.)

Could somebody suggest how to uninstall global extensions installed into the installation directory of new Moz apps, and confirm that global extensions did not exist for Firefox 0.9, Thunderbird 0.7, and earlier (as implied in the article). Cheers --Mozcerize 21:08, 8 July 2006 (UTC) to uninstall global extensions installed into the installation directory of new Moz apps
I'll admit I know very little on this subject but can't you use the same procedure as manually uninstalling from the profile... remove the associated extensions subfolder for the particular extension? <snip> I agree that the section on manually uninstalling global extensions (covering Firefox 1.5 under "recent versions") as written, doesn't jive with the Installing extensions article and should be rewritten. <snip> Alice Wyman 16:32, 10 July 2006 (UTC)
Just wanted to add that I updated the section on uninstalling global extensions from "recent versions" (e.g. Firefox 1.5) the other day so that it refers to the "installation directory" now. Alice Wyman 13:41, 13 July 2006 (UTC)
... Also, as it stands, the article doesn't actually mention a global uninstallation procedure for Firefox 1.0.x and Thunderbird 0.8--1.0.x,
The section on "other versions" (e.g. Firefox 1.0.x) still needs to be updated. Alice Wyman 13:41, 13 July 2006 (UTC)

This is one ugly article! HAND, no offence intended... --FatJohn 02:50, 2 June 2006 (UTC)

If only there was some way you could make it prettier, or at least mark it as needing clean-up. Oh well. Thanks for the comment.--Np 04:11, 2 June 2006 (UTC)

Old stuff I took out

Check the source for a more nicely formatted version.--Np 21:12, 8 June 2007 (UTC)

* The extension is listed with a red "generic" icon, or is not listed at all. Older versions of Firefox (0.9 and below) and Thunderbird (0.7 and below) used an older version of the Extension Manager; the problematic extension was not packaged for the new Extension Manager. You'll have to uninstall it manually or use an extension uninstaller (see below). The general recommendation is to [[Profile Manager | create a new profile]] for Firefox or Thunderbird and only install repackaged extensions in it. ==Uninstaller extensions== These extensions are useful for [[Firefox]] (pre-0.9), [[Thunderbird]] (pre-0.7), and [[Mozilla Suite]] users. ''Do not use these extensions if you have the "This item will be uninstalled after you restart Firefox" message in the extension manager! Either [[Profile Manager | create a new profile]] or see the section below on performing a manual uninstall.'' *[ Extension Uninstaller] by [ Jeremy Gillick], an extension built from the ground up to uninstall extensions. ([ Discuss] this in the forums.) [ Mozilla Update] links: [] [] *Uninstaller (''discontinued'') by [ Chris Pederick]. An extension which also automates this task. ([ Discuss] this in the forums.) ==Uninstalling manually== You can uninstall extensions manually, but the procedures are different in recent versions (Firefox 1.5, Thunderbird 1.5, Sunbird 0.3) and in other versions of Mozilla applications (Firefox 1.0.x, Thunderbird 1.0.x, Sunbird 0.2, Mozilla Suite, SeaMonkey). ===Uninstalling in other versions=== These instructions apply to Firefox 1.0.x, Thunderbird 1.0.x, Sunbird 0.2, Mozilla Suite and SeaMonkey In these other versions, it is strongly recommended that you [[Profile Manager | create a new profile]] instead of uninstalling manually due to the risks and tedium involved in the manual procedure. It's a good idea to [[Profile backup | make backups of your profile folder]] before deleting or changing anything in case something goes wrong. ====Removing profile-installed extensions==== You'll need to know the internal "short name" of the extension you're uninstalling. You can find it by searching for the full name in the <tt><profile folder>/chrome/chrome.rdf</tt> file. These instructions do not apply to Firefox 1.5 and Thunderbird 1.5. <ol> <li>Exit the application (Firefox, Thunderbird, or Mozilla Suite) and make sure it is [[kill application | not listed in your process list]]. <li>Browse to your [[profile folder]]. <li>'''Mozilla Suite users''': Remove the <tt><profile folder>/chrome/[shortname].jar</tt> file.<br>'''All other users''': Remove the <tt><profile folder>/extensions/{extension-GUID}</tt> folder. You can find the [ GUID] for the unwanted extension by looking in the <tt><profile folder>/extensions/extensions.rdf</tt> file or by searching for the <tt>[shortname].jar</tt> file in your <tt>extensions</tt> folder. Make note of the GUID as it will be needed again later in this process. <li>Return to the profile folder and delete the <tt>compreg.dat</tt> and <tt>xul.mfl</tt> files. (The latter file may be called something slightly different, such as <tt>XUL.mfasl</tt>).) These files will be recreated when the browser restarts. <li>Edit the files in <tt><profile folder>/chrome/overlayinfo</tt>. Do a text search to find those that contain [shortname] inside them and remove all entries which look like this: <pre><RDF:li>chrome://[shortname]/[path to file]</RDF:li></pre> <li>Edit the <tt><profile folder>/chrome/chrome.rdf</tt> file. Remove all entries referencing the extension. See [[Uninstalling_extensions#The_list_of_possible_chrome.rdf_entries|the list of possible entries]]. <li>'''Firefox and Thunderbird users''': Edit <tt><profile folder>/extensions/extensions.rdf</tt>. Remove the entry that looks like this: <pre><RDF:Description RDF:about="urn:mozilla:extension:{[GUID]}" em:name="QuickNote" [more info]> [more info] <em:targetApplication RDF:resource="rdf:[junk]"/> </RDF:Description></pre> <li>'''Firefox and Thunderbird users''': Return to the profile folder and edit <tt>components.ini</tt> and <tt>defaults.ini</tt> and remove any lines which contain the GUID of the extension being uninstalled. <li>Remove extension-related preferences from the [[user.js file]] and prefs.js. </ol> <p> Some extensions also create extra files on your hard drive. For example, [ Menu Editor] stores its data in a <tt>menuedit.rdf</tt> file in your [[profile folder]] and [ TBE] uses <tt>tabextensions.js</tt>. You might want to remove those too. </p> =====The list of possible chrome.rdf entries===== <RDF:li RDF:resource="urn:mozilla:package:[shortname]"/> <RDF:li RDF:resource="urn:mozilla:locale:[locale]:[shortname]"/> <RDF:li RDF:resource="urn:mozilla:skin:[skin]:[shortname]"/> <RDF:Description RDF:about="urn:mozilla:["locale"/"skin"]:[locale/skin]:[shortname]" c:baseURL="[path]"> <c:package RDF:resource="urn:mozilla:package:[shortname]"/> </RDF:Description> <RDF:Description RDF:about="urn:mozilla:package:[shortname]" c:baseURL="[path]" [a lot more info]> <c:selectedLocale RDF:resource="urn:mozilla:locale:[locale]:[shortname]"/> <c:selectedSkin RDF:resource="urn:mozilla:skin:[skin]:[shortname]"/> </RDF:Description> ====Removing a globally-installed extension==== Firefox 0.9+ and Thunderbird 0.7+, by default, install their extensions into the profile folder, so this section will not apply to those users. Mozilla Suite users are still able to install their extensions globally (that is, in their Mozilla Suite program installation directory and not their profile folder). # Exit Mozilla Suite. # Browse to the "chrome" subfolder of your Mozilla Suite [[installation directory]] (usually <tt>C:\Program Files\\Mozilla\chrome</tt> for Windows users; for Mac users, Ctrl-Click the Mozilla Application folder package and select "Show Package Contents" and browse to <tt> /Applications/</tt>). # Modify <tt>chrome.rdf</tt> and the files in your "overlay" folder as described above in the "Optional steps" section. # Delete <tt>[extensionname].jar</tt> (or the [extensionname] directory if it has one). # Remove every line with a reference to the extension's name from <tt>installed-chrome.txt</tt>. Usually there are up to three such lines corresponding to content, locale and skin. # A few extensions might use additional files. [[Commonly_Used_Words#Extensions|TBE]], for example, creates the file <tt>tabextensions.js</tt> in <tt><application folder>/defaults/pref/</tt> in which to store its defaults. Search through your installation directory for such files and delete them.