Closed tdegeus closed 8 months ago
It looks like you did not upload an support log. The support log is important; it gives @retorquere
your current BBT settings and a copy of the items under consideration as a test case so he can best replicate your issue, or build towards the desired behavior. Without it, @retorquere
is effectively blind. Support logs are useful for both analysis and for enhancement requests; in the case of export enhancements, I need the copy of the references you have in mind.
If you did try to submit a support log, but the ID looked like D<number>
, that is a Zotero debug report, which I cannot access. Please re-submit a BBT debug log by one of the methods below.
This request is much more likely than not to apply to you too @tdegeus, even if you think it unlikely. Please trust @retorquere
when he says he will usually need one; he will more often than not just end up saying "please send a debug log". Let's just skip over the unnecesary delay this entails. Sending a debug log is very easy:
If your issue relates to how BBT behaves around a specific reference(s), such as citekey generation or export, select at least one of the items(s) under consideration, right-click it, and submit an BBT support log from that popup menu. If the problem is with export, please do include a sample of what you see exported, and what you expected to see exported for these references.
If the issue does not relate to references and is of a more general nature, generate an support log by restarting Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled), reproducing your problem, and selecting "Send Better BibTeX debug report..." from the help menu.
Once done, you will see a debug ID in red. Please post that debug id in the issue here.
Thank you!
Does the regular log ID submission not work for you? It is really a lot easier for me than logs being pasted/attached here. Does KAHEL672-refs-euc have a change to an item that should have auto-pinned? I don't see any item changes in that log.
For uploading I got:
Exception... "Component not initialized" nsresult: "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: chrome://zotero-better-bibtex/content/better-bibtex.js :: node_modules/jszip/dist/jszip.min.js/</<[54]</e.exports< :: line 138857" data: no] (X3KA2H5R-refs-euc, items: true)
Then, I generate this log by clicking on my latest added entry that is indeed not pinned. Let me know what I could improve to debug.
Note that I tried to change autoPinDelay
in the hope that that changed anything, but it did not
:robot: this is your friendly neighborhood build bot announcing test build 6.4.3.2323 ("log pinning activity")
Install in Zotero by downloading test build 6.4.3.2323, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".
Can you generate a new log using build 2323? It has extra logging, and may have a fix for log submission using the regular send method.
The new build seems to autoPin again. So I guess I will close this until the problem reappears. Thanks anyway!
Thanks for the feedback; there's no way you could have known, but @retorquere prefers to keep bugreports/enhancements open as a reminder to merge the changes into a new release.
Strange, because I only added a few logging changes aside changing the log format. Can you try to submit an support log to see if that works again too?
Yes! ABGQZSWW-euc
Awesome, thanks for the confirmation.
:robot: this is your friendly neighborhood build bot announcing test build 6.4.3.2329 ("remove logging")
Install in Zotero by downloading test build 6.4.3.2329, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".
I've removed the logging, can you verify autopin still works for you?
I'm getting this same issue as well. Occasionally keys get auto-pinned, but other times they don't. I enabled logging but get the same "component not initialized" error as described above. Tried downloading build 2323 as suggested to log pinning activity but I think the link no longer exists.
:robot: this is your friendly neighborhood build bot announcing test build 6.4.3.2422 ("more logging")
Install in Zotero by downloading test build 6.4.3.2422, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".
Thanks - I installed that version, and waited. My most common way of adding entries into Zotero is with Zotero Connector for Chrome. The issue is intermittent, so the first 5-10 papers I added since then were auto-pinned properly. Then, I just added one where it didn't auto-pin, so I just sent a support log: id F5L2IR3W-euc
I see a possible cause, but it's not an easy fix. Zotero is re-loading the main interface, and since that's where BBT starts up, that may throw things out of whack.
Gotcha. I'm not 100% sure what that means, but if it helps, I think I found some consistency with the behavior:
It means I have work to do.
Yikes - well I'm happy to help with testing at any point, just let me know.
I have an idea on how to fix this, but I'm waiting for feedback from the zotero devs.
:robot: this is your friendly neighborhood build bot announcing test build 6.7.1.2679 ("zotero-only test")
Install in Zotero by downloading test build 6.7.1.2679, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".
Hello,
I am still experiencing the same issue! Has this case been closed?
I need a debug log. Can't help you without a debug log.
On a note: still issue reappears intermittently but usually disappears after restarting Zotero. Ik you are interested I can post a debug log from time-to-time ?
~Not necessary at this time, thanks.~ yes please.
My autoPinDelay is not working now either. Debug log ID: BPBTS2H2-apse
@nowgabis can it be the case that autoPin stops working for you after you closed the last Zotero window but did not quit Zotero (not a cmd-Q quit), opened a new Zotero window, and then autoPin doesn't work anymore? That is currently a known problem. I'm working to resolve this but it requires a big overhaul to how BBT works. cmd-Q and starting Zotero should reliably fix it.
That makes sense, thank you!
This ought to be fixed in the last few releases.
Thanks. I'm fine to close and to reopen if the problem reappears.
I set
autoPinDelay: 5
, but the citation keys are currently not pinned (before they were).better sent as a log ID
``` Application: Zotero 6.0.5-beta.2+c510d9146 en-US Platform: MacIntel Intel Mac OS X 10.16 Addons: Zotero Citation Counts Manager (1.3.0, extension) Zotero LibreOffice Integration (6.0.0.SA.6.0.5-beta.2+c510d9146, extension) Zotero Word for Mac Integration (6.0.0.SA.6.0.5-beta.2+c510d9146, extension) Better BibTex for Zotero (6.4.3, extension) Settings: autoAbbrev = true autoPinDelay = 5 caching = false citekeyFold = false citekeyFormat = "[auth][year]" citekeySearch = false DOIandURL = "doi" platform = "mac" postscript = "if (Translator.BetterBibTeX) {\n if (reference.has.abstract) {\n reference.remove('abstract');\n }\n if (reference.has.note) {\n reference.remove('note');\n }\n if (reference.has.month) {\n reference.remove('month');\n }\n if (reference.has.keywords) {\n reference.remove('keywords');\n }\n if (reference.has.file) {\n reference.remove('file');\n }\n if (item.arXiv.id) {\n reference.add({name: 'arxivid', value: item.arXiv.id});\n if (!reference.has.journal) { \n reference.add({\n name: 'journal', \n bibtex: `{arXiv preprint: ${item.arXiv.id}}` \n }); \n }\n }\n}" Settings at default: ascii = "" asciiBibLaTeX = false asciiBibTeX = true autoAbbrevStyle = "" autoExport = "immediate" autoExportDelay = 5 autoExportIdleWait = 10 autoExportPathReplaceDiacritics = false autoExportPathReplaceDirSep = "-" autoExportPathReplaceSpace = " " automaticTags = true auxImport = false baseAttachmentPath = "" biblatexExtendedDateFormat = true biblatexExtendedNameFormat = false biblatexExtractEprint = true bibtexParticleNoOp = false bibtexURL = "off" cacheFlushInterval = 5 charmap = "" citeCommand = "cite" csquotes = "" exportBibTeXStrings = "off" exportBraceProtection = true exportTitleCase = true extraMergeCitekeys = false extraMergeCSL = false extraMergeTeX = false git = "config" import = true importBibTeXStrings = true importCaseProtection = "as-needed" importCitationKey = true importExtra = true importJabRefAbbreviations = true importJabRefStrings = true importSentenceCase = "on+guess" importUnknownTexCommand = "ignore" itemObserverDelay = 5 jabrefFormat = 0 jieba = false keyConflictPolicy = "keep" keyScope = "library" kuroshiro = false mapMath = "" mapText = "" mapUnicode = "conservative" parseParticles = true patchDates = "" postscriptOverride = "" preferencesOverride = "" qualityReport = false quickCopyEta = "" quickCopyMode = "latex" quickCopyOrgMode = "zotero" quickCopyPandocBrackets = false quickCopySelectLink = "zotero" rawImports = false rawLaTag = "#LaTeX" relativeFilePaths = false retainCache = false scrubDatabase = false separatorList = "and" separatorNames = "and" skipFields = "" skipWords = "a,ab,aboard,about,above,across,after,against,al,along,amid,among,an,and,anti,around,as,at,before,behind,below,beneath,beside,besides,between,beyond,but,by,d,da,das,de,del,dell,dello,dei,degli,della,dell,delle,dem,den,der,des,despite,die,do,down,du,during,ein,eine,einem,einen,einer,eines,el,en,et,except,for,from,gli,i,il,in,inside,into,is,l,la,las,le,les,like,lo,los,near,nor,of,off,on,onto,or,over,past,per,plus,round,save,since,so,some,sur,than,the,through,to,toward,towards,un,una,unas,under,underneath,une,unlike,uno,unos,until,up,upon,versus,via,von,while,with,within,without,yet,zu,zum" startupProgress = "popup" strings = "" stringsOverride = "" testing = false verbatimFields = "url,doi,file,ids,eprint,verba,verbb,verbc,groups" warnBulkModify = 10 warnTitleCased = false workers = 1 Zotero: export.quickCopy.setting = "bibliography=http://www.zotero.org/styles/ieee" Zotero.Debug.enabled: true Zotero.Debug.enabled at start: true LocaleDateOrder: mdy Total export workers started: 0, currently running: 0 ```