[GUI Plugin] FanFicFare

[DragoLord19d]

I'm getting this error with the lastest update.
I thought Fanficfare skipped 403 errors.
calibre, version 7.6.0
ERROR: Error Updating Metadata: <p>An error has occurred while FanFicFare was updating calibre's metadata for <a href='https://www.fanfiction.net/s/9251992/1/A-Brutal-Truth'>A Brutal Truth Anthology</a>.</p>

Traceback (most recent call last):
File "C:\Users\Owner\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\fetchers\fetcher_requests. py", line 128, in request
File "C:\Users\Owner\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\requests\models.py", line 943, in raise_for_status
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://www.fanfiction.net/s/9251992/1/A-Brutal-Truth

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "calibre_plugins.fanficfare_plugin.dialogs", line 715, in do_loop
File "calibre_plugins.fanficfare_plugin.fff_plugin" , line 1356, in prep_download_loop
File "calibre_plugins.fanficfare_plugin.fff_plugin" , line 1236, in get_story_metadata_only
File "C:\Users\Owner\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\adapters\base_adapter.py", line 325, in getStoryMetadataOnly
File "C:\Users\Owner\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\adapters\adapter_fanfictio nnet.py", line 113, in doExtractChapterUrlsAndMetadata
File "C:\Users\Owner\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\requestable.py", line 119, in get_request
File "C:\Users\Owner\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\requestable.py", line 111, in get_request_redirected
File "C:\Users\Owner\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\fetchers\base_fetcher.py", line 133, in get_request_redirected
File "C:\Users\Owner\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\fetchers\cache_basic.py", line 122, in fetcher_do_request
File "C:\Users\Owner\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\fetchers\decorators.py", line 102, in fetcher_do_request
File "C:\Users\Owner\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\fetchers\base_fetcher.py", line 106, in do_request
File "C:\Users\Owner\AppData\Roaming\calibre\plugins\Fa nFicFare.zip\fanficfare\fetchers\fetcher_requests. py", line 149, in request
fanficfare.exceptions.HTTPErrorFFF: HTTP Error in FFF '403 Client Error: Forbidden for url: https://www.fanfiction.net/s/9251992...Truth'(403)

[ownedbycats]

edit: delete

[JimmXinu]

Originally Posted by DragoLord19d

I'm getting this error with the lastest update.
I thought Fanficfare skipped 403 errors.

After it masked an issue I added an additional error reporting dialog. Processing of the error'ed update hasn't changed, it's just being reported now.

I could catch HTTPErrorFFF separately if it's a significant problem.

[DragoLord19d]

Originally Posted by JimmXinu

After it masked an issue I added an additional error reporting dialog. Processing of the error'ed update hasn't changed, it's just being reported now.

I could catch HTTPErrorFFF separately if it's a significant problem.

Please. Maybe a mass confirmation?

[JimmXinu]

New Test Version Posted

2023-03-05
- Move new exception catching for metadata errors

[DavidBrookes]

I updated one of my Fanfiction libraries in Calibre this weekend and something that I have come across happened. All of the newly created or updated eBooks now have an image before the title page itself. Can I strip this from the eBooks in question and how do I prevent this from happening in the future? I have attached an eBook sample and a screenshot of the image from the same eBook.

[JimmXinu]

Cover image has been a feature of FanFicFare for over a decade, it's not new. Most users generally want them.

It's also a complicated topic. There's a wiki page Cover Settings Calibre Plugin that documents the various different settings and options.

You can remove covers from existing ebooks manually using using Calibre built-in Edit book or in batches using the Modify Epub plugin.

You can suppress all future FanFicFare covers in personal.ini with:

[overrides]
never_make_cover:true

Note that will also prevent the covers from appearing in Calibre as well as in the ebook.

[goosenik]

Hello! I had asked a bit about this on Reddit, and someone lovely suggested I come here and ask. I'm new to the plugin and coding as a whole, so forgive me if this is super simple or alternatively impossible!

1. Is there a way to change the way the title pages show up? For example-- I'd like the intro metadata page, and then the 'Summary/Description' on the following page, and then the story to start on the third page. Is there a way to do this?

2. This isn't a necessity either by any means, just something I'm curious about. Is there a way to add formatting?
Specifically, I can't stand that AO3 doesn't indent new paragraphs. lol Is there a way to tell the plugin to indent new paragraphs in the works?
Likewise, is there a way to tell it to italicize Author's Notes?
Would there be a way to do this without manually adding the formatting to each individual work?

Thanks!

[DavidBrookes]

Thank you for that - the Modify ePub plugin did the trick - regarding the overrides section to put in the personal.ini file, is there a specific place it needs to be placed or can it be put at the start of the personal.ini file as I know from my IT work something placing of settings in configuration files can be important?

