Problem Updating Citations while the Find and Replace Box Is Open
I'm using Zotero 5.0.97-beta.50+5f61ac23a and Word for Windows 16.0.14527.20168.
I was needing to change footnote citations from something like "123 n. 5" to "123n5". So, in searching Word for "n. ^#", I was trying to then edit the corresponding Zotero citations in the default citation dialog.
When I finished editing and pressed enter to save the citation, however, Zotero would crash, act like I'd deleted the contents of the whole citation manually, and ask me if I wanted to visit the debugging broken documents page. On reopening the document, I'd then need to refresh the citation, say I didn't want to save it as empty, and let Zotero recompose the citation.
If I closed the find box before editing the citation, however, that process went as expected. If this issue is reproduceable, it would be helpful if (a) Zotero could insert or modify citations with the find box open or (b) raise a warning box that the find box needed to be closed before inserting a citation.
Thanks so much!
I was needing to change footnote citations from something like "123 n. 5" to "123n5". So, in searching Word for "n. ^#", I was trying to then edit the corresponding Zotero citations in the default citation dialog.
When I finished editing and pressed enter to save the citation, however, Zotero would crash, act like I'd deleted the contents of the whole citation manually, and ask me if I wanted to visit the debugging broken documents page. On reopening the document, I'd then need to refresh the citation, say I didn't want to save it as empty, and let Zotero recompose the citation.
If I closed the find box before editing the citation, however, that process went as expected. If this issue is reproduceable, it would be helpful if (a) Zotero could insert or modify citations with the find box open or (b) raise a warning box that the find box needed to be closed before inserting a citation.
Thanks so much!
You do make a good point about the possibility of manually adjusting the text.—For me, it's really just a personal workflow preference to do the adjustment via the citation dialog so that the note references don't end up static and will update if I swap styles (e.g., to another one that might require the same formatting for citation of notes as the previous).
EDIT: Sorry, this is wrong, and yet another reason why we are planning to remove the ability to edit citations in the citation editor since it will persist the edited text even across citations style changes or even citation item changes.
Either way, editing the citation in the classic dialog should not crash Zotero, but I cannot reproduce it. Does it happen for other items? Does it matter which part of the citation you edit? Can you export the item and upload it somewhere to test?
I've even just tried in a brand new document, and I can't even insert the first citation.
But all this is only with the (old-school) "Find and Replace" dialog box open (or "Advanced Find," the one with the find, replace, and go-to tabs). With the navigation pane open (with the heading, pages, and results tabs), the Search Document feature works fine, and Zotero can insert and modify citations as usual.
With the empty new document, I get as far as selecting a citation style, but then I get the Zotero error I mentioned above before even getting the default (red outlined box) citation dialog to input a citation.
I just tested with Word Version 2109 Build 16.0.14430.20154 32-bit, and setting the citing style did fail (with an error, no crash), but editing the citation worked. What citation style are you (trying to) use? Can you provide full steps to reproduce in a new document?
If I can provide anything else, please feel free to ask.
Thank you so much.
I've now tested again and managed to reproduce the issue. However Zotero is receiving an error from Word saying that "the function" is not available with the Find and Replace window open. I didn't check which function, but it's likely we won't be able to make citing work with the Find and Replace window open, although we will be able to show a better error. I've also created a ticket to track this. Thanks for reporting and helping debug.