word zotero field code currpted

[jasonandjack1997]

Debug log ID

V4C94885-refs-euc/6.7.137-7

What happened?

I am converting a md file with bbt citations to a word file. In the converted word document when click zotero referesh the error bellow occurs and the citations are deleted automatically! I opened the converted word files weeks ago which could be refershed and updated to live ciations and did the same actions, but even these files show the same errors as below: zotero code corrupted, and citations got deleted.

The command: pandoc -s --lua-filter=zotero.lua -o paperback.docx paper.md

The md file:

---
zotero:
    csl-style: apa7 # pre-fill the style
    author-in-text: true
---

Creativity, a fundamental feature of human intelligence, has long been a challenge for AI 
[@ArtifIntellRev2022AnantrasirichaiArtificialIntelligenceCreative]
[@NatHumBehav2023WebbEmergentAnalogicalReasoning; @2023ZhangExploringMITMathematics; @InternetofThingsandCyber-PhysicalSystems2023RayChatGPTComprehensiveReview]

The word file

The error when referesh:

I have nearly a hundred ciations in that paper and now don't know what to do .

Another question is some citations have the "not in zotero" in the pandoc converting process but the keys are actual keys of items.

Best,

[github-actions[bot]]

Hello there @jasonandjack1997,

Hope you're doing well! @retorquere is here to help you get the most out of your experience with Better BibTeX. To make sure he can assist you effectively, he kindly asks for your cooperation in providing a debug log – it's like giving him the key to understanding and solving the puzzle!

Getting your debug log is a breeze and will save us both time in getting your problem resolved or the new feature you'd like implemented. Trust me, it's way quicker than discussing why it's important. :smiley:

How to Share Your Debug Log:

1. If the issue involves specific references, citekey generation, or exports, just right-click on the relevant item(s) and choose "Better BibTeX -> Submit Better BibTeX debug log" from the menu.

2. For other issues, follow these simple steps:

   • Restart Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled).
   • Reproduce the problem.
   • Select "Send Better BibTeX debug report..." from the help menu.

Once you hit that submit button, you'll get a special red debug ID. Just share that with @retorquere in this issue thread. If the question is regarding an export, don't forget to include what you see exported and what you expected.

By sharing your debug log, you're giving @retorquere a clearer picture of your setup and the items causing the issue. It's like a superhero cape for him – he can swoop in and tackle the problem much faster.

We totally get that your time is valuable, and we appreciate your effort in helping @retorquere help you. You might be surprised at how much this simple step speeds up the whole process.

Thanks a bunch!

PS: If the Debug Log menu does not appear, or it does not send the debug log

A fallback option is available under "Help" > "Send debug log to file.io".

[jasonandjack1997]

This example and action I did achived right results few weeks ago but tody I don't know that is going on.

[retorquere]

[jasonandjack1997]

Hello there @jasonandjack1997,

Hope you're doing well! @retorquere is here to help you get the most out of your experience with Better BibTeX. To make sure he can assist you effectively, he kindly asks for your cooperation in providing a debug log – it's like giving him the key to understanding and solving the puzzle!

Getting your debug log is a breeze and will save us both time in getting your problem resolved or the new feature you'd like implemented. Trust me, it's way quicker than discussing why it's important. 😃

How to Share Your Debug Log:

1. If the issue involves specific references, citekey generation, or exports, just right-click on the relevant item(s) and choose "Better BibTeX -> Submit Better BibTeX debug log" from the menu.

2. For other issues, follow these simple steps:

   • Restart Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled).
   • Reproduce the problem.
   • Select "Send Better BibTeX debug report..." from the help menu.

Once you hit that submit button, you'll get a special red debug ID. Just share that with @retorquere in this issue thread. If the question is regarding an export, don't forget to include what you see exported and what you expected.

By sharing your debug log, you're giving @retorquere a clearer picture of your setup and the items causing the issue. It's like a superhero cape for him – he can swoop in and tackle the problem much faster.

