- Updated for new Firefox 3.6 proxy panel
- Two CCKs can now coexist (Company Identifiers must be unique to each CCK)
- Bundling XPIs and JARs no longer uses XPI bundles – they are explicitly installed upon first run of the CCK (please test this if you bundle multple XPIs)
- All translated CCK Wizards should now be working
- First run screen added to CCK Wizard install
- A few bugs fixed
Some other items of note:
As I mentioned before, I’ve moved CCK Wizard development to Google Code. Please feel free to open up bugs there.
Going forward, I’m going to add the ability to do more locking down of functionality in Firefox. If you have specific needs, please open bugs in Google Code.
To close this post out, I want to answer a couple questions about CCK Wizard that are asked a lot.
What is the right way to install the CCK?
There are multiple ways the CCK can be installed based on your needs. I’ll go through all those ways.
Standard install – The XPI that is created by the CCK Wizard is just a Firefox extension, so as such it can be placed on a web page and users can simply click to install. You can get more information on how to do this from the Mozilla developer center.
In the Firefox directory – Extensions can be installed directly into the Firefox directory. Inside of the directory where the Firefox executable is located, there is a directory called extensions. Inside this directory, you can create a directory with the same ID as your CCK and then unzip your CCK into that directory. This is the only location where you can hide the add-on.
Globally – There are designated locations in different operating systems where extensions can be installed and they are picked up by Firefox. You can get more information on these locations at the Mozilla Developer Center. This involves unzipping the CCK package in a specific location on the users hard drive into a directory that is named the same as the ID of the CCK. Using this method, you can manage the CCK package centrally and the user cannot uninstall the CCK from Firefox.
Via the Windows Registry – If you are on Windows, extensions can be installed via the Windows registry. This is documented at the Mozilla Developer Center. This involves unzipping the CCK package that you created to a central location and then adding a registry key that tells Firefox where to find the CCK. Using this method, you can manage the CCK package centrally and the user cannot uninstall the CCK from Firefox.
What do the options “Do not show this extension in the extension manager” and “Prevent the uninstall of this extension” do? They don’t seem to work for me.
These options only work if your CCK is located in the extensions directory where the Firefox executable is located.
If you have any more questions, feel free to ask in the comments.