[GUI Plugin] FanFicFare

[JimmXinu]

Originally Posted by ownedbycats

Question: When I start downloading, i get a popup saying 'fetched metadata for 1/1.' There's a cancel button on it but I can't cancel it as it just whites out and goes not responding. Is there a way to cancel aside from wait?

Not really.

As I recall, the cancel is applied when the network request (or sleep) come back, but those are down inside the code without good ways to 'cancel'.

[slantybard]

I accidentally overwrote a ff book I had previously edited. Is there a way to undo that or find the old epub version? I assume not but thought I would ask prior to re-editing the book I downloaded. Thanks for any help or links (if there is one) that answers this question.

[JimmXinu]

When FFF deletes an epub to update it, it should be available in Calibre's "Restore recently delete" under the "Formats" tab.

Otherwise, pull it from backup? Maybe you have a device you put it on but haven't updated yet?

[slantybard]

Originally Posted by JimmXinu

When FFF deletes an epub to update it, it should be available in Calibre's "Restore recently delete" under the "Formats" tab.

Otherwise, pull it from backup? Maybe you have a device you put it on but haven't updated yet?

Thank you for the quick reply. I had no idea that function existed and it worked perfectly. Calibre is so powerful but hard to know all the options/capabilities.

[MidwestJen]

Originally Posted by JimmXinu

That looks like you didn't pre-cache the pages for the Browser Cache Feature.

I'm also getting this error. I do the cache preload by hand (vs the code doing it for me) for my FF . net stories. However, this only happens after a few days. For example, yesterday I ran an update of around 30 stories for various sites (including FF) and everything was fine. Today, I'm getting this:

browser_cache_path is not set, or directory does not contain a known browser cache type: 'C:\Users\xxxxx\AppData\Local\Mozilla\Firefox\Prof iles\9c97js1u.default-release\cache2'

If I close and reopen both calibre and Firefox, it will run through fine. Clearing the cache via Firefox doesn't help. This also happens with Edge. I tend to leave my laptop running all the time and only reboot when it either forces me to or I need to update something. So it's like the cache gets old (and perhaps smelly?) after a few days. This has been happening for approximately a month, but I wanted to be sure I had all the info first. Plus, while it's a pita to restart everything (mostly because I leave multiple gmail acct pages up as well and I end up having to log in to each one in a specific order or they'll try and all be the same ... seriously, wtf?) it is workable. I tend to ignore the error for a few days and skip those stories until I have a few before starting the cycle over again.

I haven't tried the test version, mostly because I wanted to see if you think it will fix the issue for mine as well. It's hard sometimes to know on this end what the changes will really do.

Thank you!!!

[JimmXinu]

Originally Posted by MidwestJen

I'm also getting this error. I do the cache preload by hand (vs the code doing it for me) for my FF . net stories. However, this only happens after a few days.
...
If I close and reopen both calibre and Firefox, it will run through fine. Clearing the cache via Firefox doesn't help. This also happens with Edge.

That suggests a few possibilities to me, but honestly, I'm just guessing.

• The does not contain a known browser cache type error only occurs for Firefox if there are no files in the dir matching the cache file name convention. Perhaps you have something running that (too) aggressively clears out temp files? Especially if you have similar results with Edge, a Chromium variant. I would expect restarting Firefox to be sufficient, however.
  
• The Firefox cache dir depends on browser profile. In my experience, most people don't bother setting up more than one profile, but perhaps you did and are switching which profile you pre-cache pages in?
  
• Is your disk full? I would expect you to have problems with basically everything then.
  
• Something is broken, corrupted or compromised on your computer?

The "Browser Simple Cache" change in the test version affects only Chromium browsers and, to my knowledge, only on Mac and Linux. I vaguely recall that some users saw the 'Simple Cache' in use on windows, but I never have.

[MidwestJen]

[*] I would expect restarting Firefox to be sufficient, however.

I'm almost positive that just restarting Firefox works, but I tend to just restart calibre as well. My last laptop was a potato, so it became habit years ago since it would bog down easily.

[*]The Firefox cache dir depends on browser profile. In my experience, most people don't bother setting up more than one profile, but perhaps you did and are switching which profile you pre-cache pages in?

No, I only have one profile. I've gone into the directory itself to confirm that it's only in that path.

[*]Is your disk full? I would expect you to have problems with basically everything then.

I currently have 420gb free.

[*]Something is broken, corrupted or compromised on your computer?

I suppose it's possible. This laptop is fairly new, less than a year old, so I wouldn't expect an issue quite yet (it only does basic searches to known mainstream sites and runs calibre, etc). I'm getting no other errors in my system, and the only other FFF error I've had recently had to do with the AO3 slow down.

