[GUI Plugin] FanFicFare

[Ealdwulf]

Originally Posted by JimmXinu

Log indicates you have open_pages_in_browser:true. Go turn off open_pages_in_browser and try it again.

When I added to code to skip login when open_pages_in_browser:true, I should have anticipated users leaving that on and only turning off use_browser_cache.

Turned it off and it worked. Thank you!

I had honestly forgotten that I had that turned on.

[JimmXinu]

New Test Version Posted

2025-06-07
- Add use_flaresolverr_session and flaresolverr_session settings for #1211
- Include Accept:image/* header when requesting an image url, thanks bellisk
- Skip OTW(AO3) login when open_pages_in_browser AND use_browser_cache AND use_browser_cache_only

[chicleeblair]

Seems fixed! Thank you for being so on the ball.

[Tharos]

Yesterday I used FFF to import fiction from the-sietch.com for the first time. I noticed that the titles are not captured correctly if there is a tag for a series.

Example:
Title on the website: Battletech Clover Spear - The War of 3056 (Battletech AU)
Title captured by FFF: BattletechClover Spear - The War of 3056 (Battletech AU)
URL: https://www.the-sietch.com/index.php...tletech-au.76/

Battletech, as a tagged series, does not belong to the title. They should therefore either be ignored or entered as a category, tag, etc.

Addition:

If I import https://www.the-sietch.com/index.php...tletech.10785/, the following is entered as a comment:

{ "lightbox_close": "Close", "lightbox_next": "Next", "lightbox_previous": "Previous", "lightbox_error": "Der angeforderte Inhalt kann nicht geladen werden. Please try again later.", "lightbox_start_slideshow": "Diashow starten", "lightbox_stop_slideshow": "Diashow stoppen", "lightbox_full_screen": "Vollbild", "lightbox_thumbnails": "Vorschaubilder", "lightbox_download": "Download", "lightbox_share": "Teilen", "lightbox_zoom": "Zoom", "lightbox_new_window": "Neues Fenster", "lightbox_toggle_sidebar": "Toggle sidebar" } <div class="bbImageWrapper js-lbImage" data-lb-caption-extra-html="" data-lb-sidebar-href="" data-single-image="1" data-src="https://images-wixmp-ed30a86b8c4ca887773594c2.wixmp.com/f/0cda10d3-bbe2-4050-82d1-43a26a0d8ccb/dfviclw-757aaef0-d58f-41fa-9ada-41322a14aa83.jpg?token=eyJ0eXAiOiJKV1QiLCJhbGc

[JimmXinu]

New Test Version Posted

2025-06-08
- Py2 fix for split BG jobs, closes #1214

[Lys]

Hi

After the last update (4.46), the progress bar seems to be broken.
The plugin is working correctly, and it updates (at least from AO3 & mirrors) correctly, but the progress bar remains at 1% all the way through.

It's a minor thing because otherwise everything seems to be working correctly.

[JimmXinu]

New Test Version Posted

2025-06-08
- Py2 fix for split BG jobs, closes #1214
- Fix xenforo2 prefixtags, some still using tags in title
- alternatehistory needs at least cloudscraper now, it seems.

Originally Posted by Tharos

Yesterday I used FFF to import fiction from the-sietch.com for the first time. I noticed that the titles are not captured correctly if there is a tag for a series.

Fixed.

Originally Posted by Tharos

If I import https://www.the-sietch.com/index.php...tletech.10785/, the following is entered as a comment:

I only see that with keep_summary_html:false
That is the content of an embedded <script> tag for the image light box. So, technically, that is what's there.

Without keep_summary_html:false the default description_limit is exceeded before it actually gets to the text.

The html removal code is really old, I want to look at it for a bit before deciding if I want to strip out embedded <script> tags, which don't appear to be common.

You could address this by keeping HTML summary for this one, but would still need a longer limit:

[https://www.the-sietch.com/index.php?threads/i-caesar-battletech.10785/]
keep_summary_html:true
description_limit:3000

Or given how non-descriptive that description is, set your own:

[https://www.the-sietch.com/index.php?threads/i-caesar-battletech.10785/]
replace_metadata:
 description=>^.*$=>This is the description of that story...

[JimmXinu]

Originally Posted by Lys

After the last update (4.46), the progress bar seems to be broken.
The plugin is working correctly, and it updates (at least from AO3 & mirrors) correctly, but the progress bar remains at 1% all the way through.

I've not noticed that, and FFF shows a progbar at different times. When exactly do you mean?

[Lys]

Originally Posted by JimmXinu

I've not noticed that, and FFF shows a progbar at different times. When exactly do you mean?

In Calibre "Job" view, after selecting the fics I want to update and then running FFF in "update EPUB if new chapters", it shows the progress like this, going from 1% to 100% all in one go:

[JimmXinu]

Originally Posted by Lys

In Calibre "Job" view, after selecting the fics I want to update and then running FFF in "update EPUB if new chapters", it shows the progress like this, going from 1% to 100% all in one go:

Because the adapter for AO3 downloads the entire text in one request (by default) and then splits it into individual chapters, it can process after that much more quickly.

So I see a 1% -> 100% jump with one story download. But with several, I do see the job progbar advance as expected.

Have you changed the new BG job settings on the FFF Config Other tab?

[Lys]

Originally Posted by JimmXinu

Because the adapter for AO3 downloads the entire text in one request (by default) and then splits it into individual chapters, it can process after that much more quickly.

So I see a 1% -> 100% jump with one story download. But with several, I do see the job progbar advance as expected.

Have you changed the new BG job settings on the FFF Config Other tab?

Umh... I haven't changed anything in the default setting (I see everything flagged in the "Other" tab, is this the correct set-up?).
I retried with just two fics, but the behaviour has been the same 1% to 100% when the job was completely finished.

As I said, it's not a big problem since the update is working correctly anyway, and if others do not experience it, I'll write it off as something in my setting that is causing this

[w4tchdoge]

Hi, I updated FFF to 4.46.0 today and the only thing I changed after the update is disabling the update reconsolidation since I like the idea of separating updates based on the site.

About 2 hours ago I set FFF to update the fanfic I read via the "Get Story URLs from Email" feature, and let it run in the background while I was preoccupied with doing other things. I came back to Calibre about an hour and a half later and clicked the "Yes" option on the library update confirmation box only to get an error like this for the works in that library update and the ones after it. From the error details mentioning a FileNotFoundError and that the file was in the temp directory I assume something changed with how FFF handles temp files, because I'm certain I've left library updates hanging on the confirmation box for much longer on v.4.45.0 (e.g. setting FFF updating before I leave for university and clicking "Yes" when I come back 4-10 hours later).

I'd like to know if this is something that can be fixed/you plan to fix, or whether I'm gonna have to learn to pay more attention to FFF library updates from now on.

[w4tchdoge]

Unrelated to my previous post, but I'm also getting a 'NoneType' object has no attribute 'get_text' error on AO3 private works, even though I have my username and password in my ini file.

[ownedbycats]

Originally Posted by w4tchdoge

Unrelated to my previous post, but I'm also getting a 'NoneType' object has no attribute 'get_text' error on AO3 private works, even though I have my username and password in my ini file.

Are you using use_archive_transformativeworks_org? It doesn't have ability to login. use_archiveofourown_gay does.

[JimmXinu]

Originally Posted by w4tchdoge

Hi, I updated FFF to 4.46.0 today and the only thing I changed after the update is disabling the update reconsolidation since I like the idea of separating updates based on the site.

Apparently I didn't test that option well enough; I see that happen, too.

Should be able to address it today.

EDIT: I suggest re-enabling the reconsolidate option in the meantime.