Closed Bug 338481 Opened 19 years ago Closed 19 years ago

CCK created w/ wizard does not install

Categories

(Other Applications :: CCK, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: schapin, Assigned: mkaply)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.0.1) Gecko/20060124 Firefox/1.5.0.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.0.1) Gecko/20060124 Firefox/1.5.0.1 I downloaded the CCK extension and walked through the wizard. The only thing I'm trying to set is the Auto proxy configuration URL. The wizard finishes and generates: -rw-rw-r-- 1 schapin user 121 May 18 13:49 cck.config drwxrwxr-x 3 schapin user 4096 May 18 13:49 jar drwxrwxr-x 5 schapin user 4096 May 18 13:49 xpi drwxrwxr-x 47 schapin user 8192 May 18 13:49 . -rw-r--r-- 1 schapin user 8869 May 18 13:49 dwa-cck.xpi cck.config looks correct: cck.config id=dwa-cck@dreamworks.com filename=dwa-cck OrganizationName=dwa ProxyType=2 autoproxyurl=http://proxyconfig/setproxy.pac I then hop onto another system and run the following as root: firefox -install-global-extension dwa-cck.xpi ... which appears to install the bits correctly: /usr/local/lib/firefox/extensions/dwa-cck@dreamworks.com -rw-r--r-- 1 root root 121 May 18 13:49 cck.config drwxr-xr-x 2 root root 4096 May 18 13:50 chrome -rw-r--r-- 1 root root 221 May 18 13:49 chrome.manifest drwxr-xr-x 2 root root 4096 May 18 13:50 components drwxr-xr-x 3 root root 4096 May 18 13:50 defaults -rw-r--r-- 1 root root 2907 May 18 13:49 install.js -rw-r--r-- 1 root root 635 May 18 13:49 install.rdf ...but, when I then launch Firefox as root (who has no ~/.mozilla/firefox directory), the proxy settings is NOT applied and I don't see the extention in the Tools > Extensions window. What am I doing wrong? Reproducible: Always Steps to Reproduce: See above. Actual Results: No proxy is set, and the extension is not installed. Expected Results: Install the extension and set the proxy.
I believe the problem is that you have not specified a version and a name on the same page where you put the ID of the extension. The CCK is supposed to not allow this, but something isn't working....
I don't know how I even wrote the code in 1.0.1. That was just bad. I'll update ASAP Argh.
Fix checked in
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Thanks!! Adding the version and name got things working for me.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: