Thank you. I'll try that and test. I'll report the results.

And yes, if you're regularly cycling through tens (hundreds?) of thousands of items, that's just kind of out of scope of what Zotero is designed and tested for. Doesn't mean you can't do it, or that w

1) Type some text: "Test"

Excellent if it is now sorted, shall remove the offenders and re-test in due time.

(But this does serve as a reminder: this is still a beta app, we've limited the number of testers for a reason, and while we very much want people to test it, we do not recommend using it if you're no

For test.

It doesn't look like an intentional removal of functionality since we still have test for it [1]

CRAN¹ has added DOIs to the packages available there. As a test I have imported one of my own packages via the magic wand. The result as seen on https://www.zotero.org/ralfs#ZT8KDEU7 is not bad. But t

Edit: I recognize that this is a very large issue if Elsevier is mentioning Zotero when acknowledging a report of a problem. I'll do any testing you request to help get to the basis of the issue. Agai

Right! Thanks much. It is indeed Word to Word. And just to be sure will try it with duplicated Test docs.

@br_roy @sjgknight @epeva @adamsmith @gduffner This should now be fixed in the latest version of the beta. You might need to manually reinstall the Word plugin from Zotero preferences if you have Word

you restart Zotero after an update. Could you test and see if it now works correctly for you?

@adamsmith That's good to know. I will test Zotero 7 with VoiceOver then as soon as it's released and report accessibility issues if applicable. Nice to hear that things are getting better

Test that out with a fresh document with a couple of citations and copying over some text. Does that work?

you need to wait longer. Otherwise, you need to test this with the data directory on your local disk. After moving the data directory, you can reset the data directory location from Advanced → Files

zotero(3)(+0000003): Proxy not required for https://zoteroproxycheck.s3.amazonaws.com/test

The purpose of that test was to copy the full path (from Zutilo) where Zotero *thinks* a linked file is located, and then try to open the file at that path outside Zotero ... which would test if it is

The test procedure is a bit extreme, but I still report the findings in case anything useful can be identified here. It does not sound right to see Zotero saturate the RAM more than 10 minutes after t

Can you test this out in a fresh document?

I've just submitted a fix for that. Can you give this a test ride?