Automatic export: Library not updating prior to export

[tduncs]

Debug log ID

PXB2BFA3-euc/6.7.236-7

What happened?

My Library is no longer updating prior to export. Recently upgraded to Zotero 7, but it was working in Zotero 7 prior to this occurrence. I have it set to auto-export on change, but when I go to settings, it's showing the last update was Sep 23rd 2024, despite having made changes and added references since. I have status=green tick. The new additions are not present in the .bib file (the export itself runs fine).
I have got to the limit on my online Zotero storage but this shouldn't affect the .bib ?
Thank you

[retorquere]

You're not on the most recent version of BBT. If the latest doesn't work, see if the discussion in #3000 applies to you.

[tduncs]

Thanks. I've updated to the version in the other thread.
My library still isn't updating prior to export.
Log: GKI6YB9M-euc/6.7.238.7121-7

[retorquere]

prior to export?

[tduncs]

As in, I can export the library fine, but it's an old version that isn't updating on change, as expected.

[tduncs]

Hmmm, so I've had another look - in settings the last update is showing as 23rd Sept (as in the screenshot). I've added several references since then, all of which are coming through into the .bib up to the 26th Sept. Then all four most recent from 30th Sept to today, don't exist in the .bib.

[tduncs]

Am I missing something - could it be to do with online storage - do I need to restart again?

[retorquere]

No relation to online storage. I was just confused with your wording. A new build is incoming that will tell me more about what is going on on your system.

[tduncs]

OK, thank you.

[github-actions]

🤖 this is your friendly neighborhood build bot announcing test build 6.7.240.7140 ("logging")

This update may name other issues, but the build just dropped here is for you; it just means problems already fixed in other issues have been folded into the work we are doing here. Install in Zotero by downloading test build 6.7.240.7140, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

[retorquere]

please install, reproduce the problem, and send a new log.

[tduncs]

That seems to have worked! Back up and running.

[retorquere]

Can you check whether the regular release (.240) also works for you?

[tduncs]

That came up with a 'Blocked' popup when I installed from file, and now the citation key field has gone?

[tduncs]

How can I undo - worried that citations with same author/year will have lost their relevant a,b,c additions?

[retorquere]

That came up with a 'Blocked' popup when I installed from file, and now the citation key field has gone?

Can you show a screenshot of that "blocked"?

How can I undo - worried that citations with same author/year will have lost their relevant a,b,c additions?

Data is separate from the plugin -- you can (re)install any version (that is not too old). Even if you plan to never install BBT again, the data remains until you manually go to the storage directory and choose to delete it.

[tduncs]

Ok, that's good to know! I couldn't recreate the Blocked popup - but I removed and re-added the plugin, and started a new Auto-Export. And all seems to be working!
Could you tell me one thing, while I've been changing the references to test all this, sometimes the citation key is added to the Extra field, and the citation key will only change based on a change to the author field if the text in Extra is removed. Is this expected behaviour?
Thanks very much.

[retorquere]

sometimes the citation key is added to the Extra field

this is either something you have selected to do, so on your instruction only, or you have enabled auto-pin, which will do it on your behalf a configurable number of seconds after a change.

and the citation key will only change based on a change to the author field if the text in Extra is removed. Is this expected behaviour?

Yes. If this appears without you doing anything, you have enabled auto-pin.

The reason some people want this is that they have used the key in articles and they don't want it to change even if corrections are made to the item. Another benefit is that these keys will show up on the Zotero-Overleaf integration -- if they are not in the Extra field, that integration will generate keys that are pretty much guaranteed to differ from BBts, and even have a chance to change over time even if you don't touch the item in Zotero.

[retorquere]

So .240 works for you now?

[tduncs]

So .240 works for you now?

Yes - thanks very much.

The reason some people want this is that they have used the key in articles and they don't want it to change even if corrections are made to the item. Another benefit is that these keys will show up on the Zotero-Overleaf integration -- if they are not in the Extra field, that integration will generate keys that are pretty much guaranteed to differ from BBts, and even have a chance to change over time even if you don't touch the item in Zotero.

And.... I didn't realise there was an Overleaf integration! So thank you again.