MozillaZine

Talk:Uninstalling extensions - SeaMonkey

From MozillaZine Knowledge Base

Request for comments

I put together this article after the Uninstalling extensions article was revised, since all the Mozilla Suite and SeaMonkey-related content had been removed. I started to clean up the manual uninstall instructions but decided to replace those instructions with the suggestion to delete the profile folder "chrome" folder. Here is what I was going to add before I decided that no one was ever going to use it and, besides, the formatting looks like it was from an older wiki version and bled through. Here is the section that I was in the process of revising but decided to remove from the article: Alice 23:14, 8 June 2007 (UTC)

Just so you know, I removed the Mozilla Suite and SeaMonkey related info because that article seemed geared to Firefox and Thunderbird only. It didn't even have a Mozilla Suite category applied to it.--Np 23:31, 8 June 2007 (UTC)
It's fine. I was thinking of doing something with that article for SeaMonkey anyway. The Mozilla Suite : FAQs article links to it (I just changed that link) and I've seen people on the SeaMonkey forums link to it, even though it's not categorized as a Mozilla Suite article. Alice 23:49, 8 June 2007 (UTC)

Again, here is the section I left out of the new article, if anyone is interested in fixing it up and adding it. Alice 23:49, 8 June 2007 (UTC) ===Removing individual profile-installed extensions===

This procedure is not recommended due to the risks and tedium involved and should only be attempted by advanced users. 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 <profile folder>/chrome/chrome.rdf file.

  1. Exit Mozilla Suite/SeaMonkey and make sure it is not listed in your process list.
  2. Browse to your profile folder.
  3. Remove the <profile folder>/chrome/[shortname].jar file.
  4. Return to the profile folder and delete the compreg.dat and xul.mfl file. (The latter file may be called something slightly different, such as XUL.mfasl ). These files will be recreated when the browser restarts.
  5. Edit the files in <profile folder>/chrome/overlayinfo. Do a text search to find those that contain [shortname] inside them and remove all entries which look like this:
    <RDF:li>chrome://[shortname]/[path to file]</RDF:li>
  6. Edit the <profile folder>/chrome/chrome.rdf file. Remove all entries referencing the extension. See the list of possible entries.
  7. Remove extension-related preferences from the user.js file and prefs.js file.

Some extensions also create extra files on your hard drive. For example, Menu Editor stores its data in a menuedit.rdf file in your profile folder and TBE uses tabextensions.js. You might want to remove those too.

====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>

If anyone wants to improve this article or tell me how to fix it up, please do. Alice 23:14, 8 June 2007 (UTC)