Quote:
Originally Posted by ownedbycats
Also, just for futureproofing: When 2025-01-01 rolls around, what will happen to any migrated unreads that have a 2024 #lastread? Will they also error?
|
Let's break it down:
1) 2024-01-01 works just fine here, so 2025-01-01 will work too. Like I said, maybe the problem is how the date was set (via Action Chains). When you set a datetime via python, you can choose to use a naive datetime or a timezone aware. My guess is that Action Chains uses a naive datetime object, but calibre adds the offset, putting it in the wrong year.
2) If you use the RG auto migrate feature, the books in your 'want to read' and 'reading' shelves will be moved to your 2025 goal in 2025-01-01. But you'll still need to change your #lastread date to 2025, since the plugin never touches your calibre library.