Quote:
Originally Posted by JimmXinu
??? Anthologies don't even call the piece of code your first error report showed.
Please try the latest test version. If nothing else, unchecking the 'Marked added/updated books' option in FFDL config will bypass that code.
The new 'Mark Books' feature in the main calibre program makes marked books visible that way. calibre's had the marking ability for a long time, but it wasn't visible before. That's why I'm adding an option to not mark added/updated books. |
I've never activated the 'marked added/updated books' option in the configs, actually; there was no point to doing so when I sort my library by latest modified. Even so the yellow pin marker seems to be turning up for the last single book I add/update, doesn't happen with anthologies.
And you're right, anthologies updated this morning don't trigger that tuple error even though I could've sworn one of the anthologies I updated last night did trigger that.
Meanwhile, adding these stories triggered the tuple error message, after several updates for other stories that went off without a hitch.
http://archiveofourown.org/works/1001954,
http://archiveofourown.org/works/1002277 and
http://www.fanfiction.net/s/8576811/1/
Attached calibre debug log, but don't think I see anything unusual in it. :S I'll update to the test version for the later afternoon/evening spate of updates and see what happens.
ETA: Updated to the test version of FFDL, downloaded
a new fic, the tuple error still occurs. Didn't have calibre-debug on however, for which I'm sorry. I still can't seem to see any logic to which stories trigger the error and which don't.