Thread: [GUI Plugin] Annotations
View Single Post
Old 05-04-2019, 10:45 PM   #604
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by TGSET View Post
Hello,
I just got a new kobo clara hd and I'm trying to duplicate my (dead) glo. I think I have all my custom columns but the annotation plugin gives an error on fetch. I've selected a custom "annotations" column as the destination. I admit I haven't tried the default "append to Comments" method.

ERROR:

Traceback (most recent call last):
File "calibre_plugins.annotations.action", line 311, in fetch_device_annotations
File "calibre_plugins.annotations.action", line 1052, in process_selected_books
File "calibre_plugins.annotations.action", line 137, in add_annotations_to_calibre
File "calibre_plugins.annotations.annotations_db", line 180, in annotations_to_html
File "calibre_plugins.annotations.annotations", line 200, in to_HTML
TypeError: 'NoneType' object is not callable

The updated kobo driver finds device data and transfers it into my other custom columns fine. Suggestions?
Is there any reason you stripped the rest for the error details? There should have been lines at the start that show the version of calibre being run and the versions of each plugin installed. This isn't just an idle question...

That looks like either you are running an older version of calibre. The plugin was recently changed to support changes in calibre this broke the compatibility with older versions of calibre. Updating calibre will fix this.

But, the change to the plugin was simple to do to support older versions of calibre. I have release version 1.9.1 of the plugin. It should support most older versions of calibre. But, I recommend updating everything. If there are issues with older versions of calibre, I am more likely to remove support from them in the plugin than try to fix the plugin. If anyone is stuck on older versions of calibre for some reason, the older versions of the plugin are available on the GitHub releases page.
davidfor is offline   Reply With Quote