With reference to bug report: 4VMI4ZGN
When I do a biblatex export of one of my collections, and tick the keep updated button, the auto-export shows up where it should:

But it just stays at either "running" (as I've shown here) or, sometimes, "scheduled".
It's one of these really annoying issues where "it used to work", then I fiddled with some stuff (I think relating to the "Export unicode as plain-text latex command" options under the "Export" options menu, and then it never worked again.
I can run the export through Zotero by doing File > Export as normal, but it no longer automatically updates on changes.
:robot: this is your friendly neighborhood build bot announcing test build 5530 ("fixes #903").
Can you try 5530?
It works for me
Also work for me. THX
Yep. It all works fine now. Wow! Fastest turnaround ever! Thank you retorquere.
Only I and @blip-bloop can close issues; I keep issues open until I've merged the changes into the main development line. Tests on the merge are running and should drop as a new release in a few minutes. Thanks for your help guys, it's so important to get test feedback (and sorry for the disruption in your workflow).
:D thank _you_
On 6 Feb 2018 12:24 pm, "Emiliano Heyns" notifications@github.com wrote:
Only I and @blip-bloop https://github.com/blip-bloop can close issues;
I keep issues open until I've merged the changes into the main development
line. Tests on the merge are running and should drop as a new release in a
few minutes. Thanks for your help guys, it's so important to get test
feedback (and sorry for the disruption in your workflow).—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/retorquere/zotero-better-bibtex/issues/903#issuecomment-363406721,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEiz1z2-IDgiLqrY7lAu0btaUWySta4wks5tSER4gaJpZM4R5156
.
@blip-bloop will also re-open issues if you comment on them :smile:
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.
Most helpful comment
Can you try 5530?