As for the aggressive cleaning ... I do have it set to clean up the cache, history, etc after I close it each time. I just don't close it that often. And manually cleaning it doesn't seem to work (in terms of fixing the error). Other than that, I don't really run anything special [EDIT: I do run Norton and it does clean temp files, so I'll look into that], so I would expect more people to be running into this if that was the case. I should probably keep track of how long it's been since I've restarted each time to see if there's something there. At this point, I just know that one day it works, the next it doesn't, and restarting fixes it.

Yeah I have no idea either. If nothing else, if someone else does start having this issue, at least you have this information to add to it. I'll continue doing the restart thing until I stumble over a solution or it's worked out down the line.

Thank you!

[Amalthia]

Hello,

Does FFF use the split epub settings listed in the Calibre --> Settings --> Conversion --> Output options -- Epub Output: "Split files larger than"

I ask because I ran across two stories with chapters/parts longer than 260kb and they weren't split when FFF imported the story. I discovered this when the part would not display on my Pocketbook device.

I wasn't sure if I need to adjust my settings somewhere else, or if there is a bug?

Thanks,
Amalthia

[JimmXinu]

Originally Posted by Amalthia

Does FFF use the split epub settings listed in the Calibre --> Settings --> Conversion --> Output options -- Epub Output: "Split files larger than"

I ask because I ran across two stories with chapters/parts longer than 260kb and they weren't split when FFF imported the story. I discovered this when the part would not display on my Pocketbook device.

It does not. FFF doesn't use any part of Calibre Conversion when generating epubs--it's all FFF specific code.

I know Calibre Conversion has an option for splitting epub output, but I've never seen it needed. 260kb seems very small by today's standards. I don't know if I could introduce such a feature. FFF's paradigm is pretty firmly one chapter == one file.

Is this a common enough problem for people I should try?

The obvious answer is run Calibre Convert on it, but the resulting epub won't work with FFF Update anymore. Save a copy in another library before converting? Convert epub->epub, send to device, restore ORIGINAL_EPUB?

Here's an example of a chapter with more than 260kb, BTW:
https://www.fanfiction.net/s/1211580...-Weaver-Option

[Amalthia]

Originally Posted by JimmXinu

It does not. FFF doesn't use any part of Calibre Conversion when generating epubs--it's all FFF specific code.

I know Calibre Conversion has an option for splitting epub output, but I've never seen it needed. 260kb seems very small by today's standards. I don't know if I could introduce such a feature. FFF's paradigm is pretty firmly one chapter == one file.

Is this a common enough problem for people I should try?

I picked 260kb for my own settings. The story I ran across the part was over 300kb and that seemed break the epub. I was able to use the "Convert to Epub" option in Calibre to fix the two fics that had this problem.

I'm not sure if this is a problem for many stories?

Most author's tend to post short chapters, or break up fics longer than 20k into chapters. The story this happened with didn't have any chapter breaks and it was over 50k words long.

I download a lot of fic and I've rarely ran across this problem. I think what is annoying about this problem is you don't know there is a problem until you try and view the story on the device and discover half the fic is missing. I don't review the contents of the epub for every story I download.

Having said all that I'm not sure it's worth the effort to add a new feature to FFF to split "larger than" files into multiple file. If this was affecting 1 out of 100 stories it may be worthwhile, but I suspect it's more like 1 in 20k stories have this issue.

Thanks for the fast response!
Amalthia

[JimmXinu]

Originally Posted by Amalthia

I picked 260kb for my own settings. The story I ran across the part was over 300kb and that seemed break the epub. I was able to use the "Convert to Epub" option in Calibre to fix the two fics that had this problem.

260kb is the Calibre default:

Split all HTML files larger than this size (in KB). This is necessary as most EPUB readers cannot handle large file sizes. The default of 260KB is the size required for Adobe Digital Editions. Set to 0 to disable size based splitting.

So at one time, it was common.

Originally Posted by Amalthia

Having said all that I'm not sure it's worth the effort to add a new feature to FFF to split "larger than" files into multiple file. If this was affecting 1 out of 100 stories it may be worthwhile, but I suspect it's more like 1 in 20k stories have this issue.

1 in 20k may be an exaggeration--I can find 3 stories in my library of 6600 with chapters larger than that. But that's because chapters that long are remarkable and I remembered them. I expect 1 in 1-2k is probably about right.

How old is your reader? Do newer readers do better I wonder?

[ownedbycats]

My Kobo reader has frozen up on long files, mostly omnibus editions that put each book to 1 file.

[JimmXinu]

This particular issue isn't about the overall epub size, but the size of the individual html files inside.

[ownedbycats]

Yes, that's what I meant. Files of hundreds of pages make the Kobo freeze.

[theducks]

The quality check PI has a Check for oversized HTML files.
I find it easy to just open the book in the Editor and use the Split (here) Icon to do it at a logical place on the offending file .

A scene break fleuron is my first choice, leaving the mark at the END (to hint in is not done) of the section.

The Tools: Reports in either Calibre Editor or Sigil, will quickly show you the file sizes (double click the Name to Jump to that file)