[GUI Plugin] FanFicFare

[JimmXinu]

New Test Version Posted

2026-09-08
- adapter_ficbooknet: Fix author for site change

[JimmXinu]

New Test Version Posted

2026-09-09
- adapter_literotica: Fix for pagination links change, thanks akshayrangnekar(#1411)

[ownedbycats]

Has anybody found any sort of pattern to what will trigger AO3 to start giving 525 errors? It seems to be random to me. Even when downloading several stories at once I get the error on just one or two.

[Amalthia]

Hi,

Today I downloaded a story into Calibre and the fandom didn't populate my tag column and no custom cover was selected for the fandom.

I'm not sure if regex is failing or the order of my replace_metadata is messing things up, or something else I have not considered is happening.

Here is the URL: https://archiveofourown.org/works/92343266
Here is the fandom information of the story in the above URL:
魔道祖师 - 墨香铜臭 | Modao Zushi - Moxiang Tongxiu & Related Fandoms

Here are my generate cover settings and replace metadata settings.

generate_cover_settings:
 ${category} => 陈情令 | The Untamed => Untamed
 ${category} => 魔道祖师 - 墨香铜臭 | Módào Zǔshī - Mòxiāng Tóngxiù => Untamed
replace_metadata:
 fandoms=>.*陈情令 \|\ The Untamed.*=>陈情令 | The Untamed
 fandoms=>.*魔道祖师 - 墨香铜臭 \|\ Módào Zǔshī - Mòxiāng Tóngxi.*=>魔道祖师 - 墨香铜臭 | Módào Zǔshī - Mòxiāng Tóngxiù
 fandoms=>.*魔道祖师 - 墨香铜臭 \|\ Modao Zushi - Moxiang Tongxi.*=>魔道祖师 - 墨香铜臭 | Módào Zǔshī - Mòxiāng Tóngxiù
 fandoms=>(魔道祖师 - 墨香铜臭 \|\ Módào Zǔshī - Mòxiāng Tóngxiù)=>\1\,陈情令 | The Untamed

I'd appreciate any and all help to solve this mystery.

Thanks,
Amalthia

[JimmXinu]

Originally Posted by Amalthia

Today I downloaded a story into Calibre and the fandom didn't populate my tag column and no custom cover was selected for the fandom.

Using your posted code, I see a GC cover selected and "陈情令 | The Untamed" added to fandoms (and therefore category by default).

If something is wrong, I don't think it's in the parts you posted.

[Amalthia]

Originally Posted by JimmXinu

Using your posted code, I see a GC cover selected and "陈情令 | The Untamed" added to fandoms (and therefore category by default).

If something is wrong, I don't think it's in the parts you posted.

Thanks for reviewing. I'll go through the rest of my code and see if there is something I missed.

Thanks!
Amalthia

[Amalthia]

Originally Posted by JimmXinu

Using your posted code, I see a GC cover selected and "陈情令 | The Untamed" added to fandoms (and therefore category by default).

If something is wrong, I don't think it's in the parts you posted.

I found the solution:

In exclude_metadata_pre: I had listed

fandoms=~.*fandom.*

so when the fandom tag listed "related fandoms" it excluded the entire tag and that messed up my generate cover too.

Best Regards,
Amalthia

[ernand]

Originally Posted by ownedbycats

Has anybody found any sort of pattern to what will trigger AO3 to start giving 525 errors? It seems to be random to me. Even when downloading several stories at once I get the error on just one or two.

From my experience, it seems to be server-side. I literally had a story give off the 525 error, then immediately tried again and it worked. Just wait a few minutes, then download it. IF you can't wait, you can use the cache method. It works 100% of the time.

[ernand]

Originally Posted by JimmXinu

No, FFF doesn't have a way to save the images resized using the <img> tag width and height.

FFF, by default, resizes to fit inside the image_max_size setting, preserving aspect ratio.

Considering the size different between web pages and book readers (FFF's primary target), and that I believe most ereaders scale images down to fit their screen, I don't see a lot of value in the <img> tag width and height.

I have, however, been considering increasing the default image_max_size from the current 580, 725. Which was taken from the Nook I used Back in the Day. I've been using 2500, 2500 at least since I switched to Kobo-KOReader.

I would really welcome the switch from 580 to 2500.
A lot of detail is lost on the 580, especially with LONG images; even if they are 500 in width, due to a long height, they become even smaller.

I know of no_image_processing:true, which shuts down all FFF image processing; I just want to skip the resize aspect of the processing. Or at least a threshold option to only resize REALLY big images.

[JimmXinu]

New Test Version Posted

2026-09-11
- Increase default image_max_size to 2500, 2500
- epub update: Don't strip h2/h3 tags that aren't chapter titles. Thanks, kitoma (#1412)

[whiteowl]

Failed to download from ficbook.net
Error: 'NoneType' object has no attribute 'text'

Settings for the site are:

[www.ficbook.net]
use_browser_cache:true
never_make_cover:true

The cache folder set correctly, just checked.

What else can be done to localize the issue?

[JimmXinu]

Story URL demonstrating the problem is always a good idea. So is a debug log.

Do you have the latest test version? There was fix for a site change a week ago.

[whiteowl]

Originally Posted by JimmXinu

Do you have the latest test version? There was fix for a site change a week ago.

I had an issue with the official version - 4.61.0. After updating to a "test one" 4.61.3 the issue disappeared.

[chicleeblair]

I have the latest/test version, and I'm having to re-enter my login details with every adult download from AO3--it seems like multiple times, but that may be older chapters I haven't updated yet--When I started trying to update things, I had the wrong password in my personal.ini, but I fixed that. I'm not using ".gay" or browser_cache. (Although, I have noticed that on the browser, .gay won't log me in.)

[culytera]

Originally Posted by chicleeblair

I have the latest/test version, and I'm having to re-enter my login details with every adult download from AO3--it seems like multiple times, but that may be older chapters I haven't updated yet--When I started trying to update things, I had the wrong password in my personal.ini, but I fixed that. I'm not using ".gay" or browser_cache. (Although, I have noticed that on the browser, .gay won't log me in.)

Do you have always_login set to true?