MozillaZine

Dev : Extensions : Extension does not install

From MozillaZine Knowledge Base

(Difference between revisions)
Revision as of 13:12, 30 November 2004
Asqueella (Talk | contribs)

<-- Previous diff
Revision as of 01:28, 19 December 2004
Asqueella (Talk | contribs)

Next diff -->
Line 1: Line 1:
 +{{extdev}}
 +
==Introduction== ==Introduction==
This page describes possible reasons for extension installation problems. Intended audience is '''extension developers''', not end-users. If you have problems with installing extensions in general, you should search somewhere else. This page describes possible reasons for extension installation problems. Intended audience is '''extension developers''', not end-users. If you have problems with installing extensions in general, you should search somewhere else.
Line 42: Line 44:
*<b>Bad target application</b>. ''That was a problem with early aviary builds''. *<b>Bad target application</b>. ''That was a problem with early aviary builds''.
*Another possible cause is [http://bugzilla.mozilla.org/show_bug.cgi?id=252543 bug 252543]. Triggers when you have components in myext.xpi/components/ that overwrite existing files in components/ (often when upgrading). The bug is fixed for 0.10, possible workaround for 0.9.x is use new names for files in components/ for each new release. *Another possible cause is [http://bugzilla.mozilla.org/show_bug.cgi?id=252543 bug 252543]. Triggers when you have components in myext.xpi/components/ that overwrite existing files in components/ (often when upgrading). The bug is fixed for 0.10, possible workaround for 0.9.x is use new names for files in components/ for each new release.
 +
 +[[Category:Development]]

Revision as of 01:28, 19 December 2004

This page is part of the extension development documentation project.

Ask your questions in MozillaZine Forums. Also try browsing example code.

Note: development documentation is in process of being moved to Mozilla Development Center (MDC).

Contents

Introduction

This page describes possible reasons for extension installation problems. Intended audience is extension developers, not end-users. If you have problems with installing extensions in general, you should search somewhere else.

If you are extension developer, you can't get your (recently packaged) extension installed and suspect the problem is with your extension, this is the right page.

Covered applications are Firefox and Thunderbird.

Possible causes

This item will be installed...

This problem is almost always caused by mistakes in your install.rdf. Take a look at that link to see an example of good install.rdf.

Some known causes include:

  • Malformed XML/RDF in install.rdf.. Make sure your install.rdf is valid XML by renaming it to install.xml and opening in Firefox. If it doesn't show any XML errors, you're ok. A good idea is to make sure your install.rdf is well-formed RDF too. There's an RDF validator at w3.org (it displays some warnings even for correct install.rdf, but that's ok).
  • Wrong information in install.rdf. Triple-check your install.rdf. The following mistakes are likely to cause the "will be installed" bug:
      <li>Typos in <em:file> tag. For example your jar file is named differently or placed in wrong directory. You may also have wrong directory structure. Another known problem is forgotten slash after directory name in <em:package> <em:locale> or <em:skin>. That is when you have <em:package>content/myext</em:package> instead of <em:package>content/myext/</em:package>, the Extension manager will not install the extension. </li>
  • Mixed case in extension's package name. Use lower case for chrome package name. (bug 257997, bug 132183). Symptoms: Firefox is completely hosed or doesn't open windows that belong to your extension.

Other

Other possible causes are listed here:

  • Not ZIP archive. You might have packed your extension in a fancy format that the EM cannot understand. You should use simple ZIP format for both XPI and JAR files.
  • Bad contents.rdf.

Pre-1.0 releases

  • Bad target application. That was a problem with early aviary builds.
  • Another possible cause is bug 252543. Triggers when you have components in myext.xpi/components/ that overwrite existing files in components/ (often when upgrading). The bug is fixed for 0.10, possible workaround for 0.9.x is use new names for files in components/ for each new release.