Quote:
Originally Posted by steltek
Are you getting this error when trying to update a fic soon after receiving an email notification from FFN?
|
No such luck, I'm afraid. My test fic was one that updated days and days ago. The copy in Calibre was 4 chapters and the one online was 5. The fifth chapter was definitely there - I could click to it manually in the browser and WebToEpub would gather it up.
I suppose that's one advantage of only trying to do this once a week or so, rather than immediately whenever a fic is updated.
And no, I'm not running any sort of cache cleaner. As part of ensuring that I was using the correct folder, I'd open it up to see what there, refresh after clearing the cache, then refresh again after loading the chapters. I wanted to ensure that the folder was emptying and then getting new files.
I tried your suggestion about "check next chapter" and... it's made me very confused.
So I'm testing with four different fics now: two that aren't in Calibre at all and two that are in Calibre, but have at least a couple of new chapters online.
With totally new fics, I get the same error as I mentioned before: can't find the page in cache. This happens whether checking next chapter is true or false.
With existing fics, I'm now getting a different error: I'm told that the fic already has X chapters, where X is the number of chapters in the copy in Calibre. It's not the number of chapters that are online (and which I've loaded). I'm getting this error now whether "check next chapter" is true or false.
These aren't compatible errors! In order to determine that the fic already has a certain number of chapters, FFF must have found the pages in cache, right? Granted, it's not finding all the pages because it's got the number wrong, but this strongly implies that it's locating some chapter pages. But when it comes to completely new fics, it can't find anything?
Ergo, I'm very confused. I'm hopeful that the "already has x chapters" error can be linked back to something I've done wrong and can fix.