One of the key innovation in LibX 2.0 is the fact that there exists only a single download package for all users (independent of which edition they wish to use). After downloading this package, the user must then activate an edition, or an edition is automatically activated.
Generic Download without Activation
If a user downloads LibX from the download page, no edition will be activated. Instead, a screen such as the one below is shown, where the user can search for editions and activate them.
If the user comes from an IP range that was also used by an edition maintainer previously, the edition recommendation
system may kick in.
Direct Download and Activation of an Edition
If a user downloads LibX 2.0 from an edition download page, such as the download page for LibX 2.0 VT, then the VT edition will be activated automatically after download. This works by using cookies, which will be set upon download, and LibX will read those cookies when it starts up. If you wish to embed the download link into your site, use this syntax:
and replace ‘vt’ with your edition id. This will set the cookie on download, install LibX, which should then automatically activate edition vt.
Temporary Activation of a Configuration for Testing by Edition Maintainer
Edition maintainers often have LibX installed while testing a new revision. If an edition maintainer looks at a edition download page, then opens LibX, they will see a “Maintainer” tab as shown below:
In this example, a maintainer has LibX Worldcat edition rev 4 installed (which was the live revision at this point), but was looking at the test page for revision 5.
Upgrading existing LibX 1.5 users.
We have patched LibX 1.5 to store the configuration locally. If you enable the 1.5 – 2.0 update in the edition builder, users will be directed to the LibX 2.0 plug-in (via the update.rdf mechanism). When LibX 2.0 starts up in Firefox, it will check if this configuration was stored, and should activate it automatically.
Above process may fail if the user is not connected to the Internet when the configuration is activated, or libx.org is not reachable. In this case, a message: “Could not load configuration …” may be displayed. It may also fail if the configuration itself is faulty (for instance, some required setting is not set.)
It will fail if the edition has not been made live, i.e., if no live revision exists.
In those cases, the user should manually activate the edition; feel free to contact us should the problem persist.