[LibX] Silent deployment of the toolbar to Chrome.
godmar at gmail.com
Tue May 8 06:50:52 PDT 2012
I don't follow. None of the sources you mention talk about including the
appid in the manifest.json file of the extension. In fact,
http://code.google.com/chrome/extensions/manifest.html does not even
mention an appid as a valid key for a manifest.json file.
LibX 2.0's appid is ffkfoaiikoedjcjlpnnaidojhfchiafk which is all you
should need to know.
Also, when pushing updates to multiple machines, you'll need some way of
activating a particular edition.
It's not clear how this could work. We're working on a service that checks
which campus a user is on and suggests editions associated with that campus
(hopefully deployed soon). Till then, you'd need to either set the same
cookie that would be set had the user downloaded the plugin (see
or you'd need to write to the localStorage facility associated with the
edition's background page (not clear how to do this using an automated
On Fri, May 4, 2012 at 10:08 AM, Janis Mathewson <jmm132 at psu.edu> wrote:
> Good morning,
> We are trying to silently deploy the LibX Toolbar to Chrome on our Library
> In the manifest.json file, the app id is missing. We see it in the
> updates.xml file, but not the manifest.json file. In order for active
> directory group policy to push the libx toolbar out we need to have the app
> id in and codebase url in the manifest file. (we think) Here are the
> guides I was trying to follow:
> http://code.google.com/chrome/extensions/autoupdate.html and
> Any help in getting this to work would be greatly appreciated.
> Janis Mathewson
> Department for Information Technologies (I-Tech)
> Penn State University Libraries
> University Park, PA 16802-1812
> (814) 865-4867
> Libx mailing list
> Libx at mozdev.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libx