[GUI Plugin] Reading Goal

[ownedbycats]

I already imported the new date yes:

[thiago.eec]

Originally Posted by ownedbycats

I already imported the new date yes:

I see. Then you the only way is to edit the JSON. The new date won't be picked up automatically by the plugin. The book was probably transferred to your 2025's goal, if you have the migration option enabled. Just remove it from 2025, after you edit the JSON (I know you are good at this ).

[ownedbycats]

An amusing glitch due to mixing up the orders

[Terisa de morgan]

OK, I've seen your message. It has worked for me because my book wasn't in the goal, neither it has been started, so it was simply adding a new record. Sorry for the misinformation

[Terisa de morgan]

Originally Posted by thiago.eec

Hi, Terisa.
Try the version attached.

I don't get the error now but, instead of getting a window to define the custom challenges, I get a message saying that the book cannot be added to the goal because of the year is invalid. And almost every operation gets the same error.... only adding to the annual goal is working.

[Comfy.n]

I'm pretty sure my case is hardly reproducible but anyway, I looked into my past calibre config folder backups, since they contain RG backups prior to the plugin built-in backup feature, to see if I could find something.

Here's what i found:

},
  "All": {},
  "general_info": {
    "autofill_done": true,
    "schema_version": 1.5,
    "timestamp": {
      "__class__": "datetime.datetime",
      "__value__": "2024-12-21T19:56:43.848078+00:00"
    }
  }
}
---
},
  "All": {},
  "general_info": {
    "autofill_done": true,
    "schema_version": 1.2,
    "timestamp": {
      "__class__": "datetime.datetime",
      "__value__": "2023-09-12T06:29:11.015881+00:00"
    }
  }
}
---
 },
  "general_info": {
    "autofill_done": true,
    "schema_version": 1.5,
    "timestamp": {
      "__class__": "datetime.datetime",
      "__value__": "2024-10-27T20:10:28.628124+00:00"
    }
  }
}

Out of 57 json backups with dates ranging from september/23 to december/24, only 6 of them contain the string "All". (I noticed that some have schema version 1.2 then at some point they use 1.5, but this doesnt seem relevant)

So I'm puzzled at why 51 dont have that node "All" and I've sent you the latest backup from october that didn't contain that and also the december one that triggered the error message upon trying to open the main plugin dialog.

Oh and I didn't edit manually the Json, last time I mentioned Json editing on MR was when I needed to transfer highlights from an epub opened outside the library.

I still think that the mentioned "Ctrl+A" action may be triggering this, but I was pretty sure that this was the first time I tried that, maybe not, lol.

[Terisa de morgan]

Originally Posted by thiago.eec

Hi, Terisa.
Try the version attached.

After reverting to the official version, I don't get the exception but the only entry in the menu that works is "Adding to Reading Goal" (Perhaps removing too, I've not tested).

[thiago.eec]

Originally Posted by Terisa de morgan

I don't get the error now but, instead of getting a window to define the custom challenges, I get a message saying that the book cannot be added to the goal because of the year is invalid. And almost every operation gets the same error.... only adding to the annual goal is working.

That's probably because some unfinished books were migrated to 2025's goal. When this warning is shown, the books will be marked in your calibre library. Just change their dates to 2025, and you'll be fine.

[thiago.eec]

Originally Posted by Comfy.n

I'm pretty sure my case is hardly reproducible but anyway, I looked into my past calibre config folder backups, since they contain RG backups prior to the plugin built-in backup feature, to see if I could find something.

Here's what i found:

},
  "All": {},
  "general_info": {
    "autofill_done": true,
    "schema_version": 1.5,
    "timestamp": {
      "__class__": "datetime.datetime",
      "__value__": "2024-12-21T19:56:43.848078+00:00"
    }
  }
}
---
},
  "All": {},
  "general_info": {
    "autofill_done": true,
    "schema_version": 1.2,
    "timestamp": {
      "__class__": "datetime.datetime",
      "__value__": "2023-09-12T06:29:11.015881+00:00"
    }
  }
}
---
 },
  "general_info": {
    "autofill_done": true,
    "schema_version": 1.5,
    "timestamp": {
      "__class__": "datetime.datetime",
      "__value__": "2024-10-27T20:10:28.628124+00:00"
    }
  }
}

Out of 57 json backups with dates ranging from september/23 to december/24, only 6 of them contain the string "All". (I noticed that some have schema version 1.2 then at some point they use 1.5, but this doesnt seem relevant)

So I'm puzzled at why 51 dont have that node "All" and I've sent you the latest backup from october that didn't contain that and also the december one that triggered the error message upon trying to open the main plugin dialog.

