[GUI Plugin] FanFicFare

[JimmXinu]

New Test Version Posted

2023-03-21
- adapter_wattpadcom: Fix accidentally hardcoding a story in.
- adapter_ficbooknet: Fix for site change.

Originally Posted by JimmXinu

It looks like ficbook.net is serving it's pages with cache life set to 0 now, so the browser doesn't cache them.

Which means you can't use FFF's Browser Cache feature with it.

You might try one of the Proxy servers instead. FlareSolverr just had a new version come out...

I tried the new FlareSolverr v3.1.0--it has a windows executable version again with needing Docker--and there was also a site change for ficbook.net.

[HobeJung]

After updating the plug "FanFicFare" I can no longer download books. I put the link but the book does not download.

[JimmXinu]

Originally Posted by HobeJung

After updating the plug "FanFicFare" I can no longer download books. I put the link but the book does not download.

Moderator Notice
I've moved your post to the appropriate thread. Please use the existing threads for plugins. -- Jimm

There's an issue with the Wattpad site--a recent site change that prevents chapter URLs from working while story URLs containing /story/ still do.

There's a fix already up in the test version.

Otherwise, I will need at least a story URL that doesn't work for you before I can help.

[ownedbycats]

Is possible to collect an AO3 series description without an anthology?

[JimmXinu]

No, that's not part of the story metadata--it's only on the series page.

[ownedbycats]

I think I can pull it off with a replace_metadata using a seriesUrl conditional.

How would I regex to prepend an arbitrary HTML string to the actual description?

Alternately, if I create a custom entry, could I somehow set that to an arbitrary value based on a conditional? It would let me put it on the tittle page.

[JimmXinu]

Make a custom column, manually put the value in it, use the "Pass Calibre Columns into FFF" feature to feed it back into FFF.

[ownedbycats]

That works. I think a Series Description column would work for non-fanfic too.

Update: I added calibre_cust_seriesdescription to the AO3 titlepage_entries: (only site that has descriptions) and now the description is on the titlepage.

[ownedbycats]

New question. Is there a way to remove the extra linebreak here:



since there's a <p>, the <br /> isn't really necessary.

<b>Series Description:</b> <div>
<p align="justify" style="font-style: italic">blah blah blah</p></div><br />

<b>Summary:</b> <div class="userstuff">
              <p align="justify">blah blah blah</p>
            </div><br />

[archiveofourown.org]

titlepage_entries: seriesHTML,category,genre,language,characters,ships,status,datePublished,dateUpdated,dateCreated,rating,warnings,ao3chaps,numWords,publisher,calibre_cust_seriesdescription,description

[JimmXinu]

If you want to take responsibility for adding line break formatting to all entries, you could change titlepage_entry.

From the Custom Output wiki page:

## ${id}, ${label}, ${value}
titlepage_entry:<b>${label}:</b> ${value}<br />

It might work to change the br to have a class containing the id and then apply a CSS to that class to not have regular line break behavior:

## ${id}, ${label}, ${value}
titlepage_entry:<b>${label}:</b> ${value}<br class="te_${id}" />

add_to_output_css:
 br.te_seriesHTML { display: none; }

I haven't tested that beyond Calibre Edit book. It may not be that simple.

[jan2544213]

The new version works perfectly. Thank you so much!

[junni]

Hi Jimmy i had a novel in novelfullplus (i made the adapter based on yours) which i was updating, but the site went down. So in another site which has basically the same structure (novelnext.com), when i try updating the novel, it redownloads everything again, just to update the newest chapters. Is there a way for it to only download the newest chapters? I think i might need to change something inside the book maybe?
i'm happy to provide more info if you need.


Another question, when i'm downloading a long novel, some websites might give a 520 error during download. is there a way to resume the downloads instead of trying to redownload everything again?

[JimmXinu]

FFF stores the chapter URL in a <meta> tag in the header of each chapter file. When it doesn't match, FFF assumes it needs to be replaced.

You could try removing the <meta name="chapterurl" ... > tags from the epub before updating with the new site--if you are very confident that the chapters line up the same.

But it would be a lot safer to download from the new site as a different book. You could use a storyUrl personal.ini section to set first_chapter:X for the new URL to force FFF to always act as if you'd entered the URL with [X-] after it.

first_chapter is an undocumented feature, but we're already talking about unsupported sites, so why not.

Setting continue_on_chapter_error:true records failed chapters while continuing on. Error chapters will be replaced, if possible, on Update. Note that FFF will continue to try every chapter--so if starts failing at chapter 5 of 500, you may be waiting through failed 495 chapter attempts.

Setting a slow_down_sleep_time of a few seconds for the site may well help.

I've explained before how you can break up the download of long stories using the chapter range feature on the story URL.

(And please don't call me Jimmy.)

[junni]

Originally Posted by JimmXinu

FFF stores the chapter URL in a <meta> tag in the header of each chapter file. When it doesn't match, FFF assumes it needs to be replaced.

You could try removing the <meta name="chapterurl" ... > tags from the epub before updating with the new site--if you are very confident that the chapters line up the same.

But it would be a lot safer to download from the new site as a different book. You could use a storyUrl personal.ini section to set first_chapter:X for the new URL to force FFF to always act as if you'd entered the URL with [X-] after it.

first_chapter is an undocumented feature, but we're already talking about unsupported sites, so why not.

Setting continue_on_chapter_error:true records failed chapters while continuing on. Error chapters will be replaced, if possible, on Update. Note that FFF will continue to try every chapter--so if starts failing at chapter 5 of 500, you may be waiting through failed 495 chapter attempts.

Setting a slow_down_sleep_time of a few seconds for the site may well help.

I've explained before how you can break up the download of long stories using the chapter range feature on the story URL.

(And please don't call me Jimmy.)

Jimm, sorry, i don't know why, but i always read your name as Jimmy. Won't happen again.

About the solutions you mentioned, changing the the meta tag or removing, doesn't seem feasible, since it's a 2000+ chapter story. For the first chapter and chapter range solution, i would have to be constantly editing it, and it's troublesome since i have a lot of novels in this situation. (but it was good to know these options)

continue_on_chapter_error:true seems great, but for this situation would be cool if we could set some kind of buffer time before continuing.

"slow_down_sleep_time" seems the way to go. i currently have on 3, which i assume is 3 seconds. Maybe i should set it on 5.

[ownedbycats]

I think it's just "Jim" and the extra m is for his last name. (I'm not sure about the Xinu part.)