[GUI Plugin] FanFicFare

[smallbutmighty]

Originally Posted by ownedbycats

The AO3 adapter collects "comments" (though I am not sure whether it's user comments or something else), so its just a matter of putting it somewhere:

...

You can try this:

[archiveofourown.org]

## adds to titlepage_entries instead of replacing it.
extra_titlepage_entries: comments

Thanks. Unfortunately that just adds a line with the number of comments the fic has, rather than appending the actual comments to the epub - which is what I'm trying to do.

[JimmXinu]

Multi-reply

Originally Posted by HowWouldIKnow

Hi,
I just updated to the newest Calibre and FFF and now I have waited a few hours only to get only Errors for every single story.

Some changes where made a couple months ago that will make downloads take longer if they are all from the same site. Downloads from the same site are now serialized.

Everything you've shown is debug output when working correctly. Also, I was able to download that story successfully.

Originally Posted by smallbutmighty

Thanks. Unfortunately that just adds a line with the number of comments the fic has, rather than appending the actual comments to the epub - which is what I'm trying to do.

It's been requested before, but it's not something I'm interested in adding to FFF.

Depending on site, comments or reviews could end up being lots of additional page hits and how would updates be handled? There's no comment index like a chapter list--would have to download them all again each time.

I didn't even want to collect the number of comments or reviews (or likes/kudos/stars/whatever) because they can change minute to minute. But enough people asked that I did anyway.

[smallbutmighty]

Originally Posted by JimmXinu

It's been requested before, but it's not something I'm interested in adding to FFF.

Fair enough, and a very understandable reasoning too! If it's not something possible then it's not possible! Thank you for your reply and the work creating and maintaining this fab plugin.

[ownedbycats]

Apologies, I wasn't sure exactly what it was

[ownedbycats]

Originally Posted by JimmXinu

It's been requested before, but it's not something I'm interested in adding to FFF.

Depending on site, comments or reviews could end up being lots of additional page hits and how would updates be handled? There's no comment index like a chapter list--would have to download them all again each time.

I didn't even want to collect the number of comments or reviews (or likes/kudos/stars/whatever) because they can change minute to minute. But enough people asked that I did anyway.

A possible suggestion: An option to add a link to the comments page to the title page?

[ownedbycats]

unsure if I asked this before: With Generate Cover, I can set it to fill a column. Is there a way to have FFF fill a column for a downloaded image cover?

[JimmXinu]

Originally Posted by ownedbycats

A possible suggestion: An option to add a link to the comments page to the title page?

Reducing two clicks (story link, then reviews link on that page) to one click.
I don't see that being worth the effort to parse and record the reviews link on 100+ sites.

Originally Posted by ownedbycats

unsure if I asked this before: With Generate Cover, I can set it to fill a column. Is there a way to have FFF fill a column for a downloaded image cover?

I don't see anywhere in the Generate Cover plugin to populate a column.
Generate Cover plugin only appears to have an option to populate a column with a static value.

Nor is there a Calibre custom column type that can accept an image.

FFF does have a metadata entry named cover_image that can be 'default', 'old', 'specific' or 'first' to tell where the cover image came from.

If you're asking for the cover URL, why? What would be the point of having that in a column?

[ownedbycats]

Not the cover URL. I just wanted a static value, e.g. "downloaded" or "generated."

[JimmXinu]

The logic that decides whether to generate a cover or not is after the logic that sets custom columns so that your Generate Cover settings can use the custom columns set.

I'd need a fairly compelling reason to risk changing that.

[ownedbycats]

I think I can just use Action Chains then, it'd be easy to check that 'generated' doesn't exist and then fill in 'downloaded' for those.

[ownedbycats]

or another thought: If I set custom column to populate #covertype with 'downloaded' then GC should overwrite it with 'generated' for the ones that were generated. I will try that.

[JimmXinu]

Only if you run GC separately. When it's called from FFF, the custom column configured in GC doesn't appear to be set. At least, that's what happened when I tried it.

[Ascello]

Originally Posted by ownedbycats

The AO3 adapter collects "comments" (though I am not sure whether it's user comments or something else), so its just a matter of putting it somewhere:

[archiveofourown.org]

## Some adapters collect additional meta information beyond the
## standard ones.  They need to be defined in extra_valid_entries to
## tell the rest of the FanFicFare system about them.  They can be
## used in include_subject_tags, titlepage_entries,
## extra_titlepage_entries, logpage_entries, extra_logpage_entries,
## and include_in_* config items.  You can also add additional entries
## here to build up composite metadata entries.
## archiveofourown.org, for example, fills genre (a standard
## entry) as the composite offreeformtags, ao3categories in
## include_in_genre.  If there's ever more than 4 series, add
## series04,series04Url etc.
extra_valid_entries:fandoms, freeformtags, freefromtags,
 ao3categories, comments, chapterslashtotal, chapterstotal, kudos,
 hits, bookmarks, collections, byline, bookmarked, bookmarktags,
 bookmarksummary, bookmarkprivate, bookmarkrec, restricted, series00,
 series01, series02, series03, series00Url, series01Url, series02Url,
 series03Url, series00HTML, series01HTML, series02HTML, series03HTML

You can try this:

[archiveofourown.org]

## adds to titlepage_entries instead of replacing it.
extra_titlepage_entries: comments

Huh. Which thing on ao3 is this "byline"?

[JimmXinu]

Some AO3 stories have a 'byline' when some is archiving a story for a different author. (OTW is the software AO3 runs on, BTW.)

You can find examples by googling site:archiveofourown.org "archived by"

The only doc for it in FFF is in defaults.ini:

## OTW allows users to archive stories they didn't write in certain
## cases.  These are indicated by showing a byline such as:
## 'Orig Author [archived by Archivist Author]'
## If use_archived_author is set true (and there's only one author
## listed), author will be set to 'Orig Author' instead of 'Archivist
## Author'.  authorUrl will still point to the Archivist Author's page.
#use_archived_author:false

[JimmXinu]

New Test Version Posted

2020-04-12
- Updates from cloudscraper 1.2.58

I hadn't noticed any problems with the previous cloudscraper version, but OTOH, I also haven't had any problems with the new version in the few days I've been using it.