[GUI Plugin] FanFicFare

[sallyhop1]

I have no idea how to find this thread to report an error. Can you direct me? Thanks!

[steltek]

Originally Posted by sallyhop1

I keep getting errors for Fanfiction.net downloads. I know Fiction Press/Fanfiction has been doing a lot of updates recently, so I figured that is probably the cause.

This is the error message I got tonight when trying to update a story previously downloaded:


The Procedure
iambeagle
The site fanfiction.net is blocking downloads. Site is disabled in this version of FanFicFare.
https://www.fanfiction.net/s/13714341/1/

I did the most recent Calibre update as well as the most recent plug-in update, but I'm still getting this error message.

Any help would be greatly appreciated. I know of several other readers who are getting the same error.

Thanks!
Sally

If you read back over the last 5-6 pages of this thread, you will see that Fanfiction.net has implemented a Cloudflare "under attack" status. As a result, FFF no longer works with Fanfiction.net. They (Fanfiction.net) are further in the middle of yet another server migration that is expected to last for 10 days from yesterday.

Whether this is a permanent issue or not is up in the air at this point. @JimmXinu and others are researching possible options, but a solution (if even possible) is not available at this time.

The current version of FFF thus has Fanfiction.net support disabled for now to prevent unnecessary server requests that won't work anyway.

Originally Posted by sallyhop1

I have no idea how to find this thread to report an error. Can you direct me? Thanks!

There is no need to report the error as it is already known and being worked on.

[ownedbycats]

What I am seriously confused about is how people see an error saying "Site is disabled in this version of FanFicFare" and think that Jim doesn't realize.

[JimmXinu]

New Test Version Posted

2021-01-14
- adapter_webnovelcom: Fixes for site changes. Closes #629

[ownedbycats]

A question that I'm asking here, mostly in order to not clutter up the Github thread:

I've mostly been updating my existing ffnet fanfics by downloading the latest chapter as HTML in FFDL, importing it into the existing ePub, and then editing things manually (e.g. updating the title page/ToC/Calibre metadata and some minor formatting).

Assuming that I keep the internal filenames consistent, will FFF be able to handle these kludged-together files in the future? (This is assuming that somehow normal downloading starts to works again, rather than the Web2Epub-as-intermediary thing mentioned on Github.)

While I'm here: is there a way to omit the numbers in the ToC if the chapter names actually begin with "Chapter x"?

[JimmXinu]

New Test Version Posted

2021-01-15
- adapter_fanficsme: do an extra fetch before login for cookie(?) Closes #633

[ownedbycats]

Originally Posted by ownedbycats

While I'm here: is there a way to omit the numbers in the ToC if the chapter names actually begin with "Chapter x"?

I found a chapter_title_strip_pattern. I think that might work if I can figure out how to edit it right.

[steltek]

FYI, I was just able to update 7 different stories, one at a time, using the last version of FFF that supported Fanfiction.net.

By coincidence, the Fictionpress Twitter site says they are in the final stages of the server migration and also mentions that a few site problems have been fixed and web services restored. So, it isn't for sure that it will last, but there is hope.

[ownedbycats]

I cleared out the Cloudflare-specific cookies for ffnet and didn't get a browser check. I'm going to tentatively say they might've removed the under attack mode.

EDIT: As well, installing an older version of FFF successes. My FFDL kludge-updates are also work.

[ownedbycats]

Originally Posted by ownedbycats

A day or two ago there was a glitch that resulted in users being sent to the wrong account page when logging in, showing another username and their full email (yeah, not good). I checked it out myself and it looked like the server was inappropriately serving up cached pages. It seems to have resolved itself.

I was actually right about it being a caching bug.

[Clem2605]

Well, I'm in France, so maybe there is a location thing, and I use the version 3.27.0 of FFF.

I wanted to try using FFF on ff.net one last time before updating to the version who doesn't support it.

I was just able to download more or less 10 FF, I did them 4 by 4, not wanting to risk anything, but it worked.
... But then For the last two it did work: "503 error".

There was only seconds between the two updates, and I'm trying the last two again, just to be sure, I'll be editing as soon as it's finished.

[ownedbycats]

503/520 errors are likely to be related to the current server migration going on.

[tricklem]

I went back to FFF version 3.27.4 and it is working for fanfiction.net again. I was able to update 5 stories. Of course, 2 of those I had to delete and re-download because I had updated them with ffdl and fff didn't recognize them, but once I deleted them and re-downloaded it was good!

Figured out how to overwrite, and updated everything including the missing data the ffdl doesn't populate.

[Ytierian]

Originally Posted by tricklem

I went back to FFF version 3.27.4 and it is working for fanfiction.net again. I was able to update 5 stories. Of course, 2 of those I had to delete and re-download because I had updated them with ffdl and fff didn't recognize them, but once I deleted them and re-downloaded it was good!

Figured out how to overwrite, and updated everything including the missing data the ffdl doesn't populate.

3.27.0 is also functioning for fanfiction.net now. Just did a few updates and a download on Calibre 4.23 without a problem.

[JimmXinu]

New Test Version Posted

2021-01-16
- Re-enable ffnet and bump up sleep times for same.
- ffnet fpcom, continue_on_chapter_error:true by default, increase sleep times.
- First rough version of reporting continue_on_chapter_error chapters.

This version reports when failed chapters included due to continue_on_chapter_error:true. I plan to improve the reporting and probably include 'marking' them as well.

I also plan to implement a more complex sleep system with a random component.

Easiest would be a simple min/max setup with a value randomly chosen between those limits, but a variable sleep proportional to the size of the last fetch appeals to my sense of elegance.