View Single Post
Old 09-27-2020, 08:52 AM   #1915
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 JDesat View Post
I just sent it to you in PM. I had to do it in 2 messages because it was too long for just one.
Thanks, that told me what was happening. And I'd actually seen it recently, but, but hadn't been able to reproduce it.

The problem is happening when the last read date isn't set for books marked as finished or being read. It looks like it is caused by using other functions in the plugin. The most likely one would be setting the reading status using either the "Update metadata in device library" or "Change Reading Status in device library". The "Store/Restore current bookmark" would probably also do it if the date isn't stored. It would also need two copies of the same book to be on the device.

The attached beta should fix this. I added some extra checks on the last date read to prevent the error. I have also turned on some extra debugging in case it doesn't solve the problem. That should give a better idea of what is happening if this doesn't fix it.

Last edited by davidfor; 10-07-2020 at 01:25 AM. Reason: Removed beta as it has been released.
davidfor is offline