[GUI Plugin] FanFicFare

[ownedbycats]

I set up an error column and set column colouring to turn the entire row radioactive-green if there's an error. That should make it easy to notice.

[ownedbycats]

I may have found a possible bug involving cover generation if you're able to replicate it:

1. Make sure cover generation is working under normal circumstances.
2. Have a text file containing the URL of a fanfiction.
3. With "get story URLs from inside files" enabled in the options, use "Update EPUB if new chapters." (Not tested the other options though.)
4. It'll download the EPUB, but fail to generate the cover.

"Update EPUB Cover?" seems to have no effect, oddly enough.

EDIT: It does properly download existing covers, though.

[JimmXinu]

On the FFF config Calibre Cover tab there's a setting for 'Inject/update the cover inside the epub'. Do you have that turned on?

Because cover generation, either by GC plugin or using Calibre's built-in is done after download.

[ownedbycats]

Inject cover is turned on yes. But I had "generate covers only for new books" turned on. Oops. I feel kind of like a pester sometimes.

[ownedbycats]

If an author moves their fanfics to another site, should I tell FFF to overwrite the old files or will updating still work after fixing the url identifier?

[JimmXinu]

Originally Posted by ownedbycats

If an author moves their fanfics to another site, should I tell FFF to overwrite the old files or will updating still work after fixing the url identifier?

If the epubs are at all recent (within ~5 years), they have site-specific chapter URLs embedded in each epub chapter. If 'updated' with a different site story URL, all the chapters will be discarded and downloaded anew.

So it's up to you. Experiment and see what you like best.

[ownedbycats]

Thanks.

I can't seem to get the regex right for this. How would I remove a "(orphan_account)" appended to the author (example here)?

I already have an author=>orphan_account=>Unknown and my results usually result in either "AuthorName (Unknown)" or "AuthorName ()" or "Unknown." Regex is not my forte.

[JimmXinu]

 author=>\(orphan_account\)=>

You probably want author=>^orphan_account$=>Unknown for the other one, then you don't have to worry about order.

[ownedbycats]

Thanks. I was also able to use that to get rid of the "(Video Game)" appended to some AO3 categories. I really should see if "regex for dummies" is a thing.

[ownedbycats]

Here's yet another question:

Aside from attempting to fetch new chapters for all my fics and getting the "chapters not recognized" error on them, is there any way for FFF to detect ePubs that were not downloaded with FFF?

Also, what exactly does "remove new chapter marks from selected book" do?

[JimmXinu]

Originally Posted by ownedbycats

Aside from attempting to fetch new chapters for all my fics and getting the "chapters not recognized" error on them, is there any way for FFF to detect ePubs that were not downloaded with FFF?

Nothing in FFF comes to mind. You could use plugin Quality Check's Search ePubs feature to search for FanFicFare in OPF manifest to mark the ones that are from FFF. Might need to section off in a VL or separate library to make that convenient.

Originally Posted by ownedbycats

Also, what exactly does "remove new chapter marks from selected book" do?

If you have mark_new_chapters:true, new chapters will be marked on update. That feature removes those marks.

From defaults.ini:

## If true, when updating an epub that already has old chapters, new
## chapters will be marked in the TOC and chapter header by using
## chapter_title_new_pattern and chapter_title_addnew_pattern to set
## the chapter title.
## If set to latestonly, only new chapters downloaded this time will
## be marked (new) and existing chapters will have any (new) marks
## removed.
## mark_new_chapters can be true, false or latestonly
mark_new_chapters:false

## chapter title patterns use python template substitution.  The
## ${number} is the 'chapter' number and ${title} is the chapter
## title, after applying chapter_title_strip_pattern.  ${index04} is
## chapter number padded with leading zeros (mostly for internal use)
## such as 0001.  ${index} == ${number} for backward compatibility.  A
## few site adapters add additional chapter metadata.

## The basic pattern used when not using add_chapter_numbers or
## mark_new_chapters
chapter_title_def_pattern:${title}

## Pattern used with add_chapter_numbers, but not mark_new_chapters
chapter_title_add_pattern:${number}. ${title}

## Pattern used with mark_new_chapters, but not add_chapter_numbers
## (new) is just text and can be changed.
chapter_title_new_pattern:(new) ${title}

## Pattern used with add_chapter_numbers and mark_new_chapters
## (new) is just text and can be changed.
chapter_title_addnew_pattern:${number}. (new) ${title}

[ownedbycats]

Hmm, the problem with that is that I used FFF to download metadata without overwriting the old files.

I did come across a sort of kludgy workaround so for future people:

the first is that if you didn't insert them with Polish Book or Modify ePub, Quality Check can search for books with missing covers (under the somewhat misleading "find non-replaceable covers"). That found a bunch.

Then at least for AO3-downloaded fics they all contain the phrase "Posted originally on the Archive of Our Own at" [then url here]. I couldn't get Quality Check to search for that exact phrase so I ended up using Agent Ransack (need the trial of the paid version for epub searching, or maybe convert to txt and use another program) and the Drop Search Results plugin to mark all of them.

[ownedbycats]

I ran into a glitch while duplicating books to test out some settings in personal.ini.

If a fanfic has no formats and FFF attempts to update the metadata from the website (granted, I'm not sure why someone would do this instead of just downloading it), it'll throw this error:

calibre, version 4.18.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/12493045/1/'>Whole</a>.</p>The ebook has been updated, but the metadata has not.

Traceback (most recent call last):
  File "calibre_plugins.fanficfare_plugin.fff_plugin", line 1606, in update_books_loop
  File "calibre_plugins.fanficfare_plugin.fff_plugin", line 2318, in update_metadata
  File "site-packages\calibre\ebooks\oeb\polish\main.py", line 267, in polish
AttributeError: 'NoneType' object has no attribute 'rpartition'

<a bunch of story-specific info here>

[JimmXinu]

New Test Version Posted

2020-06-17
- Check for epub before polishing cover into it.

Originally Posted by ownedbycats

I ran into a glitch while duplicating books to test out some settings in personal.ini.

If a fanfic has no formats and FFF attempts to update the metadata from the website (granted, I'm not sure why someone would do this instead of just downloading it), it'll throw this error:

IF you do update metadata from site AND have not epub AND generate a cover AND try to inject that generated cover, THEN you can hit that. That's what I call a corner case.

Anyway, it checks for the epub existing first now.

[MerlinMama]

Sorry if this has been covered before, I didn't find anything though.



When adding new fics (I guess even updating), I would like all of my labels to show up on the titlepage, even if there's no information to put in them, or if the information would come from custom columns. For example:


Fandom: Harry Potter
Pairing:
Status: Complete
Last Read:
Summary: A story about Harry Potter.


Is this possible, or would it not work? Hope I'm making sense!