We totally get that your time is valuable, and we appreciate your effort in helping @retorquere help you. You might be surprised at how much this simple step speeds up the whole process.

Thanks a bunch!

PS: If the Debug Log menu does not appear, or it does not send the debug log

A fallback option is available under "Help" > "Send debug log to file.io".

Sorry that I reallized that the log provides settings and contextual info. The log id is provided. The pandoc version is 3.1.8.

[retorquere]

Don't open duplicate issues because you chose to ignore the debug log request and then expect an immediate response from me.

I'll look into the problem today.

[retorquere]

I cannot reproduce the problem. Please attach the docx file that Zotero claims is corrupted.

[retorquere]

Please also upload a screenshot where the Zotero popup does not obscure the document, the error message says "this citation" but I cannot see which citation it is referring to.

[retorquere]

Another question is some citations have the "not in zotero" in the pandoc converting process but the keys are actual keys of items.

The debug log only had Anantrasirichai and Bull, so I cannot test this. With the items in V4C94885-refs-euc/6.7.137-7 there is just one item and the rest correctly fails to resolve.

[jasonandjack1997]

Please also upload a screenshot where the Zotero popup does not obscure the document, the error message says "this citation" but I cannot see which citation it is referring to.

The screenshot is the previous image.

[jasonandjack1997]

Another question is some citations have the "not in zotero" in the pandoc converting process but the keys are actual keys of items.

The debug log only had Anantrasirichai and Bull, so I cannot test this. With the items in V4C94885-refs-euc/6.7.137-7 there is just one item and the rest correctly fails to resolve.

I think the problem could be a version issue. When I used zotero 6.0.27 on a third computer the citations in docx refreshed correctly (most of them) and not automatially deleted (every citation is kept).

I suppose it could be caused be the Word plugin version with zotero 7. Altought weeks ago the plugin worked fine.

[retorquere]

Please also upload a screenshot where the Zotero popup does not obscure the document, the error message says "this citation" but I cannot see which citation it is referring to.

The screenshot is the previous image.

I understand, but I need a new screenshot where you move the popup out of the way so that I can see what "this citation" refers to. I am assuming zotero highlights it in some way, but I cannot see it, because the popup is over the document.

[retorquere]

I suppose it could be caused be the Word plugin version with zotero 7. Altought weeks ago the plugin worked fine.

I'll see whether I can reproduce the problem on Z7b.

[jasonandjack1997]

Please also upload a screenshot where the Zotero popup does not obscure the document, the error message says "this citation" but I cannot see which citation it is referring to.

The screenshot is the previous image.

I understand, but I need a new screenshot where you move the popup out of the way so that I can see what "this citation" refers to. I am assuming zotero highlights it in some way, but I cannot see it, because the popup is over the document.

Here I reproduced it. No matter yes or no clicked all will be deleted.

[jasonandjack1997]

Q7PCJS7D-refs-apse/6.7.137-7 The citekey is ArtifIntellRev2022AnantrasirichaiArtificialIntelligenceCreative. The key is identical but it could not be found and converted. One citation in pandoc cmd showed not found but still converted

[retorquere]

Citation keys are case-sensitive; your document has ArtifIntellRev2022AnantrasirichaiArtificialintelligencecreative but your library hasArtifIntellRev2022AnantrasirichaiArtificialIntelligenceCreative, and it is the former that is not found. I cannot speak to the other items as they are not in Q7PCJS7D-refs-apse/6.7.137-7.

[retorquere]

(BTW Zotero popups aside , it is substantially easier for me to deal with text documents and console output being attached or pasted rather than screenshotted, it's easier for me to search for exact terms).

[retorquere]

I can reproduce the corruption message on Zotero beta, but have not yet found the cause. I've asked the devs for support on the developers forum.

[github-actions[bot]]

:robot: this is your friendly neighborhood build bot announcing test build 6.7.139.2718.5413 ("csl-json year is a string")

Install in Zotero by downloading test build 6.7.139.2718.5413, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

[retorquere]

There's a new version of the filter on the website, combined with this test build it should solve the corruption problem.