Quote:
Originally Posted by ownedbycats
Also, if you try to update immediately after the update is posted, sometimes the chapter index on the first chapter isn't updated yet and it fails. check_next_chapter:true may help.
|
I usually have that option set. However, it wasn't necessary in this test case as the chapter was already on the FFN server (I was able to update it in my virtual machine test installation, where I keep a limited number of fics that update semi-frequently in case I need to test a problem) before I tried it on the updated machine.
Quote:
Originally Posted by JimmXinu
The error says it's failed on the first chapter, which your posted logs don't list as found in the cache:
"fanficfare.exceptions.HTTPErrorFFF: HTTP Error in FFF 'Page not found or expired in Browser Cache (see FFF setting browser_cache_age_limit)'(428) URL:'https://www.fanfiction.net/s/13051824/1/New-Blood'"
You haven't been skipping step 3 have you? "Navigate in your browser to chapter 1 of the the story you want to download."
https://github.com/JimmXinu/FanFicFa...erCacheFeature |
No, sorry about that. I always start with the link for chapter one to get it in the browser cache, then jump to the last existing chapter before going to the new updated chapter(s). I've tried to many different things that I guess I grabbed the wrong log.
Before, it simply wasn't working at all. I ended up fully removing Calibre (including the hidden folders), reinstalled it, and reinstalled the FFF plugin. Even went so far as to restore the library from backup as well as to try to export the existing library, to create a new library, and import the files back in to it. The existing epubs are all readable in Calibre, and there doesn't appear to be anything wrong with any of them.
Now, I've reached the point that I can at least delete an existing fic and download it again in its entirety with FFF.
However, when I try to update an existing fic in the library to add a chapter, it flags all existing chapters between chapter one and the existing end of the fic as bad chapters because they are not present in the cache and replaces each of them with a bad chapter flag (unless I page through the entire fic). These were stories that were all downloaded and updated using FFF. It does the same thing whether you try to update it using the FFF button, or by clicking the down arrow and entering the URL.
At this point, you don't have to waste any more of your time on it as I've run out of fics that need updates so I can't get another log. I'll take another jab at it once I get some additional fics on FFN that need to be updated and, if I'm still having the same problem, will post the correct log next time.