Unable to produce relative file paths for attachments in file: field when exporting

[abradd]

• I have verified that I am on the latest release of BBT (https://github.com/retorquere/zotero-better-bibtex/releases/latest) and Zotero
• I am posting a single question, bug or feature request
• I have included a descriptive subject of the problem
• I am available for follow-up questions and testing

My data directory is set to ~/zotero (with the storage folder internally that symlinks to another location so I can sync it across computers) in the Zotero preferences and my pdfs are exported via Zotfile to ~/literature. I saw an explanation for the current scheme of generating relative vs. absolute paths for the file: field in #654, but I am still unable to produce relative paths regardless of my selected export location. The ~/zotero/storage folder contains mostly html content from snapshots because I relocate the pdfs with Zotfile.

I have exported my .bib file to ~/zotero, ~, and ~/literature, but every time it produces an absolute path in the file: field. This applies for both the html content in ~/zotero/storage and the pdf content in ~/literature. Given the current implementation I don't really expect the pdf files to be defined relative paths under any case, but I am surprised the html content was not defined as a relative path.

[retorquere]

If you export to ~/literature where your attachments live, the path should automatically be relative. I will have a look.

[FirasSadiyah]

I am having the same issue with a similar scenario to OP. The file path is not relative in any of these cases above.

[blip-bloop]

🤖 this is your friendly neighborhood build bot announcing test build 5.0.192.2655 ("fixes #935 (I think)").

[FirasSadiyah]

@retorquere This build is working for me. Many thanks.

[retorquere]

A new release (.194) will be out soon, but it's just what you have now with a formal label on it. You will be upgraded autommatically, or you can force-update in the addons panel in 10 minutes or so when the tests have ran.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.