User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:188.8.131.52) Gecko/20060728 Firefox/184.108.40.206 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:220.127.116.11) Gecko/20060728 Firefox/18.104.22.168 When you integrate an extension (.xpi) in your package and then install your package in firefox it shows an error : "Firefox can't install this element because the chrome registry failed" (roughly translated from french) At the restart : * Your package isn't installed * All other extension are disabled Reproducible: Always Steps to Reproduce: 1. install cck wizard (1.0.3) globally 2. create your configuration package (cck.config in additional information) 3. install your package in firefox (globally or in the profile) Actual Results: * Error message at the package installation * All installed extensions are disabled Expected Results: * install the config package (including the bundled extension) * let the other extensions actived ;-) cck.config email@example.com name=Test Bundled version=0.1 description=Test for extension integration creator=me homepageURL=http://www.mycompany.com updateURL=http://www.mycompany.com/update.rdf filename=testBundled OrganizationName=mycompany HomePageURL=http://www.mycompany.com CompanyName=Mozilla Firefox: My Company DefaultSearchEngine=(use the browser default) BundlePath1=C:\TEMP\sage-1.3.6-fx+mz.xpi ToolbarLocation=Last BookmarkLocation=Last I've tried other extensions In C:\program files\mozilla firefox\extensions There's a directory firstname.lastname@example.org instaead of email@example.com It contains the content of C:\TEMP\package cck.xpi install.rdf sage-1.3.6-fx+mz.xpi instead of expected files (all is good without an extension bundled in). Delete this directory to repair firefox and previuosly installed extension.
I tried with your CCK.config as posted and sage and it worked for me. What version of Firefox were you trying to install this extension into? Did you try with this exact cck.config? Or were you attempting to create a copy of your "official" cck.config? Also, you say "nstall your package in firefox (globally or in the profile)" Did you do this simply by opening the XPI in Firefox? You wouldn't get a choice between global or profile. Thanks! I want to get this figured out.
(In reply to comment #1) > What version of Firefox were you trying to install this extension into? Firefox 22.214.171.124 fr > Did you try with this exact cck.config? Or were you attempting to create a copy > of your "official" cck.config? I have tried this config, create a minimal config and test it on my firefox. My "official" config is more complex and I didn't want "side effects". > Also, you say "nstall your package in firefox (globally or in the profile)" > Did you do this simply by opening the XPI in Firefox? You wouldn't get a choice > between global or profile. I've tried both with -install-global-config flag in command line and dropping the .xpi in my Fx window.
> I've tried both with -install-global-config flag :-[ I meant -install-global-extension of course.
it appears that install-global-extension doesn't support multipackage XPIs. I was able to install if I explicitly opened the XPI in the URL bar or if I dragged drop to the browser. What I see in those cases is the extension manager opening up and the two extensions showing up as being installed upon reboot.
(In reply to comment #4) > I was able to install if I explicitly opened the XPI in the URL bar or if I > dragged drop to the browser. Same for me , retested my testBunbled.xpi including Sage in my profile (drag and drop) and the these two were installed and both work. I think I'have made a wrong operation with my profile test :-[ You change the resolution to INVALID ? WONTFIX ? It's good to know anyway.
Yes, this is good information to have if we see the global extension problem again. Thanks!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → INVALID
(In reply to comment #6) > Yes, this is good information to have if we see the global extension problem > again. I think it takes place in the FAQ and most important in cckWizard.dtd <!ENTITY customizeBundles.warning ... > That actually states "If you add extensions and/or themes to your CCK ... You must install through the browser *or use the -install-global-extension mechanism*"
You need to log in before you can comment on or make changes to this bug.