Syncing troubles with group libraries

nhm_wien

This zotero account owns 4 "Public, Closed Membership" group libraries.
Unfortunately some members cannot sync anymore because of the following warning message:
https://www.dropbox.com/s/64ustwbc9ofgbvl/zotero_warning.jpg
After clicking "Reset Group and sync" there appear new warnings about the other groups and the warnings appear over and over again, this means syncing is impossible.

Thank you for any advice!

adamsmith

1. Make sure all of the members have updated to Zotero 4.0.13, which came out last night with some sync fixes
2. have you made sure the members still have write access to that library? (either they're administrators or all members have editing privileges in the library settings - to be set by the administrator on zotero.org)

dstillman

Also, when did this problem start?

nhm_wien

Thank you! 4.0.13 did not solve the synching troubles.
The warnings affect only those group libs without editing privileges. The members had editing privileges the years before but not now.
This problem started some days ago.

dstillman

If possible, could you generate a Debug ID that covers two appearances of the message for a particular group, with a reset between them?

(Alternatively, if one of the computers is running OS X or Linux, real-time debug output, which you can email to support@zotero.org with a link to this thread, might be more helpful. The Debug ID might not capture enough data by default.)

nhm_wien

The Debug ID is D855089199.
Thank you very much!

dstillman

Unfortunately the debug output doesn't go far enough back to be useful. (Not your fault — it only stores a fixed amount by default. We could increase the limit with some hidden prefs if necessary.)

We can fiddle this more, but since the current sync architecture is going away soon, there are two options that might be easier:

1) The affected users can leave all the problematic groups — or you can remove them — and then sync to remove the groups locally. Then if they join the groups again, the problem should go away.

2) Alternatively, if they're not using other libraries in Zotero or haven't made any local changes in other libraries, they could do Restore from Zotero Server from the Sync -> Reset pane of the Zotero preferences to simply overwrite all their local data with the server versions.

I'm not totally sure what's causing this, though, and I can't reproduce it, so it's not impossible that there'd still be a problem after. But hopefully either of the steps above would clear this up.