Oh and I didn't edit manually the Json, last time I mentioned Json editing on MR was when I needed to transfer highlights from an epub opened outside the library.

I still think that the mentioned "Ctrl+A" action may be triggering this, but I was pretty sure that this was the first time I tried that, maybe not, lol.

Hi, @Comfy.n

Now that you gave me the hint, I did find two "All" entries in over 250 backup files. The last one from Sep 2024. I have a guess of in which scenario this might occur. I'll investigate.

For now, you might want to manually delete this "All" entry from your current database. Then the plugin will work again.

[thiago.eec]

Originally Posted by thiago.eec

Hi, @Comfy.n

Now that you gave me the hint, I did find two "All" entries in over 250 backup files. The last one from Sep 2024. I have a guess of in which scenario this might occur. I'll investigate.

For now, you might want to manually delete this "All" entry from your current database. Then the plugin will work again.

Found the problem. It happens if you do a backup with 'All' selected in the year menu. It's fixed now.

I'll release a new version.

[thiago.eec]

Version 1.8.1 - 04 Jan 2025

- Bug fixes

[Comfy.n]

Originally Posted by thiago.eec

For now, you might want to manually delete this "All" entry from your current database. Then the plugin will work again.

Ah, this was a fix much simpler than I thought. By just removing that "All" line I could restore a working backup.

Glad you found what was triggering the issue!

Thank you and @ownedbycats for this great plugin.

[ownedbycats]

Small bug maybe: Going to another year of challenges and double-clicking one makes the pop-up come up. Both start and end dates undefined. Dont know what will happen if attempt to change one.

The buttons are disabled tjough.

[JSWolf]

Just installed this plugin and I've been setting up my books for the 2025 Reading Goal. I've just received a division by zero error. All I did was switch from 2025 to All and boom!

calibre, version 7.23.100
ERROR: Unhandled exception: <b>ZeroDivisionError</b>:division by zero

calibre 7.23.100  embedded-python: True
Windows-10-10.0.22631-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.22631')
Python 3.11.5
Windows: ('10', '10.0.22631', 'SP0', 'Multiprocessor Free')
Interface language: None
EXE path: C:\Program Files\Calibre2\calibre.exe
Successfully initialized third party plugins: DeACSM (0, 0, 16) && Gather KFX-ZIP (from KFX Input) (2, 19, 0) && DeDRM (10, 0, 9) && Package KFX (from KFX Input) (2, 19, 0) && Annotations (1, 17, 13) && Apple Books covers (0, 2, 0) && Barnes & Noble (1, 5, 6) && BookFusion Plugin (0, 8, 1) && Count Pages (1, 13, 6) && Diaps Editing Toolbag (0, 5, 0) && EpubCheck (0, 2, 5) && EpubMerge (3, 2, 0) && EpubSplit (3, 10, 0) && Favourites Menu (1, 3, 1) && Find Duplicates (1, 10, 9) && Hyphenate This! (0, 1, 3) && KFX metadata reader (from KFX Input) (2, 19, 0) && From KFX (2, 19, 0) && KFX Input (2, 19, 0) && Set KFX metadata (from KFX Output) (2, 13, 0) && KFX Output (2, 13, 0) && KePub Input (3, 6, 6) && KePub Metadata Reader (3, 4, 3) && KePub Metadata Writer (3, 4, 3) && KePub Output (3, 7, 2) && Kindle hi-res covers (0, 5, 1) && KindleUnpack - The Plugin (0, 83, 1) && Kobo Metadata (1, 9, 1) && Kobo Utilities (2, 17, 2) && KoboTouchExtended (3, 7, 3) && Modify ePub (1, 8, 5) && Quality Check (1, 13, 16) && Reading Goal (1, 8, 1) && Reading List (1, 15, 4) && ScrambleEbook (0, 6, 0) && TextDiff (1, 2, 4)
Traceback (most recent call last):
  File "calibre_plugins.Reading_Goal.main", line 3442, in update_year
  File "calibre_plugins.Reading_Goal.main", line 3255, in statistics_tree
ZeroDivisionError: division by zero

[JSWolf]

Originally Posted by Wiggo

I am very keen on the Reading statistics. Unfortunately, I'm on holiday at the moment and can't test it.

The only thing that bothers me when reading the description is the need of a new column again - Reading Progress. Couldn't there be an alternative with a simple read-column yes/no?

What would also be cool is to break down the books of a year by tags.

Your plugin would be a good replacement for Goodreads/StoryGraph.

If you use Kobo Utilities, you can get the Reading stats for these columns automatically. You would not need a Y/N column as you'd have Reading Progress set to 100%.