Upgrade StorageSlightly more verbosity in debugging log?
Hi,
As described here I just went through a frustrating troubleshooting experience related to the "TypeError: This parameter must be a string or Unicode object." error.
As explained in that thread, my experience would have been much less unpleasant if zotero would have included the citationID in the debugging output at the relevant point. This would have enabled me to quickly and definitely identify and resolve the offending citations.
Thus, I would suggest that this information is included in the debugging output in future versions of zotero.
Thanks.
Alternatively, an option to increase/decrease the verbosity of output would be even more awesome - reduces the clutter if not needed but can provide additional help if required. Maybe that already exists but my searches in documentation and forum were not fruitful.
As described here I just went through a frustrating troubleshooting experience related to the "TypeError: This parameter must be a string or Unicode object." error.
As explained in that thread, my experience would have been much less unpleasant if zotero would have included the citationID in the debugging output at the relevant point. This would have enabled me to quickly and definitely identify and resolve the offending citations.
Thus, I would suggest that this information is included in the debugging output in future versions of zotero.
Thanks.
Alternatively, an option to increase/decrease the verbosity of output would be even more awesome - reduces the clutter if not needed but can provide additional help if required. Maybe that already exists but my searches in documentation and forum were not fruitful.
See the preference key "debug.level"