Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MdNotes not generating anything (on Macbook 2023) #215

Open
paulinvienna opened this issue Apr 6, 2023 · 2 comments
Open

MdNotes not generating anything (on Macbook 2023) #215

paulinvienna opened this issue Apr 6, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@paulinvienna
Copy link

Describe the bug
Mdnotes does not create/export any markdown file: whatever I select (create markdown file, export to markdown, batch export to markdown), it brings up the folder where the md file should be saved, but no note gets generated.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the note/parent file
  2. Right click and select Mdnotes
  3. Select "batch export to markdown"
  4. Select target folder and click "open"
  5. No note is generated

Expected behavior
Previously, this created a note in the target folder, which I could see both within Zotero (under the parent file), in finder (I'm working with Mac) and in Obsidian.

Screenshots
Screenshots don't work as it is the absence of action that is the problem.

Desktop (please complete the following information):

  • OS: Mac OS Ventura 13.2.1
  • Zotero version: [v6.0.23]
  • Mdnotes version: [v0.2.3]
  • Zotfile version: [v5.1.2]
  • BetterBibtex version: [v6.7.67]

Additional context
This was not a problem when I was using my previous MacBook (Intel) - but seems to be an issue since installing it on my new MacBook (Apple M2)

@paulinvienna paulinvienna added the bug Something isn't working label Apr 6, 2023
@kun-wang
Copy link

kun-wang commented Oct 24, 2023

I meet the same problem. The "Debug Output Logging" information from Zotero/Help/ is as follows:

TypeError: fileName is undefined getValidFileName@chrome://zotero/content/xpcom/file.js:1251:5 getNCFileName@chrome://mdnotes/content/mdnotes.js:414:14 getMDNoteFileName@chrome://mdnotes/content/mdnotes.js:421:10 getItemMetadata@chrome://mdnotes/content/mdnotes.js:238:30 getRegularItemContents@chrome://mdnotes/content/mdnotes.js:945:22 exportToMarkdownMenu@chrome://mdnotes/content/mdnotes.js:1037:26

@kun-wang
Copy link

I meet the same problem. The "Debug Output Logging" information from Zotero/Help/ is as follows:

TypeError: fileName is undefined getValidFileName@chrome://zotero/content/xpcom/file.js:1251:5 getNCFileName@chrome://mdnotes/content/mdnotes.js:414:14 getMDNoteFileName@chrome://mdnotes/content/mdnotes.js:421:10 getItemMetadata@chrome://mdnotes/content/mdnotes.js:238:30 getRegularItemContents@chrome://mdnotes/content/mdnotes.js:945:22 exportToMarkdownMenu@chrome://mdnotes/content/mdnotes.js:1037:26

As mentioned in issue #224, my problem dues to the BetterBibtex update on October 24th.

I fixed the problem by rolling back the version of BetterBibtex.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants