Making Zotero Available on our Campus Desktop
We have a campus wide student desktop that uses AppSense to deploy some virtualized applications while others are not virtualized but installed on the thick client.
Firefox and Word are not virtualized so it isn't feasible to centrally update plug-ins so our Desktop teams have decided to allow the installation of Zotero and the MSWord plugin by users on the thick client.
This has the complication that if they upgrade Firefox the plugins may need updating.
The plan is to host the matching xpi files for users to install. But we will not always be current with Firefox versions.
Is there somewhere we can check which xpi files we need for a specific version of Firefox and download the right files? I know that they are archived but I don't know how the technical team could check which ones they need against their Firefox version.
I hope this isn't too confused! I'd really appreciate any advice.
Another issue that has been raised - though not critical - is that of the signing of the extensions. I understand that if the extensions were signed, the technical team would be able to script updates but that for unsigned extensions they have to update manually. Is there any prospect of signed extensions?
Thanks in advance
Jim
Firefox and Word are not virtualized so it isn't feasible to centrally update plug-ins so our Desktop teams have decided to allow the installation of Zotero and the MSWord plugin by users on the thick client.
This has the complication that if they upgrade Firefox the plugins may need updating.
The plan is to host the matching xpi files for users to install. But we will not always be current with Firefox versions.
Is there somewhere we can check which xpi files we need for a specific version of Firefox and download the right files? I know that they are archived but I don't know how the technical team could check which ones they need against their Firefox version.
I hope this isn't too confused! I'd really appreciate any advice.
Another issue that has been raised - though not critical - is that of the signing of the extensions. I understand that if the extensions were signed, the technical team would be able to script updates but that for unsigned extensions they have to update manually. Is there any prospect of signed extensions?
Thanks in advance
Jim
(All Firefox extensions will need to be signed (by Mozilla) later this year, though.)
I can't really speak to the policy issue - I can ask that UCL consider a move to ESR but any movement would be many months away I fear.
The reason to host the xpis ourself would just be to ensure compatibility with the potentially outdated version of Firefox on our desktop.
As to signing, again if I understand correctly, our environment requires that an extension be signed in order that its installation on our thick client be automated. Unsigned clients have to be included through a manual process. I don't understand more of this issue than that I'm afraid. But your later comment renders this moot.
I had hoped we'd discover a way to check the compatibility of the extensions and match the xpis to whatever the current FF installation is, but maybe we have to concede we can't.
I'll pass what I've learned on to the technical team concerned.
The next Firefox ESR is 38, which is due out in May. We follow Mozilla's support schedule and test for compatibility with the previous ESR until it's EOLed, which for 31 will be in August. We don't necessarily go out of our way to break compatibility at that point, but we don't worry about it if it happens, and sometimes choose to do so if supporting older versions becomes a burden.