[GUI Plugin] FanFicFare

[JimmXinu]

Originally Posted by vehf263

Hello!
Can I ask you a question here?
Thank you.

Assuming you mean the same question you sent to my email, you use FanFicFare CLI.

This thread is for the FanFicFare Calibre Plugin. Most users here are not going to know much about Python CLI issues.

You'll get better results from the google group I sent you the link for.

[JimmXinu]

New Test Version Posted

2024-05-07
- adapter_forumquestionablequestingcom:Switch to BaseXenForo2ForumAdapter

QQ is currently down for transition to XF2 forum software. Posted test version worked on the public test bed, so hopefully it will work when the site comes back up.

[gthesob]

Originally Posted by JimmXinu

New Test Version Posted

2024-05-07
- adapter_forumquestionablequestingcom:Switch to BaseXenForo2ForumAdapter

QQ is currently down for transition to XF2 forum software. Posted test version worked on the public test bed, so hopefully it will work when the site comes back up.

So far so good!

[kagekarasu]

Originally Posted by JimmXinu

New Test Version Posted

2024-05-07
- adapter_forumquestionablequestingcom:Switch to BaseXenForo2ForumAdapter

QQ is currently down for transition to XF2 forum software. Posted test version worked on the public test bed, so hopefully it will work when the site comes back up.

I used the test version to update some fics from qq, it work but it is extremely slow, it took me around 8 min for 6 chapters, my internet connection is slow but previously it took around 30 sec, the problem is the searching metadata part, it took more than 7 min so though that calibre had crashed at first.

[JimmXinu]

New Test Version Posted

2024-05-08
- QQ: Doesn't need reader_posts_per_page:30 anymore

Originally Posted by kagekarasu

I used the test version to update some fics from qq, it work but it is extremely slow, it took me around 8 min for 6 chapters, my internet connection is slow but previously it took around 30 sec, the problem is the searching metadata part, it took more than 7 min so though that calibre had crashed at first.

FFF uses the same code for SpaceBattles and SufficientVelocity that is now used for QQ.

QQ used to show more posts per reader page, but now it's at the default (10). That would cause FFF to do a lot more individual network hits.

Which honestly doesn't actually match up with your reported issue. My first instinct is a story of many images. You can PM me the story URL if you're still having trouble.

[kagekarasu]

Originally Posted by JimmXinu

New Test Version Posted

2024-05-08
- QQ: Doesn't need reader_posts_per_page:30 anymore


FFF uses the same code for SpaceBattles and SufficientVelocity that is now used for QQ.

QQ used to show more posts per reader page, but now it's at the default (10). That would cause FFF to do a lot more individual network hits.

Which honestly doesn't actually match up with your reported issue. My first instinct is a story of many images. You can PM me the story URL if you're still having trouble.

I found the problem, it's not FFF or the story having too many image, windows was downloading an update in the background whithout notification even tough i set them on, again...

[JimmXinu]

Originally Posted by kagekarasu

I found the problem, it's not FFF or the story having too many image, windows was downloading an update in the background whithout notification even tough i set them on, again...

All good--you prompted me to find a different issue.

[Homer55]

just so you know, QQ migrated to Xenforo 2, so the plugin doesn't work there anymore

[Anyssia]

Hi! I use the caching feature to download FFnet fics to Calibre, but I have a problem with the addon vs Firefox' cache. I always get an error message and I didn't know what was the problem.

I went around by using Chrome, but today I keep getting a 403 error when using WebToEpub with Chrome to download/cache ffnet pages. Apparently, it's not only me.

So I need to go back to Firefox, except I still get said error and I don't understand what I'm doing wrong since I'm doing the same thing with Chrome:

the error I get every time is:

HTTP Error in FFF 'Page not found or expired in Browser Cache (see FFF setting browser_cache_age_limit)'(428) URL:...

no matter which fic I'm downloading.

And when it's not straight up an error, it's missing chapters:

"Download epub completed, 1 failed chapters, 1 total chapters."

I tried with regular Firefox, I even tried with Developer Firefox and the latest unpublished version of WebToEpub, I always get the same from problem with directing FFF to using a Firefox cache. I thought it might be an addon conflict, but the single addon in Developer Firefox is WTE, so I have no idea, please

under: [defaults] :

## This feature has been tested on Firefox and Chrome browsers on Windows, Mac and Linux. 
## Users report it works with Chromium-based browsers Vivaldi and Microsoft Edge and Firefox-based 
## browser Waterfox.
###browser_cache_path:C:\Users\Utilisateur\AppData\Local\Mozilla\Firefox\Profiles\nqmpbxxz.default-release\cache2
###browser_cache_path:C:\Users\Utilisateur\AppData\Local\Google\Chrome\User Data\Default\Cache\Cache_Data
browser_cache_path:C:\Users\Utilisateur\AppData\Local\Mozilla\Firefox\Profiles\xydoaeq3.dev-edition-default\cache2

[JimmXinu]

Unfortunately, I think I'm seeing the same thing--using WebToEpub to load the browser cache isn't working.

I will look into it, perhaps the cache key for WebToEpub has changed. But I can't make any promises.

However, manually loading the chapters into cache or using open_pages_in_browser:true both still work.

[Anyssia]

Originally Posted by JimmXinu

Unfortunately, I think I'm seeing the same thing--using WebToEpub to load the browser cache isn't working.

I will look into it, perhaps the cache key for WebToEpub has changed. But I can't make any promises.

However, manually loading the chapters into cache or using open_pages_in_browser:true both still work.

Alright, good to know that it's not just me, thank you. I'll try to use the open pages feature then.

[JimmXinu]

New Test Version Posted

2024-05-09
- Fix for WebToEpub firefox cache key changing

Originally Posted by JimmXinu

Unfortunately, I think I'm seeing the same thing--using WebToEpub to load the browser cache isn't working.

I will look into it, perhaps the cache key for WebToEpub has changed. But I can't make any promises.

Turns out that's it was and that it was easy to add. On Firefox, at least.

WebToEpub was last updated Mar 22, so I assume it was change in Firefox itself.

I'm also seeing WebToEpub not work on ffnet with Chrome now. Nothing I can do about that.

[Firewolf88]

Hi there, I'm having a small problem. For whatever reason FFF has stopped collecting additional/freeform tags on ao3 sometimes and I can't figure out why. I've tried telling it to re-get meta data from site, I've deleted and redownloaded the fic, and it just refuses to collect them in the metadata column. It may be a restricted viewing problem, or at least those are the ones I'm having a much harder time trying to get the tags off of. I have seemed to be able to get there by telling it to overwrite non restricted works, but it doesn't work for restricted ones and I'm not quite sure its 100% effective. I've tried always_login true and it didn't do anything. Is there some other line to add to personal.ini or setting that might do the trick?

[ownedbycats]

On the AO3, uncheck the 'Hide additional tags (you can still choose to show them)' in the account settings.

[JimmXinu]

Agreed. If it happens when downloading 'logged in', that sounds like you've hidden those.