|Overview Screenshots Download and Install Help Contact|
Info for System Adminstrators
This help topic is intended for system administrators managing the deployment of Clippings on multiple machines.
System administrators and redistributors can bundle a default Clippings datasource file into a customized Clippings XPI to pre-populate their users' datasources when they install the customized XPI. To create a customized XPI, do the following:
- Download the Clippings 3.0 XPI and save it to a location on your system.
- Unzip the XPI using a ZIP client such as WinZip. Make sure that the directory structure in the XPI file (actually a ZIP archive with an .xpi file name extension) is intact.
- Copy a Clippings datasource file containing the default Clippings data to the defaults directory and rename it clippak.rdf.
- Re-zip the XPI archive; the directory structure and all files that were in the XPI must be preserved.
When the user installs the customized XPI, the default Clippings data will be automatically imported when starting the host application (Firefox or Thunderbird) after the installation.
Use the Clippings Editor utility to create the default datasource file.
Ensuring Integrity of Customized XPIs
Because the Clippings XPI can be customized with default clippings, there exists a need for your end users to ensure that the customized XPI they are receiving from you is genuine and has not been tampered with.
To ensure that your users are obtaining the correct XPI, you should generate a checksum against the final customized XPI and distribute the checksum as a text file along with the customized XPI. There are various utilities available to do this for you, namely md5sum or sha1sum on Unix and Linux. After your end users have downloaded the customized XPI, they can validate the download by running a checksum validator utility against their download to ensure that they have the genuine, untampered XPI.
Creating Default Clippings Files With Clippings Editor
Clippings Editor is a standalone application for creating, editing and viewing Clippings datasource files. Use this tool to create the default Clippings datasource file for packaging in a custom Clippings XPI for distribution to your users.
Download and Install
Choose one of the following:
- XULRunner Application Archive (77 KB) - This option requires that the Mozilla XULRunner runtime (versions 1.8-1.8.0.*) be installed on your system. Works on Windows, Mac OS X and Linux. Follow the instructions in this Devmo article on how to install the application archive.
- Full Standalone Application (for Windows only) (7.0 MB) - This is the full application with the Mozilla XULRunner runtime built in. A separate download of the XULRunner runtime is not required. To install, simply unzip to a desired location on your system.
Supported languages: English (United States), Dutch, French, Italian, Japanese, Polish.
Things You Should Know About
If creating a new Clippings datasource file, you will be prompted for a file name and folder location to save it to before you can begin editing it.
The datasource file is automatically saved when exiting the application. The Save command on the File menu is available if you wish to save the currently-open file at any time.
Clippings Editor doesn't natively handle the old Clippings 1.x series format files. Clippings 1.x files can be opened, but a new Clippings file must be created to edit it. Also, Clippings Editor cannot save a file in Clippings 1.x format – use the Export command on the File menu to export to Clippings 1.x format.
Do not use Clippings Editor to modify the Clippings datasource file in the user's Firefox or Thunderbird profile folder (or the user's home directory if the common Clippings datasource is enabled). Doing so may result in data corruption. Instead, invoke Clippings Manager from the host application and export the Clippings data using Options → Export. You can then edit the exported file using Clippings Editor.
Back to Help Index