Chrome connector and multiple instances of standalone
I´m working in Windows 2012R2 server. We have zotero standalone installed and every user has it´s own database (the base directory is created on the profile directory of each user). Also, every user has a different language in his zotero configuration (changing the configuration parameters in about:config --> general.useragent.local to his prefered language and int.locale.matchOS to false).
We have installed the zotero Chrome extension. But when someone tries to save an item using this connector, the item actually is saved into the library of the first instance opened of the zotero standalone. Actually the zotero chrome extension recognizes only the first instance in the configuration windows (where it says if zotero standalone is available).
Let me use an example:
User A opens zotero standalone at 10 am. User A works adding books to his library A (which is in spanish) and everything is ok. But another guy (user B) opens another instance of zotero standalone (in french) at 10:20 am and when he tries to add a book to his library (B) using Chrome connector, he realizes that the book is not into his french library (B) but into the library of user A.
User B asks to user A to close his instance of zotero standalone (since they are working as clients of Windows Server). Now user B can add books to his library B using Chrome connector. Now user A opens zotero standalone and when he tries to add a book to his library A he realizes now that his book finishes on library B.
User A closes his zotero standalone instance and check if the zotero standalone is available in the configuration window of the extension of his own Chrome instance. It says available, even when his instance of standalone is closed. Because is "reading" the instance of user B (if user B closes his instance, it says unavailable correctly)
I hope the example is not confusing.
My question is: theres a way so the Chrome connector can work with the differents instances of Zotero Standalone? Why only connects to the first one?
We are using:
Zotero Standalone 4.0.25.2
Google Chrome 39.0.2171.95 m (64-bit)
Zotero Connector: 4.0.21
We have installed the zotero Chrome extension. But when someone tries to save an item using this connector, the item actually is saved into the library of the first instance opened of the zotero standalone. Actually the zotero chrome extension recognizes only the first instance in the configuration windows (where it says if zotero standalone is available).
Let me use an example:
User A opens zotero standalone at 10 am. User A works adding books to his library A (which is in spanish) and everything is ok. But another guy (user B) opens another instance of zotero standalone (in french) at 10:20 am and when he tries to add a book to his library (B) using Chrome connector, he realizes that the book is not into his french library (B) but into the library of user A.
User B asks to user A to close his instance of zotero standalone (since they are working as clients of Windows Server). Now user B can add books to his library B using Chrome connector. Now user A opens zotero standalone and when he tries to add a book to his library A he realizes now that his book finishes on library B.
User A closes his zotero standalone instance and check if the zotero standalone is available in the configuration window of the extension of his own Chrome instance. It says available, even when his instance of standalone is closed. Because is "reading" the instance of user B (if user B closes his instance, it says unavailable correctly)
I hope the example is not confusing.
My question is: theres a way so the Chrome connector can work with the differents instances of Zotero Standalone? Why only connects to the first one?
We are using:
Zotero Standalone 4.0.25.2
Google Chrome 39.0.2171.95 m (64-bit)
Zotero Connector: 4.0.21
The best solution I can offer for multi-user environments is to use Firefox with Zotero extension.
is there a solution to this problem already?
My colleagues and I would love to use ZOTERO Standalone together with Chrome on a Windows 2012 Server as it much smoother than using Firefox (which became very bulky and bloated in the last years...).
Thanks!