Extension web page Javascript install trigger
Sailfish
install.rdf/chrome.manifest installation files over the older
install.js/contents.rdf installation files. However, it now seems like
the install trigger javascript function now returns a "-207 Invalid
Install Package" error. Is there a new javascript function that is
needed now with the new installation file format?
TIA
--
Sailfish - Netscape/Mozilla Champion
Netscape/Mozilla Tips: http://www.ufaq.org/ , http://ilias.ca/
Rare Mozilla Stuff: http://www.projectit.com/
CatThief
> I recently converted an old extension of mine to now use the
> install.rdf/chrome.manifest installation files over the older
> install.js/contents.rdf installation files. However, it now seems like
> the install trigger javascript function now returns a "-207 Invalid
> Install Package" error. Is there a new javascript function that is
> needed now with the new installation file format?
>
> TIA
>
Hi Pat,
I'm assuming the install trigger javascript function is part of a link
you have on your web site?
As long as the install script code is correct, the problem is most
likely a result of entries inside the chrome.manifest that don't match
the path to your files. Can you post the contents of that file as well
as a short description of your extension's directory structure?
--
Regards,
CatThief
To reply privately, please PM me at MozillaZine
http://forums.mozillazine.org/ucp.php?i=pm&mode=compose&u=25774
Sailfish
> Sailfish wrote the following on 02-12-2010 9:26 PM:
>
> I'm assuming the install trigger javascript function is part of a link
> you have on your web site?
>
simply a link to the XPI file on my server and this had worked fine on
Fx up to 3.5. However, with 3.6 I started getting the -207 errors. The
thing that's odd is that I can DnD the XPI from my desktop and it
installs swimmingly. I can also do a local install it from the add-ons
manager and, again, it install fine. Additionally, I've uploaded the
file to AMO where it currently resides in the sandbox but it installs
fine from there, too.
> As long as the install script code is correct, the problem is most
> likely a result of entries inside the chrome.manifest that don't match
> the path to your files. Can you post the contents of that file as well
> as a short description of your extension's directory structure?
>
Sure.
chrome.manifest
---------------
content inspectorwidget chrome/content/inspectorwidget/
overlay chrome://browser/content/browser.xul
chrome://inspectorwidget/content/inspectorwidget_fx.xul
overlay chrome://browser/content/browser.xul
chrome://inspectorwidget/content/inspectthisOverlay.xul
overlay chrome://navigator/content/navigator.xul
chrome://inspectorwidget/content/inspectorwidget_mz.xul
overlay chrome://navigator/content/navigator.xul
chrome://inspectorwidget/content/inspectthisOverlay_mz.xul
overlay chrome://messenger/content/mailWindowOverlay.xul
chrome://inspectorwidget/content/inspectorwidget_tb.xul
overlay chrome://calendar/content/calendar.xul
chrome://inspectorwidget/content/inspectorwidget_sb.xul
locale inspectorwidget en-US chrome/locale/en-US/inspectorwidget/
locale inspectorwidget fr-FR chrome/locale/en-US/inspectorwidget/
skin inspectorwidget classic/1.0 chrome/skin/classic/inspectorwidget/
style chrome://global/content/customizeToolbar.xul
chrome://inspectorwidget/skin/inspectorwidget.css
style chrome://browser/content/browser.xul
chrome://inspectorwidget/skin/inspectorwidget.css
style chrome://navigator/content/navigatorOverlay.xul
chrome://inspectorwidget/skin/inspectorwidget_mz.css
style chrome://messenger/content/mailWindowOverlay.xul
chrome://inspectorwidget/skin/inspectorwidget_tb.css
style chrome://calendar/content/calendar.xul
chrome://inspectorwidget/skin/inspectorwidget_sb.css
skin inspectorwidget aluminumalloy/1.0
chrome/skin/aluminumalloy/inspectorwidget/
style chrome://global/content/customizeToolbar.xul
chrome://inspectorwidget/skin/inspectorwidget.css
style chrome://browser/content/browser.xul
chrome://inspectorwidget/skin/inspectorwidget.css
style chrome://navigator/content/navigatorOverlay.xul
chrome://inspectorwidget/skin/inspectorwidget_mz.css
style chrome://messenger/content/mailWindowOverlay.xul
chrome://inspectorwidget/skin/inspectorwidget_tb.css
style chrome://calendar/content/calendar.xul
chrome://inspectorwidget/skin/inspectorwidget_sb.css
skin inspectorwidget skypilot/1.0 chrome/skin/skypilot/inspectorwidget/
style chrome://global/content/customizeToolbar.xul
chrome://inspectorwidget/skin/inspectorwidget.css
style chrome://browser/content/browser.xul
chrome://inspectorwidget/skin/inspectorwidget.css
style chrome://navigator/content/navigatorOverlay.xul
chrome://inspectorwidget/skin/inspectorwidget_mz.css
style chrome://messenger/content/mailWindowOverlay.xul
chrome://inspectorwidget/skin/inspectorwidget_tb.css
style chrome://calendar/content/calendar.xul
chrome://inspectorwidget/skin/inspectorwidget_sb.css
skin inspectorwidget toyfactory/1.0
chrome/skin/toyfactory/inspectorwidget/
style chrome://global/content/customizeToolbar.xul
chrome://inspectorwidget/skin/inspectorwidget.css
style chrome://browser/content/browser.xul
chrome://inspectorwidget/skin/inspectorwidget.css
style chrome://navigator/content/navigatorOverlay.xul
chrome://inspectorwidget/skin/inspectorwidget_mz.css
style chrome://messenger/content/mailWindowOverlay.xul
chrome://inspectorwidget/skin/inspectorwidget_tb.css
style chrome://calendar/content/calendar.xul
chrome://inspectorwidget/skin/inspectorwidget_sb.css
Directory Tree
--------------
content
inspectorwidget
inspectomatic.js
inspectorwidget.js
inspectorwidget_fx.xul
inspectorwidget_mz.xul
inspectorwidget_sb.xul
inspectorwidget_tb.xul
inspectthis.js
inspectthisOverlay.xul
inspectthisOverlay_mz.xul
locale
en-US
inspectorwidget
inspectorwidget.dtd
fr-FR
inspectorwidget
inspectorwidget.dtd
skin
aluminumalloy
inspectorwidget
inspect-hov.png
inspect-small-hov.png
inspect-small.png
inspect.png
inspectorwidget.css
inspectorwidget_mz.css
inspectorwidget_sb.css
inspectorwidget_tb.css
classic
inspectorwidget
inspect-hov.png
inspect-small-hov.png
inspect-small.png
inspect.png
inspectorwidget.css
inspectorwidget_mz.css
inspectorwidget_sb.css
inspectorwidget_tb.css
skypilot
inspectorwidget
DOMInspector-act.png
DOMInspector-dis.png
DOMInspector-hov.png
DOMInspector-small-act.png
DOMInspector-small-dis.png
DOMInspector-small-hov.png
DOMInspector-small.png
DOMInspector.png
inspect.png
inspectorwidget.css
inspectorwidget_mz.css
inspectorwidget_sb.css
inspectorwidget_tb.css
toyfactory
inspectorwidget
DOMInspector-small.png
DOMInspector.png
inspect.png
inspectorwidget.css
inspectorwidget_mz.css
inspectorwidget_sb.css
inspectorwidget_tb.css
Sailfish
>
> I'm assuming the install trigger javascript function is part of a link
> you have on your web site?
>
simply a link to the XPI file on my server and this had worked fine on
Fx up to 3.5. However, with 3.6 I started getting the -207 errors. The
thing that's odd is that I can DnD the XPI from my desktop and it
installs swimmingly. I can also do a local install it from the add-ons
manager and, again, it install fine. Additionally, I've uploaded the
file to AMO where it currently resides in the sandbox but it installs
fine from there, too.
> As long as the install script code is correct, the problem is most
> likely a result of entries inside the chrome.manifest that don't match
> the path to your files. Can you post the contents of that file as well
> as a short description of your extension's directory structure?
>
Sure.
locale inspectorwidget en-US chrome/locale/en-US/inspectorwidget/
locale inspectorwidget fr-FR chrome/locale/en-US/inspectorwidget/
Directory Tree
--------------
locale
en-US
inspectorwidget
inspectorwidget.dtd
fr-FR
inspectorwidget
inspectorwidget.dtd
Sailfish
>
> I'm assuming the install trigger javascript function is part of a link
> you have on your web site?
>
simply a link to the XPI file on my server and this had worked fine on
Fx up to 3.5. However, with 3.6 I started getting the -207 errors. The
thing that's odd is that I can DnD the XPI from my desktop and it
installs swimmingly. I can also do a local install it from the add-ons
manager and, again, it install fine. Additionally, I've uploaded the
file to AMO where it currently resides in the sandbox but it installs
fine from there, too.
> As long as the install script code is correct, the problem is most
> likely a result of entries inside the chrome.manifest that don't match
> the path to your files. Can you post the contents of that file as well
> as a short description of your extension's directory structure?
>
Sure.
locale inspectorwidget en-US chrome/locale/en-US/inspectorwidget/
locale inspectorwidget fr-FR chrome/locale/en-US/inspectorwidget/
Directory Tree
--------------
locale
en-US
inspectorwidget
inspectorwidget.dtd
fr-FR
inspectorwidget
inspectorwidget.dtd
Sailfish
> On 2/13/2010 5:53 PM, CatThief wrote:
>> Sailfish wrote the following on 02-12-2010 9:26 PM:
>>
>> I'm assuming the install trigger javascript function is part of a link
>> you have on your web site?
>>
> Actually, before converting over to the new chrome.manifest it was
> simply a link to the XPI file on my server and this had worked fine on
> Fx up to 3.5. However, with 3.6 I started getting the -207 errors. The
> thing that's odd is that I can DnD the XPI from my desktop and it
> installs swimmingly. I can also do a local install it from the add-ons
> manager and, again, it install fine. Additionally, I've uploaded the
> file to AMO where it currently resides in the sandbox but it installs
> fine from there, too.
>
issue? After all, all of the successful steps involved either a local
install or an install from AMO's server and the only one that fails is
my server.
This leads me to believe that maybe Firefox has changed as to what it
expects when being served an xpi file. I've added the following line in
my server's .htaccess file:
AddType application/x-xpinstall .xpi
but am now wondering if either this has changed or if I need to do
something differently?
Any ideas?
Sailfish
fine! I hadn't changed anything on my server, extension or Firefox???
Gremlins?
CatThief
> Very odd. I just tried the download link again and now it's installing
> fine! I hadn't changed anything on my server, extension or Firefox???
>
> Gremlins?
Gremlins indeed. :) I'm glad to hear everything is working the way it
should.
CatThief
> On 2/14/2010 9:37 PM, CatThief wrote:
>> Sailfish wrote the following on 02-14-2010 3:09 AM:
>>
>>> Very odd. I just tried the download link again and now it's installing
>>> fine! I hadn't changed anything on my server, extension or Firefox???
>>>
>>> Gremlins?
>>
>> Gremlins indeed. :) I'm glad to hear everything is working the way it
>> should.
>>
> I'm not sure if everything is settled, though, since I hadn't been able
> to isolate what the problem actually was. I'm going to continue to test
> it over the next week or so to ensure that it doesn't resurface.
>
> Thanks for your offer to help.
>
I would, though, safely rule out any issues with the chrome.manifest.
Sailfish
> Sailfish wrote the following on 02-15-2010 3:48 AM:
>
>> On 2/14/2010 9:37 PM, CatThief wrote:
>>> Sailfish wrote the following on 02-14-2010 3:09 AM:
>>>
>>>> Very odd. I just tried the download link again and now it's installing
>>>> fine! I hadn't changed anything on my server, extension or Firefox???
>>>>
>>>> Gremlins?
>>>
>>> Gremlins indeed. :) I'm glad to hear everything is working the way it
>>> should.
>>>
>> I'm not sure if everything is settled, though, since I hadn't been able
>> to isolate what the problem actually was. I'm going to continue to test
>> it over the next week or so to ensure that it doesn't resurface.
>>
>> Thanks for your offer to help.
>>
>
> I would, though, safely rule out any issues with the chrome.manifest.
>