[GUI Plugin] FanFicFare

[ownedbycats]

Originally Posted by julo

Thanks for the info.
So it is part of Calibre and not somewhere in the registry or whatnot.

Also settings are library-specific.

If I remember correctly, the 'copy structure' checkmark when creating a new library will copy it.

[JimmXinu]

Originally Posted by ownedbycats

If I remember correctly, the 'copy structure' checkmark when creating a new library will copy it.

So it does. I did not know that.

[ownedbycats]

Question: If possible, how would I do a replace_metadata on datePublished? e.g. =>2020-01-01?

Story-specific, obviously— case example is a still in-progress fic moved to AO3 without being backdated. Checking 'new only' works for Calibre metadata but not the title page.

[JimmXinu]

Originally Posted by ownedbycats

Question: If possible, how would I do a replace_metadata on datePublished? e.g. =>2020-01-01?

Story-specific, obviously— case example is a still in-progress fic moved to AO3 without being backdated. Checking 'new only' works for Calibre metadata but not the title page.

What have you tried and what didn't work with it?

[ownedbycats]

User error. I was trying to match the date exactly and used the wrong one. A match-all works:

add_to_replace_metadata:
 datePublished=>^.*$=>2012-04-16

While it wasn't the case this time, I also wonder whether timezones might throw off the date and cause it to fail.

[JimmXinu]

Timezones in python are a disaster--weren't even included in python distro until 3.9. Timezones as used by various sites are inconsistent--some are site TZ, some are user TZ.

FFF basically just ignores timezones as much as possible.

[ownedbycats]

Yes, I remember the timezone issue coming up in one instance: one now-complete story, the author always updated at exactly 12:00 GMT on Saturday. Since I'm -4:00, it wasn't uncommon for me to read that same chapter on Friday night. This confused one of my templates which checked that #lastupdated was newer than #lastread.

[atsumiri]

Hi, first of all i want to thank you for this amazing plugin!
It saves so much time! thank you

I think FicBook.net have made some changes and now when i download or update any fics from there it always put 'In-Progress' status into metadata even for the fics that have "Completed" status.

For example, https://ficbook.net/readfic/4851292 this fic has "Завершён" - "Completed" status but it shows 'In-Progress' status in metadata
Is there any way to fix it?

[JimmXinu]

New Test Version Posted

2022-11-30
- adapter_ficbooknet: Site change for status + remove debug

[ownedbycats]

Is add_category_when_multi_category:false the correct syntax for when I don't want to add 'crossover' in a story-section override? It works, so probably yes. (The forum search won't let me search for it.)

[JimmXinu]

FYI, I noticed that I wasn't getting ffnet notifications anymore. Looking at the site I found:

Note: Email Alerts are now only active if Email Opt-in is enabled in account settings.

... and after enabling ...

Email Optin Setting Updated
Email optin ENABLED. Please note email opt-in settings is reset to no/disabled after 90 days.

[ownedbycats]

That's good to know.

[marshie250]

I had a question about cover generation when it comes to anthologies. I have several stories that I have created covers for, and would like to preserve those when updating the stories, while generating covers based on updated metadata for stories that have no created covers. For this, setting Update Calibre Cover (from ePub) to "Yes, if EPUB has a cover image" and Generate Calibre Cover to "Yes, unless FanFicFare found a cover image" works beautifully.

Updating anthologies while using these settings, however, forces cover generation even with stories I've created a cover for. I've tried various combinations of settings, but ultimately I've only been able to either:
a) use the previously mentioned settings to preserve created covers while still generating covers with the updated metadata for stories without created covers (though created anthology covers are always overwritten with generated covers), or
b) set calibre to preserve the cover no matter what (using the "Only for New Books" settings), which keeps all created covers, even for anthologies, but obviously will not re-generate with updated metadata for stories with no created covers

Am I missing a setting to resolve this issue with the forced creation of anthology covers? Or do I need to just stick with the settings in scenario b and manually generate covers for stories when I see they've been updated?

[JimmXinu]

You are correct.

FFF plugin doesn't have a way to identify a cover you have set manually for an anthology vs one that was found.

As mentioned in the wiki page, you could use a force_cover_image for the first book story URL. But you'll need to save the cover somewhere and add that setting.

If you use a specific anthology GC set from generate_cover_settings (like I do), you also need to adjust it to not execute when the cover type is force:

add_to_generate_cover_settings:
 ${anthology} ${cover_image}=>^true [^f].*$=>FFDL

[marshie250]

Thank you for the quick response! I can't believe I never stumbled upon that wiki page when I was trying to find a way to do this. I'll play around with it, but it sounds like scenario B rather than specify a location for all the anthologies with created covers (I have about a hundred and that does not seem worth the headache).