pdf is stored but .zotero-ft-cache and .zotero-ft-info are not created
Hi everyone,
When I add a new article in Zotero using the icon in the adress bar of Firefox, the new item is created correctly, the pdf file is attached and stored in a new folder. However, sometimes the files .zotero-ft-cache and .zotero-ft-info are not created in this new folder so that the pdf cannot be open in Firefox by double-clicking on the Zotero open. The pdf is correctly read when I open it with an external viewer.
It occurs only sometimes and I cannot find the criteria that makes it happens. No error message is displayed. I am using FF 9.0.1 and 2.1.10. The problem occurs both on Windows XP and Vista.
Thanks for help,
Florent
When I add a new article in Zotero using the icon in the adress bar of Firefox, the new item is created correctly, the pdf file is attached and stored in a new folder. However, sometimes the files .zotero-ft-cache and .zotero-ft-info are not created in this new folder so that the pdf cannot be open in Firefox by double-clicking on the Zotero open. The pdf is correctly read when I open it with an external viewer.
It occurs only sometimes and I cannot find the criteria that makes it happens. No error message is displayed. I am using FF 9.0.1 and 2.1.10. The problem occurs both on Windows XP and Vista.
Thanks for help,
Florent
For example, here was the former name automatically given by Zotero:
"Barkan et Luz - 2007 - Diffusivity fractionations of H 216OH 217O and H .pdf"
and the new name I have given:
"Barkan et Luz - 2007.pdf"
There was a special character after the "H"s (an exponent). Is there any mean to manage that automatically?
In Zotero 3.0b3 on Windows XP, with the Foxit Reader PDF plugin in Firefox, I get an empty Firefox window with a zotero://attachment URL. I'm get the same behavior on Windows 7 with the Adobe Acrobat plugin.
A similar problem has been reported before.
We can try to figure out what characters cause this and strip them. For what it's worth, the same file works fine in a PDF plugin on OS X.
Thanks Dan for having included the fix in the next version.