[GUI Plugin] FanFicFare

[ownedbycats]

The 'title page' entries might cause issues when using Kobo Utilities' Update ToC, but there's the delete-and-restore method. I didn't think of anthologies though, I'll add it.

[riothamus]

I'm having trouble with one specific ff.net story. Other stories are updating fine, but this one seems to have issues with the browser cache. I'm getting

HTTP Error in FFF 'Page not found or expired in Browser Cache (see FFF setting browser_cache_age_limit)'(428) URL:'https://www.fanfiction.net/s/14211179/1/Pansy-s-Protector'
https://www.fanfiction.net/s/14211179/1/Pansy-s-Protector

This is right after I open the pages in chrome and FFF also opens up the first chapter but I still get the error. Several other stories updated just fine before and after. I ran into the same error last week on the same story.

[JimmXinu]

Originally Posted by riothamus

I'm having trouble with one specific ff.net story. Other stories are updating fine, but this one seems to have issues with the browser cache. I'm getting

HTTP Error in FFF 'Page not found or expired in Browser Cache (see FFF setting browser_cache_age_limit)'(428) URL:'https://www.fanfiction.net/s/14211179/1/Pansy-s-Protector'
https://www.fanfiction.net/s/14211179/1/Pansy-s-Protector

This is right after I open the pages in chrome and FFF also opens up the first chapter but I still get the error. Several other stories updated just fine before and after. I ran into the same error last week on the same story.

I'm not seeing it. However, if that was the page that you saw the CloudFlare in front of, it can be cached differently and you may need to load it again.

Usually clicking through to chapter 2 and then using the '< Prev' button (not your browser back button) is enough. Clicking in the URL box and hitting enter to load https://www.fanfiction.net/s/1421117...sy-s-Protector explicitly also usually works. Failing either of those, try entering the URL in a new tab and doing ctrl-shift-R to force a reload.

[jazzhands]

I'm so sorry to ask, I swear I've searched but I can't come up with an easy solution, and I think it should be simple.

Is there code I can add or edit in the personal.ini file to stop downloading any freeformtags from A03?

Thanks in advance!

[riothamus]

Originally Posted by JimmXinu

I'm not seeing it. However, if that was the page that you saw the CloudFlare in front of, it can be cached differently and you may need to load it again.

Usually clicking through to chapter 2 and then using the '< Prev' button (not your browser back button) is enough. Clicking in the URL box and hitting enter to load https://www.fanfiction.net/s/1421117...sy-s-Protector explicitly also usually works. Failing either of those, try entering the URL in a new tab and doing ctrl-shift-R to force a reload.

Hey thanks. Doing the force reload on each chapter and the author page did it.

[JimmXinu]

Originally Posted by ownedbycats

[https://www.fanfiction.net/s/13873983/1/Slices-Of-Apple-The-Warlord-s-Horde-Of-Fruitcakes]
add_to_replace_metadata:
 title=>^.*=>Slices Of Apple

custom_column_settings:
 "The Warlord's Horde Of Fruitcakes"=>#subtitle

The subtitle fails to map to the column. I tested with my other fics already using this setup and it won't populate an empty #subtitle column. (Preexisting values didn't get replaced with an empty, at least.)

You have custom_column_settings--it should be custom_columns_settings.

On the one hand, typos are the user's problem. OTOH, having color highlighting for much of the the INI trains the user to not look for their own typos.

I may take another look at whether highlighting can be applied to story URL sections.

[JimmXinu]

Originally Posted by jazzhands

I'm so sorry to ask, I swear I've searched but I can't come up with an easy solution, and I think it should be simple.

Is there code I can add or edit in the personal.ini file to stop downloading any freeformtags from AO3?

There isn't any way to stop FFF collecting those tags--it's part of the code. However, you can stop FFF from using those tags.

Looking in defaults.ini, freeformtags are included in genre, you change that in your personal.ini with:

[archiveofourown.org]
include_in_genre: ao3categories

For reference, defaults.ini has:

## AO3 doesn't have anything it calls 'genre'.  The adapter used to be
## hardcoded to include the site specific metadata freeformtags &
## ao3categories in the standard metadata field genre.  By making it
## configurable, users can change it.
include_in_genre: freeformtags, ao3categories

[jazzhands]

Thank you so much! I really appreciate how active you are here. I've found answers to all of my other questions because you're so quick to provide answers to your users.

Originally Posted by JimmXinu

There isn't any way to stop FFF collecting those tags--it's part of the code. However, you can stop FFF from using those tags.

Looking in defaults.ini, freeformtags are included in genre, you change that in your personal.ini with:

[archiveofourown.org]
include_in_genre: ao3categories

For reference, defaults.ini has:

## AO3 doesn't have anything it calls 'genre'.  The adapter used to be
## hardcoded to include the site specific metadata freeformtags &
## ao3categories in the standard metadata field genre.  By making it
## configurable, users can change it.
include_in_genre: freeformtags, ao3categories

[ownedbycats]

Originally Posted by JimmXinu

You have custom_column_settings--it should be custom_columns_settings.

On the one hand, typos are the user's problem. OTOH, having color highlighting for much of the the INI trains the user to not look for their own typos.

I may take another look at whether highlighting can be applied to story URL sections.

I looked and my other sections also were custom_column - I did have it right at one point so I'm not sure how that happened. (Maybe got clumsy with the copy-pasting?) The subtitle entry seems a bit more sensible so I will switch to that.

[JimmXinu]

New Test Version Posted

2023-04-18
- Show INI highlighting under [storyUrl] sections
- Update translations.
- adapter_quotevcom: Some stories have no comments.

[storyUrl] sections headers are still a different color because there isn't edit checking on the story URL itself. [storyUrl] sections are identified by starting with https?://

I'd have to touch every adapter to add that.

[ownedbycats]

INI highlighting works good.

I also found 2-3 more typos in various tweaks.

[ninjadudedxp]

Trying to search through the thread for my answer but cant seem to find it, is there a way for calibre FFF to auto update? I Have email set up but i still have to manually click update from email anytime i login.

I have calibre set up on my local server so i dont tend to log in often enough but would like it to update with current chapters automatically.

[ownedbycats]

Originally Posted by ninjadudedxp

Trying to search through the thread for my answer but cant seem to find it, is there a way for calibre FFF to auto update? I Have email set up but i still have to manually click update from email anytime i login.

I have calibre set up on my local server so i dont tend to log in often enough but would like it to update with current chapters automatically.

No. Deliberate choice I think, but don't remember the exact reasoning.

[JimmXinu]

Unfortunately, no.

Calibre doesn't have any mechanism for GUI plugins to be automatically activated. Both calling for updates and the 'proceed to update library' dialog need GUI interaction.

I believe that some plugins allow for bypassing the 'proceed to update' dialog, but last I heard, that is Calibre's official way of protecting the library from multiple actions overwriting each other and should not be skipped.

[ownedbycats]

Originally Posted by JimmXinu

I believe that some plugins allow for bypassing the 'proceed to update' dialog, but last I heard, that is Calibre's official way of protecting the library from multiple actions overwriting each other and should not be skipped.

Extract ISBN and Count Pages (both kiwidude's plugins) both have this option.