[GUI Plugin] FanFicFare

[JimmXinu]

Originally Posted by quilledink

I copied directly from there into the defaults section of my person ini, then adjusted for my username (put ~ in front of /Library for it to automatically fill it in, but it generates as /Users/quilledink/)

As I recall, the ~ for home dir expansion does NOT work in INI files, eg browser_cache_path. defaults.ini shows full absolute path.

And, in fact, your error should be:

"browser_cache_path is not set, or directory does not contain a known browser cache type: 'C:\Users\user\AppData\Local\Mozilla\Firefox\Profi les\xxxxx.default\cache2'"
...except showing your browser_cache_path.

If you run debug mode, the debug log will show you where FFF is generating that error more precisely.

Originally Posted by quilledink

I did see in another thread a while back you suggested something about calibre's "safe_open_url" -- is that something that might work? (I'm not familiar enough with coding in general to know--I more tend to try and logic and research my way through stuff like this).

Unrelated.

Originally Posted by nephtys59

Stopped working this evening with error 428. Damn AO3!

Solved changing this value:
browser_cache_age_limit:-1

Let's hope it lasts.

Be aware that FFF does NOT honor the original cache time out. If you leave browser_cache_age_limit:-1, FFF will happily use hours/days/weeks old cache entries if it finds them.

Keep that in mind if you start seeing FFF not 'noticing' new chapters.

[nephtys59]

Originally Posted by JimmXinu

Be aware that FFF does NOT honor the original cache time out. If you leave browser_cache_age_limit:-1, FFF will happily use hours/days/weeks old cache entries if it finds them.

Keep that in mind if you start seeing FFF not 'noticing' new chapters.

Yes, I'm aware of that. I cleaned the browser cache BEFORE launching the update, so that the cache contained only the fics I wanted to update and I did this even before changing the setting from 4 to -1 but with setting 4 hour I got the error 428 anyway ... the ways of AO3 are mysterious, I believe.
I checked the fics anyway after update and all the chapters were there, even the newer ones. So I consider it a win.

[crashtest]

I'm pretty new to FanFicFare, but I did have it up and working for the past month or so. I'd routinely download and upload AO3 epubs using use_archiveofourown_gay. A few days go my settings suddenly stopped working and I've been trying to get it back online ever since. I've gleaned all the info I can from these threads and I'm still not sure what I'm doing wrong.

Is there something wrong with this personal.ini? When I use it, my browser is open, set to this profile, and logged into AO3. It creates a job, but then the job progress stalls until ~1 minute 20 seconds and fails, giving me error "HTTP Error in FFF 'Page not found or expired in Browser Cache (see FFF setting browser_cache_age_limit)'(428) URL" Thanks!

[defaults]
browser_cache_path: /Users/username/Library/Caches/Google/Chrome/Profile 13/Cache/Cache_Data

[archiveofourown.org]
is_adult: true
use_browser_cache:true
use_browser_cache_only:true
open_pages_in_browser:true
browser_cache_age_limit: 4.0

[girlikecupcake]

Originally Posted by crashtest

I'm pretty new to FanFicFare, but I did have it up and working for the past month or so. I'd routinely download and upload AO3 epubs using use_archiveofourown_gay. A few days go my settings suddenly stopped working and I've been trying to get it back online ever since. I've gleaned all the info I can from these threads and I'm still not sure what I'm doing wrong.

Is there something wrong with this personal.ini? When I use it, my browser is open, set to this profile, and logged into AO3. It creates a job, but then the job progress stalls until ~1 minute 20 seconds and fails, giving me error "HTTP Error in FFF 'Page not found or expired in Browser Cache (see FFF setting browser_cache_age_limit)'(428) URL" Thanks!

[defaults]
browser_cache_path: /Users/username/Library/Caches/Google/Chrome/Profile 13/Cache/Cache_Data

[archiveofourown.org]
is_adult: true
use_browser_cache:true
use_browser_cache_only:true
open_pages_in_browser:true
browser_cache_age_limit: 4.0

Have you tried other age limits? 4 is a good starting point but about 24 hours ago I had to bump it to 6 even though I knew for a fact things should be fine, and nephtys59 posted a short bit ago about using -1 on error 428 instead to force it to work. I just tested with a story with the cache_age set to 6 and it worked fine - it opened three pages in the browser (chapter index, first chapter, full story) then proceeded to download.

[quilledink]

Ah, thank you so much! I'd gotten errors with other browsers that had shown the full file path, even when using ~, so I'd just assumed that meant it was reading it okay.

And it's working now! Turns out the reason I was getting the "Chrome" error was because I'd messed up the openers_by_scheme changes as well--everything's working now! Thank you again!

Originally Posted by JimmXinu

As I recall, the ~ for home dir expansion does NOT work in INI files, eg browser_cache_path. defaults.ini shows full absolute path.

And, in fact, your error should be:

"browser_cache_path is not set, or directory does not contain a known browser cache type: 'C:\Users\user\AppData\Local\Mozilla\Firefox\Profi les\xxxxx.default\cache2'"
...except showing your browser_cache_path.

If you run debug mode, the debug log will show you where FFF is generating that error more precisely.


Unrelated.


Be aware that FFF does NOT honor the original cache time out. If you leave browser_cache_age_limit:-1, FFF will happily use hours/days/weeks old cache entries if it finds them.

Keep that in mind if you start seeing FFF not 'noticing' new chapters.