If you've been asked to provide a Debug ID (which is different from a Report ID) to help troubleshoot a problem, follow these simple steps:
For large amounts of output, “Submit to Zotero Server” may return an error. If so, click “Open about:config” in the Advanced pane of the Zotero preferences, search for extensions.zotero.debug.store.submitSize, double-click it, and reduce its value to “500000”. Then try to submit the output again.
If you'd like to follow Zotero's debug output in real-time, you'll need to enable debug output and start Firefox or Zotero from the command line.
Close Firefox or Zotero Standalone, and then restart it via the command line:
You should see debug output in the console as Zotero starts.
To capture output for a particular action (e.g., for a translator save attempt), press Cmd-K in the Terminal to clear all previous output before performing the action and then copy the complete output immediately afterwards.
If you receive the message “Command not found” in the Terminal, the location of Firefox on your system may be slightly different, or you may have entered the above line incorrectly. Ctrl-click on the icon you use to open Firefox and select Show in Finder. Look at the name of the Firefox application and the folder it is in. Replace “Firefox” in the line above with the name you see in the Finder. If Firefox is not located in the Applications folder, press Command-I and look at the “Where:” field to see the full path, and replace “/Applications” in the above line with that path. If there are any spaces in the path or app name, you'll need to surround the entire path with quotation marks. For example, if Firefox is named “Firefox 24”, you might use this line (quotation marks included):
"/Applications/Firefox 24.app/Contents/MacOS/firefox-bin" -ZoteroDebug
If you receive the message “dyld: unknown required load command 0x80000022 Trace/BPT trap” in the Terminal, use this command instead:
arch -i386 /Applications/Firefox.app/Contents/MacOS/firefox-bin -ZoteroDebug
Note: Real-time debug output on Windows slows down Zotero.
Close Firefox or Zotero Standalone, and then restart it via the command line:
You should see debug output in the Browser Console (Firefox) or text console (Standalone) as Zotero starts.
To copy output to the clipboard in Firefox, after performing the relevant action (e.g., saving via a translator), right-click within the console and choose Select All, and then right-click again and choose Copy.
To copy output in Standalone, select text and right-click to copy it.
If you cannot locate Firefox or Zotero Standalone, find an existing shortcut to Firefox/Zotero Standalone (e.g. on your desktop or in the Start menu), right-click it, select Properties, make sure the Target field is selected, and copy it to the clipboard by pressing Ctrl-C. Click Cancel to close the shortcut window. Back in Start→Run, clear the field and paste in the clipboard by pressing Ctrl-V. At the end of the field, after the second quotation marks, add a space followed by '-console -ZoteroDebug' (without quote marks).
Close Firefox, and then restart it via the command line, adding the -ZoteroDebug command-line flag.
You should see debug output in the console as Zotero starts. After performing the relevant action (e.g., saving via a translator), immediately copy the complete content to the clipboard.
To enable Zotero debug output permanently, set extensions.zotero.debug.log to true in about:config, accessible from the Firefox address bar or the Advanced pane of the Zotero preferences, and then start Firefox or Zotero from the command line.