updating fics broke?

[pyroclastTech]

HEY EVERY !

i tried using this to update one of my fics, but it didnt even detect the EPUB files in the folder, let alone search for them, could anyone shed some light on this?

context: i made a test fic (public fic), downloaded it and one other id made through my 'works' tab. i then made a second chapter and attempted to retrieve the updated one with the second chapter (to ensure it worked, it didnt).

[nianeyna]

Thanks for the report! I suspect this might have to do with some changes I made to the epub parsing code recently. I'll create an issue from this discussion so that it's on my list of things to work on. If you get a chance it would be helpful if you could email me the exact file that you were expecting to be detected which wasn't - my email is in the contact section of the readme.

[pyroclastTech]

any luck so far?

[Probiotic8307]

Almost missed this from the title, but I am seeing the same issue with the "u: download latest version of incomplete fics" (Linux) when trying to download EPUBs. The same message as op:

0it [00:00, ?it/s]

I tested logged in, with several (unlocked) fics that are being actively updated. Nothing at all re-downloaded/updated, and there were no new log entries.

I had previously slightly modified the default naming convention to:

FileNamePattern={worknum}_{author} - {title}

[nianeyna]

Well, I absolutely went down several wrong paths here, but today I actually looked at the screenshot again and the lightbulb went off. The reason it's not working is because you put quotes around the file path. I'm going to push a change so that quoted filepaths are correctly recognized, but the feature isn't exactly broken, it just has bad input validation. I'm so sorry that took like a year to figure out...

[pyroclastTech]

hello! i'm so sorry, I neglected entirely to reply lol. i figured that one out, it may be a good idea to put a note on the github page about it as its slightly inconsistent across the program (unless there was a warning i didn't see lol). btw i love the program, it worked an absolute treat

…

On Sat, 18 Apr 2026 at 21:00, nianeyna ***@***.***> wrote: Well, I absolutely went down *several* wrong paths here, but today I actually *looked* at the screenshot again and the lightbulb went off. The reason it's not working is because you put quotes around the file path. I'm going to push a change so that quoted filepaths are correctly recognized, but the feature isn't exactly broken, it just has bad input validation. I'm so sorry that took like a year to figure out... — Reply to this email directly, view it on GitHub <#254?email_source=notifications&email_token=BMDBDCGS44BC34HFJMXPWJ34WPNEVA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGE2TSMJYUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-16615918>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BMDBDCFVNDZIHWGKAS2QLH34WPNEVAVCNFSM6AAAAACX6DFAKOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRRGU4TCOA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[nianeyna]

oh that's a relief, I'm glad it wasn't just broken for you all this time lol. No need for a note, I just fixed the behavior instead 😂