$version variable is displayed in Zotero 8 upgrade banner

dstillman · 2026-01-23T04:09:10+00:00

This discussion was created from comments split from: Announcing Zotero 8.

aborel · 2026-01-23T03:42:04+00:00

Very minor issue, in the status message displayed after the upgrade, the name of the $version variable is displayed instead of its value:

https://s3.amazonaws.com/zotero.org/images/forums/u9008/vqrg0rn1wq8f62nj018n.png

(Mac version, but probably not OS-specific)

dstillman · 2026-01-23T03:46:14+00:00

@aborel: Not a general issue. Do you have plugins installed?

https://s3.amazonaws.com/zotero.org/images/forums/u6/akuv5z4qs06wxy8waejb.png

aborel · 2026-01-23T04:08:00+00:00

Yes, several, I hadn't considered that. I'll try to downgrade and repeat the operation to identify which one(s) could be responsible.

dstillman · 2026-01-23T04:12:27+00:00

You don't need to repeat the upgrade. If you closed the banner already, you can just clear the extensions.zotero.postUpgradeBannerVersionShown pref in the Config Editor and restart.

aborel · 2026-01-23T04:39:05+00:00

Thanks for the tip, it will be much more efficient!

dstillman · 2026-01-23T04:57:33+00:00

(BBT has caused this sort of thing before, FWIW, though I'm not sure we ever figured out exactly why.)

aborel · 2026-01-23T05:16:52+00:00

I'm unable to reproduce with just this config change, the variable value is displayed correctly now with the same plugins as before (including BBT, which I suspected too) :-/
Is there a similar config option for "Zotero needs access to Word data to install the Word plugin." and "Zotero now automatically keeps attachment filenames in sync as you make changes to items."?

hsiangyu_wong · 2026-01-23T14:58:26+00:00

Technically, if some l10n files added by plugins are not properly removed after they got disabled (either manually or by update), some l10n of the app itself will not work due to missing resources from the removed plugin.

Restarting the app usually helps.

aborel · 2026-01-23T21:03:28+00:00

I see. Maybe this was a leftover from some older plugin version and the problem fixed itself when I restarted Zotero in order to reproduce the error.

shirriff · 2026-01-23T22:07:10+00:00

I'm seeing the same strange but minor issue after upgrading. The version displayed correctly after restarting Zotero, though. I'm on MacOS with plugins Better BibTeX and Zotero OCR. Report 426570215