Upgrade Storagedoctorproctor
About
- Username
- doctorproctor
- Joined
- Roles
- Member
Comments
-
Hi, no, it was created from scratch in GoogleDocs. But it *was* originally in Chicago author-date format; that's the only thing that may be different.
-
OK, we are now on the same page. Quick note that if I have previously selected Chicago 18th notes-biblio style I *do* see that endnote option, but when I select another style, then go back to 18th notes-biblio, the option disappears. Jim P.
-
Hi, bumping this request. I'm now on Z latest (7.0.24). When I indicate endnotes for Chicago 18th ed notes/bibliography, should I see current footnotes migrated to end of document? Perhaps I am misunderstanding the functionality of this option. Tha…
-
Yes, I'm on 7.0.22 (see screenshot att'd). Happy to further diagnose on my end. Regards, Jim https://s3.amazonaws.com/zotero.org/images/forums/u610289/osngn8dnh0cqk0eedzow.png
-
I'm using Chicago 18th ed notes-biblio dated 7/17/25 with GoogleDocs. I know that GoogleDocs does not inherently support endnotes, but this option appears via Document Preferences (see att'd screenshot). The option does not, however, work. Is this…
-
OK, will do, and again I sure appreciate all the time you and other developers put into this excellent product!...have used it successfully for years.
-
Got it; sorry for Google's issues. Yes, I have no other problems, and use Zotero heavily with GoogleDocs, Chicago author-date (latest) style. I have not experienced this bug at all, outside of the scenario I described. The workaround I posted yest…
-
I think I have a workaround (though possibly only applicable to me): the original destination document had formatted Z references, and as I typically do I unchecked "Automatically update citations" when initially running Z document prefs, given docu…
-
I have now confirmed a new piece of information: I do *not* get error 500 when copying/pasting into a new, blank GDoc without existing Z citations. I did attempt to fix in existing recipient GDoc by clicking Refresh, but this did not fix problem. …
-
Just reproduced error (#848498816). 500 error displays when I paste GDoc text with Z refs into existing doc with Z refs. Pasted ref doesn't look unlinked until I attempt to edit it, then I get warning/ref turns red. https://s3.amazonaws.com/zotero.…
-
Hi, this isn't yet working for me with connector update; just submitted report #458643966 [which mentions JS connection error, though my screen shows exact same 500 error as others]. I did install .177 update and restarted Chrome, so I should be up …
-
Hi, thanks and sorry, I'll be more clear as to your points. I'm pretty sure all of this (initial citation via Z connector, then later copy/paste of text with citation) happened following the most recent .141 update. By "earlier," I meant a time gap …
-
Hi, experienced problem again just now; see att'd screenshots. Steps I was taking: (1) I had earlier copied/pasted a reference (Homans 2024) that appeared to paste just fine, i.e., it appeared in standard shaded Z format in my GDoc. (I have done si…
-
Yes, thank you; I restarted Chrome and now see the updated connector. I'll check to see if I can reproduce the error, and will report here if so.
-
OK, citations issue just happened; see screenshot att'd, and those two refs in GoogleDoc now in red. A few details: -They were fine a few hrs ago when I last worked on the doc. -I *think* I was "successful" this time when I did "Document preference…
-
An additional, likely related, error attached. This happens when I select "Document preferences..." to connect Chrome with Z after a several-hour break. I can then select it again and all works fine; error just shows the first time. https://s3.amaz…
-
Thank you!
-
I have not yet reproduced the problem I reported, but I *have* witnessed the attached twice today, in which after a break of several hours I return to the GoogleDoc to add a Z citation and get this error msg. If I copy/paste [or add a citation] afte…
-
Thanks, I will report back when it happens again. This AM I did full doc prefs to make sure all was working, copy/pasted three passages, none had a problem. Will continue to monitor for this issue and post requested info.
-
Good; thanks. Jim P.
-
Thanks; I was not editing items in a group collection at the time, but I'll let you know if issues persist. Regards, Jim P.
-
Okay, will pressure our IT folks to upgrade...I guess it's difficult during school semesters!... Jim
-
Okay, thank you again for your careful response; I sure appreciate it. We'll process this a bit more and figure out a workable procedure on our end. I may report another sync issue soon (on another thread), but will investigate it a bit first. Jim
-
Well, after getting more feedback from students and thinking about the above for awhile, I have a few more thoughts: (1) Not all students who had problems syncing were fixed by the latest dev XPI. I was thinking we could manually update their group…
-
Okay, thanks. I think we can construct some rules/recommendations out of the above. Regards, Jim
-
Okay, I'm understanding this a bit better. Basically, what is apparently required are two users modifying the same tag or collection, though this doesn't always trigger an error. This is interesting in that, for the most part, our students are work…
-
Right, so my interpretation of what you say above is that this could possibly happen merely by syncing an old version, not necessarily by doing editing (e.g., of tags) in the group library, then syncing. Anyway, once we experienced the problem (aga…
-
Here's one affected student's reply to my query, and he is reliable and tech-minded...possibly would it happen simply if the local tagset doesn't match the server tagset? "I can confirm that I did not change tags before attempting to sync and have …
-
Yes, certainly, and we will recommend the same...I don't know why they wouldn't have it on, unless e.g. their login information is incorrect. (There will still be students who aren't yet using it outside of course requirements, so they won't have s…
-
Okay, so as a procedure, we could recommend first syncing before doing any work with tags, and this should solve the problem. It's good to hear that it's not about earlier versions. I'll check with affected users to confirm the above. Thanks, Jim