[GUI Plugin] FanFicFare - Page 690

Lys · Yesterday, 01:44 PM

I tried to update a single fic (with/without VPN) from AO3 and I got 525 error for both cases, as well.

Yesterday I managed to run the update for 5/6 fics at once without errors (the whole process was just slow).

Anyssia · Yesterday, 02:26 PM

If I'm not messing up, I use this under [archiveofourown.org] in personal.ini to make a ToC.

Code:

## AO3 chapters have 'date' available for each chapter.
## These can be used with custom output (see
## https://github.com/JimmXinu/FanFicFare/wiki/CustomOutput ) or with
## chapter_title_*_pattern settings.
## Examples for html & epub:
#<html>
#tocpage_entry:
# <a href="#section${index04}">${chapter}</a> ${date}<br />
#<epub>
tocpage_entry:
 <a href="file${index04}.xhtml">${chapter}</a> ${date}<br /><br />

It works for chaptered fics, but does anyone knows if there is a way to force Calibre/FFF to make a ToC even for one-shot fanfics, please?

(also, +1 with a 525 error on anthologies)

Subtext · Yesterday, 05:31 PM

I finally managed to update my anthologies by increasing the "slow_down_sleep_time" in ini, it takes ages to start and finish but I didn't get any 525 errors!

ownedbycats · Yesterday, 05:35 PM

I also had it go away, though no changes.

Anyssia · Yesterday, 05:44 PM

Quote:

Originally Posted by Subtext

I finally managed to update my anthologies by increasing the "slow_down_sleep_time" in ini, it takes ages to start and finish but I didn't get any 525 errors!

how far did you go? mine is on 4 at all time

beck_liz · Yesterday, 06:19 PM

Quote:

Originally Posted by Subtext

I finally managed to update my anthologies by increasing the "slow_down_sleep_time" in ini, it takes ages to start and finish but I didn't get any 525 errors!

I've been unable to download anything with FFF since Wednesday (though the one time I asked it only to update if there were new chapters was the only time I didn't get a 525 error). I changed this setting in .ini from 6.5 to 10, and it now takes awhile, but it works. 10 was a number I chose randomly. So thanks for mentioning that setting!

nan1923 · Yesterday, 06:57 PM

What worked for me as a work around for the 525 errors, add in the personal.ini:

browser_cache_path:C:\Users\...

under [archiveofourown.org] in epub:
use_browser_cache:true
use_browser_cache_only:true
open_pages_in_browser:true

and comment your login and password out, if you included that in the personal.ini. If you are logged in in browser that causes an error message.

With that you can set sleeptime to 0. I only get errors with anthologies with more then 40 fics then. If that happens, wait a few seconds and then reload those pages in browser and start download again.

The only thing not working with that for some reason are pictures. Those you need to add manually in the epub.

JimmXinu · Yesterday, 08:07 PM

Re: CloudFlare

I don't think there's anything specific we can do about it. Either it's CF doing it's thing, or it's a problem between CF and AO3, if cats' link is relevant.

FFF defaults currently has:

Code:

## AO3 is blocking people more aggressively.  If you download fewer
## stories less often you can likely get by with reducing this sleep.
slow_down_sleep_time:2

I can increase that if a larger number works better. Personally, I haven't seen this.

I don't usually recommend BrowserCache for AO3 because it doesn't work with login, but if it works...

Quote:

Originally Posted by Anyssia

It works for chaptered fics, but does anyone knows if there is a way to force Calibre/FFF to make a ToC even for one-shot fanfics, please?

FFF only writes a TOC if there's more than one chapter--that's currently hard coded.

I could add an option to force TOC generation if that's something that's useful to people. I'd need to review what it might do to epub update and anthology generation.

JimmXinu · Yesterday, 08:15 PM

Error log reported here show this specifically failing during login.

Does it work better without always_login:true? Or maybe it's worse on login-required stories?

Still nothing we can do to fix it, but it may be possible to avoid more.

bpothier · Yesterday, 09:10 PM

Not sure if this may apply to other adapters, but found the bug I mentioned a few posts back (using current test version in CLI mode makes adding numerous debug calls a bit easier)

Simple version: Stories that contain the word "author" in the Title break the "authfrom" code.

(This is relative to: adapter_storiesonlinenet.py around line 216)
Specifically, when the check of div "top-header" finds the word "author":

"if authfrom is None or 'author' not in str(authfrom)"

(actually from story title) it uses that for processing the "authfrom" to set "autorID", "authorUrl", etc... When in fact, those values do not exist in the "top-header" so later on when findStoryRow loops the authorUrl[0].. it is blank... and fails with "list index out of range".

Testing by forcing it to use the soup.find on 'footer' instead, will correctly process and set values.

I looked back and the other story that failed (that I had not dived into issue on) also contained the word "author" in title..

SFW test story: SOL /s/56768 "the-author"

JimmXinu · Yesterday, 10:47 PM

New Test Version Posted

2025-02-14
- adapter_storiesonlinenet: Remove some code that broke parsing when 'author' was in the title.

The SOL adapter was contributed by someone else in 2012. I don't read the site and only ever look at it when it's broken; so I've honestly no idea why it does what it does a lot of the time.

But I do remember that it's kind of brittle because the site is old and has three different 'faces', SOL, finestories and scifistories.

That bit of code doesn't appear to be doing anything useful anymore.

Yes, CLI is very useful for debug, I use it all the time. You might also look at this. Saves tons of network when testing/debugging.

