Thread: Glo Display Calibre metadata comments in Glo details
View Single Post
Old 06-16-2016, 08:44 AM   #11
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 leftright View Post
Installed the test plugin.
logs attached with no change to comments, then a minor change to comments.

After a minor change the comments show up in the Glo synopsis tab. with several blank pages.

EDIT:
I noticed that there was 10's of blank lines in the html code, e.g.
<div>
blank
blank
blank
etc.

then Comments start;
I deleted all these 10's of blank lines in the html code and the comments now show up in my Glo, 7 pages worth in the synopsis tab.

Many thanks for your time.
Glad that it's sorted out. From the logs, it looks like the comment was in the database, just not being displayed. The only thing I can think is that there was something in the comment that the device didn't like and that stopped the comment from being displayed. I can't see what it was. All of the versions that I can pull from the logs and file are displaying with no problems. It probably means there was something either you removed when editing the comment, or calibre automatically cleaned up as you made another change.

One thing that would be good to check is if there is a stack dump file on the device. If something about the comment was causing an error, nickel might have written the stack at the time of the error. Can you look in the .kobo directory for files with the name "stack_nn.log" (the "nn" will be numbers). If there are any, they might help Kobo work out what was wrong.
davidfor is offline   Reply With Quote