[JimmXinu]

Multi-reply, FYI.

Originally Posted by goosenik

1. Is there a way to change the way the title pages show up? For example-- I'd like the intro metadata page, and then the 'Summary/Description' on the following page, and then the story to start on the third page. Is there a way to do this?

FanFicFare output is customizable, but it's complicated.

FFF doesn't have a way to split the title page into different files, but you can inject a page break between entries with a personal.ini setting:

[defaults]
# ...
titlepage_entries: seriesHTML,category,genre,language,characters,ships,status,datePublished,dateUpdated,dateCreated,rating,warnings,numChapters,numWords,publisher,<dir style="page-break-after: always"></div>,description

Originally Posted by goosenik

2. This isn't a necessity either by any means, just something I'm curious about. Is there a way to add formatting?
Specifically, I can't stand that AO3 doesn't indent new paragraphs. lol Is there a way to tell the plugin to indent new paragraphs in the works?
Likewise, is there a way to tell it to italicize Author's Notes?
Would there be a way to do this without manually adding the formatting to each individual work?

By default, FFF tries to normalize the appear of stories and the default output is what I prefer.

The output_css setting from defaults.ini (for epub) is:

[epub]
# ...
## Allow customization of CSS.  Make sure to keep at least one space
## at the start of each line and to escape % to %%.  Also need
## background_color to be in the same section, if included in CSS.
## 'adobe-hyphenate: none;' prevents hyphenation on newer Nooks
## STR(wG) (1.2.1+ for sure)
output_css:
 body { background-color: #%(background_color)s;
        text-align: justify;
        margin: 2%%;
	adobe-hyphenate: none; }
 pre { font-size: x-small; }
 h1 { text-align: center; }
 h2 { text-align: center; }
 h3 { text-align: center; }
 h4 { text-align: center; }
 h5 { text-align: center; }
 h6 { text-align: center; }
 .CI {
     text-align:center;
     margin-top:0px;
     margin-bottom:0px;
     padding:0px;
     }
 .center   {text-align: center;}
 .cover    {text-align: center;}
 .full     {width: 100%%; }
 .quarter  {width: 25%%; }
 .smcap    {font-variant: small-caps;}
 .u        {text-decoration: underline;}
 .bold     {font-weight: bold;}
 .big { font-size: larger; }
 .small { font-size: smaller; }

You can make your output_css setting entirely, or add to the existing one. For example, to indent <p> paragraphs, you could add:

[epub]
add_to_output_css:
 p {
         text-indent: 4em;
    }
 div.fff_chapter_notes {
         font-style: italic;
    }

Note that p setting won't help with stories written with <br> instead of <p> tags.

The div.fff_chapter_notes setting italicizes the author notes.

Originally Posted by DavidBrookes

Thank you for that - the Modify ePub plugin did the trick - regarding the overrides section to put in the personal.ini file, is there a specific place it needs to be placed or can it be put at the start of the personal.ini file as I know from my IT work something placing of settings in configuration files can be important?

Position in the file doesn't matter. You need to be careful to not accidentally separate existing lines from their section, and it's best to look for an existing section header and put your config under that rather than having multiple of the same [section] headings.

[goosenik]

Okay, first of all, you're a wizard and I'm in awe.

Second, thank you so much!

Third-- so the indentation and italics work, but I do now notice at the end of the work, there's no space before the end-note. Essentially it goes:

"and that was the end of the story."
Notes for the Chapter:
Here are the chapter notes and etc.

It's all just smooshed together. I swear, I tried to research how to add line breaks or to add like a 'space, hard line, space' before/after the notes, but whenever I add anything to your sample, it loses the italics. Is there any chance you could show me just that one last fix?

[JimmXinu]

The key is that you control the CSS that is applied.

Add something like margin-top:1em; to the div.fff_chapter_notes rule. Or 2em, etc if you want more space.

[wildfire070]

With the newest update, I'm having to acknowledge each error that pops up while updating stories. Normally, I can select all of my stories that are in-progress and run an "update existing stories" to see if there's new chapters. If there were any errors, it would pop up at the end dialogue. So essentially I can let it run while I'm off doing another task. Now it won't proceed with checking the other stories unless I click and acknowledge each error that pops up so I'll have to monitor it or else it will hold up the entire process. Is there a way to revert back to the previous way errors were reported?

[JimmXinu]

Already fixed in current test version. See post.

Test version linked in my signature below.

I would also point out the FAQ: Why shouldn't I just select my entire library and use FanFicFare plugin to check for updates?

[wildfire070]

Awesome good to know! Thank you!