Yesterday, 02:26 PM	#10337
Anyssia Member Posts: 24 Karma: 19112 Join Date: Aug 2012 Device: Kobo Libra2	ToC for one-shot fanfics If I'm not messing up, I use this under [archiveofourown.org] in personal.ini to make a ToC. Code: ## AO3 chapters have 'date' available for each chapter. ## These can be used with custom output (see ## https://github.com/JimmXinu/FanFicFare/wiki/CustomOutput ) or with ## chapter_title__pattern settings. ## Examples for html & epub: #<html> #tocpage_entry: # <a href="#section${index04}">${chapter}</a> ${date}<br /> #<epub> tocpage_entry: <a href="file${index04}.xhtml">${chapter}</a> ${date}<br /><br /> It works for chaptered fics, but does anyone knows if there is a way to force Calibre/FFF to make a ToC even for one-shot fanfics*, please? (also, +1 with a 525 error on anthologies)

Yesterday, 09:10 PM	#10345
bpothier Member Posts: 17 Karma: 10 Join Date: May 2020 Device: Kobo	SOL bug when title contains the word "author" Not sure if this may apply to other adapters, but found the bug I mentioned a few posts back (using current test version in CLI mode makes adding numerous debug calls a bit easier) Simple version: Stories that contain the word "author" in the Title break the "authfrom" code. (This is relative to: adapter_storiesonlinenet.py around line 216) Specifically, when the check of div "top-header" finds the word "author": "if authfrom is None or 'author' not in str(authfrom)" (actually from story title) it uses that for processing the "authfrom" to set "autorID", "authorUrl", etc... When in fact, those values do not exist in the "top-header" so later on when findStoryRow loops the authorUrl[0].. it is blank... and fails with "list index out of range". Testing by forcing it to use the soup.find on 'footer' instead, will correctly process and set values. I looked back and the other story that failed (that I had not dived into issue on) also contained the word "author" in title.. SFW test story: SOL /s/56768 "the-author" Last edited by bpothier; Yesterday at 09:50 PM. Reason: (added SFW story url)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[GUI Plugin] KindleUnpack - The Plugin	DiapDealer	Plugins	506	Yesterday 10:52 PM
[GUI Plugin] Open With	kiwidude	Plugins	403	04-01-2024 09:39 AM
[GUI Plugin] Marvin XD	Philantrop	Plugins	126	01-29-2017 01:48 PM
[GUI Plugin] KiNotes	-axel-	Plugins	0	07-14-2013 07:39 PM
[GUI Plugin] Plugin Updater Deprecated	kiwidude	Plugins	159	06-19-2011 01:27 PM

Yesterday, 01:44 PM	#10336
Lys Groupie Posts: 154 Karma: 721208 Join Date: Dec 2022 Location: Not in an English speaking country Device: (Too many) Kobo(s)	I tried to update a single fic (with/without VPN) from AO3 and I got 525 error for both cases, as well. Yesterday I managed to run the update for 5/6 fics at once without errors (the whole process was just slow).

Yesterday, 05:31 PM	#10338
Subtext Junior Member Posts: 4 Karma: 10 Join Date: Nov 2014 Device: Onyx boox Nova 2, Kindle Paperwhite 2, Kindle Voyage	I finally managed to update my anthologies by increasing the "slow_down_sleep_time" in ini, it takes ages to start and finish but I didn't get any 525 errors!

Yesterday, 05:35 PM	#10339
ownedbycats Custom User Title Posts: 10,026 Karma: 68889039 Join Date: Oct 2018 Location: Canada Device: Kobo Libra H2O, formerly Aura HD	I also had it go away, though no changes.

Yesterday, 06:57 PM	#10342
nan1923 Enthusiast Posts: 25 Karma: 140 Join Date: Jul 2022 Device: none	What worked for me as a work around for the 525 errors, add in the personal.ini: browser_cache_path:C:\Users\... under [archiveofourown.org] in epub: use_browser_cache:true use_browser_cache_only:true open_pages_in_browser:true and comment your login and password out, if you included that in the personal.ini. If you are logged in in browser that causes an error message. With that you can set sleeptime to 0. I only get errors with anthologies with more then 40 fics then. If that happens, wait a few seconds and then reload those pages in browser and start download again. The only thing not working with that for some reason are pictures. Those you need to add manually in the epub.

Yesterday, 08:15 PM	#10344
JimmXinu Plugin Developer Posts: 6,687 Karma: 4600391 Join Date: Dec 2011 Location: Midwest USA Device: Kindle Paperwhite(10th)	Error log reported here show this specifically failing during login. Does it work better without always_login:true? Or maybe it's worse on login-required stories? Still nothing we can do to fix it, but it may be possible to avoid more.

Yesterday, 10:47 PM	#10346
JimmXinu Plugin Developer Posts: 6,687 Karma: 4600391 Join Date: Dec 2011 Location: Midwest USA Device: Kindle Paperwhite(10th)	New Test Version Posted 2025-02-14 - adapter_storiesonlinenet: Remove some code that broke parsing when 'author' was in the title. The SOL adapter was contributed by someone else in 2012. I don't read the site and only ever look at it when it's broken; so I've honestly no idea why it does what it does a lot of the time. But I do remember that it's kind of brittle because the site is old and has three different 'faces', SOL, finestories and scifistories. That bit of code doesn't appear to be doing anything useful anymore. Yes, CLI is very useful for debug, I use it all the time. You might also look at this. Saves tons of network when testing/debugging.