[GUI Plugin] FanFicFare

[ThistleProse]

I am new to Calibre, and FanFicFare; I'm leaning towards this being an issue because AO3 was down earlier and maybe its glitching still? I did manage to download several stories and anthologies over the past several hours, but now I'm getting these errors. All the steps are going as usual to download (links are active, and opening in my browser, etc) so nothing is standing out to me as a reason beyond AO3 maybe being twitchy at the moment. If it is something I need to fix though, I'd love to do so lol.




Thanks for this awesome plugin. I love it.

[JimmXinu]

Originally Posted by Elaine T

My turn with an Ao3 issue. Anthology update on a series got a 403 error, with a 'another error occurred'.

Any AO3 403 Forbidden errors are almost certainly site or Cloudflare blocking.

I just got a 'Shields Up' Cloudflare page accessing AO3 in browser, so I'm pretty confident it's that. This has been happening on and off for years now.

FYI, use_archiveofourown_gay:true isn't enough this time.

See https://github.com/JimmXinu/FanFicFa...ache-feature-1 and https://github.com/JimmXinu/FanFicFare/issues/1348

[estherflails]

Hi. I've been using the browser cache method on Ao3 for a while now, but I noticed sometimes the embedded images from random sites didn't load in the browser. I think I may have managed to fix that issue now. Is there a way to fix the affected fics and download just the missing images by updating the fics, or would I have to overwrite them? Unfortunately I don't know which fics this happened to, or even which ones have pictures in them, I can only guess from the file size. (Is there maybe a way to add a tag to the fics that have images in them?)

[ownedbycats]

Originally Posted by estherflails

Hi. I've been using the browser cache method on Ao3 for a while now, but I noticed sometimes the embedded images from random sites didn't load in the browser. I think I may have managed to fix that issue now. Is there a way to fix the affected fics and download just the missing images by updating the fics, or would I have to overwrite them? Unfortunately I don't know which fics this happened to, or even which ones have pictures in them, I can only guess from the file size. (Is there maybe a way to add a tag to the fics that have images in them?)

You can delete affected chapters in Calibre's epub editor and updating will grab again without overwriting entire story.

[JimmXinu]

Originally Posted by estherflails

Is there a way to fix the affected fics and download just the missing images by updating the fics, or would I have to overwrite them? Unfortunately I don't know which fics this happened to, or even which ones have pictures in them, I can only guess from the file size. (Is there maybe a way to add a tag to the fics that have images in them?)

Without knowing which fics or doing anything to them? No. Overwrite is the only way I can think of.

The Quality Check plugin can help you find epubs with broken images:
Quality Check > Check ePub Structures > Check broken image links

I'm not keen on the idea of FFF trying to mark fics with images in.

You can look for images tags in your epubs with:
Quality Check > Search ePubs > <img with Scope HTML content checked.

[estherflails]

Originally Posted by JimmXinu

Without knowing which fics or doing anything to them? No. Overwrite is the only way I can think of.

The Quality Check plugin can help you find epubs with broken images:
Quality Check > Check ePub Structures > Check broken image links

I'm not keen on the idea of FFF trying to mark fics with images in.

You can look for images tags in your epubs with:
Quality Check > Search ePubs > <img with Scope HTML content checked.

I didn't know about this plugin, this seems perfect to figure out which fics need to be fixed. Thank you!

[ownedbycats]

Originally Posted by JimmXinu

Without knowing which fics or doing anything to them? No. Overwrite is the only way I can think of.

Does selectively deleting the chapters not download images again? I seem to recall doing that in past when FFF had a bug

[JimmXinu]

Originally Posted by ownedbycats

Does selectively deleting the chapters not download images again? I seem to recall doing that in past when FFF had a bug

Yes, deleting chapters should get FFF to attempt to download the images in those chapters again. But you have to know which fics to delete from, which was the crux of the question.


There are recent changes to how FFF records failed images should open the door to adding a feature to retry previously failed images in future. (IE, recording the failed img url.)

I didn't try to implement it at the time because it would only help with images that failed since the change was added -- and because I ran out of energy for image handling. Maybe I'll look into that this week.

[Droewyn]

Is it possible to set FFF so that it doesn't put "there are already [X] chapters" in the Status field? I really want that field to just read either In-Progress or Complete, and if I accidentally try to reupload an already-up-to-date fix I'd rather it just be ignored than throw a status.

Thank you!

[JimmXinu]

Originally Posted by Droewyn

Is it possible to set FFF so that it doesn't put "there are already [X] chapters" in the Status field? I really want that field to just read either In-Progress or Complete, and if I accidentally try to reupload an already-up-to-date fix I'd rather it just be ignored than throw a status.

To the best of my recollection, FFF doesn't put "there are already [X] chapters" in its status metadata entry. For most sites, it's only ever 'In-Progress' or 'Completed'.

It sounds like maybe you are talking about FFF's "Update/Overwrite Error Column" setting under the Custom Columns tab in FFF's settings?

But unless you are also setting that column with Status, that column shouldn't ever be filled with 'In-Progress' or 'Completed'.

[Droewyn]

Originally Posted by JimmXinu

To the best of my recollection, FFF doesn't put "there are already [X] chapters" in its status metadata entry. For most sites, it's only ever 'In-Progress' or 'Completed'.

It sounds like maybe you are talking about FFF's "Update/Overwrite Error Column" setting under the Custom Columns tab in FFF's settings?

But unless you are also setting that column with Status, that column shouldn't ever be filled with 'In-Progress' or 'Completed'.

Huh. I'm pretty sure that's not a setting I ever messed with. I'll poke around and see if I can separate it out.

[Droewyn]

Okay, I never noticed that you could scroll down in the Custom Columns tab, so I'd missed that setting. It looked like it defaulted to using the Status column for error messages, so I changed it. Thanks so much!

[ownedbycats]

Originally Posted by JimmXinu

Yes, deleting chapters should get FFF to attempt to download the images in those chapters again. But you have to know which fics to delete from, which was the crux of the question.


There are recent changes to how FFF records failed images should open the door to adding a feature to retry previously failed images in future. (IE, recording the failed img url.)

I didn't try to implement it at the time because it would only help with images that failed since the change was added -- and because I ran out of energy for image handling. Maybe I'll look into that this week.

Could new entry for status, perhaps be added to the error dialog? For example, "chapters updated, images failed."

[chrisric]

If I have been reading novel "ABC" on site "XYZ", 500 chapters in Calibre and site "XYZ" disappears forever, can I move the epub to a new FFF supported site without downloading the 500 chapters again?

Thanks.

-Chris

[JimmXinu]

Originally Posted by chrisric

If I have been reading novel "ABC" on site "XYZ", 500 chapters in Calibre and site "XYZ" disappears forever, can I move the epub to a new FFF supported site without downloading the 500 chapters again?

It is not feasible to keep chapters from one site and download new chapters from another to update the same book.

I would keep the epub you already for those chapters and start a new book for the story on the new site.

You can skip downloading old chapters from the new site with chapter range or first_chapter (and last_chapter) are undocumented settings equivalent to using a chapter range.