[GUI Plugin] FanFicFare

[JimmXinu]

Originally Posted by ninjadudedxp

Ok i see add update chapters only, would this be a part of personal.ini somewhere? Im using the Automation which i think is only using FFF command line.

This thread is specifically for the Calibre Plugin version of FFF, so I assume questions here are about the plugin.

The FFF CLI version is a bit different, the CLI options -u/--update-epub, -U/--update-epub-always and --force control updates. See the CLI -h/--help list.

I don't know anything about "the Automation", it's not something I use or support.

[TaviCalderon]

hi,

i added the below to my personal.ini, but it didn't seem to change anything or make the summaries italicized. did i miss something? should i have plugged the word "description" into something on the titlepage_entry: line?

Spoiler:

titlepage_entry:<b class="fff_tp_label" id="${id}_label">${label}:</b> <span class="fff_tp_value" id="${id}_value">${value}</span><br />

add_to_output_css:
 #description_value {
    font-style:italic;
 }

sorry, i know nothing about css or coding in general so i'm not sure where i went wrong. i added this under the [epub] section since that's the only format i have anything in.

[JimmXinu]

Originally Posted by TaviCalderon

i added the below to my personal.ini, but it didn't seem to change anything or make the summaries italicized. did i miss something? should i have plugged the word "description" into something on the titlepage_entry: line?

Did you install the latest test version?

If not, you also need wide_titlepage_entries: like I mentioned earlier.

Other than that, I don't see anything wrong.

Originally Posted by TaviCalderon

sorry, i know nothing about css or coding in general so i'm not sure where i went wrong. i added this under the [epub] section since that's the only format i have anything in.

If you want to customize your output to the level that you apparently do, I suggest learning at least a little HTML and CSS.

[culytera]

Originally Posted by TaviCalderon

sorry, i know nothing about css or coding in general so i'm not sure where i went wrong. i added this under the [epub] section since that's the only format i have anything in.

Check this thread, you might get some ideas.

[TaviCalderon]

thanks guys!! i didn't realize i needed to add that line into wide_titlepage_entries, lol. thought i just needed to clear out what was in wide_titlepage_entries by default to make it work. my bad!

appreciate all your help to anyone else who is frantically googling and cannot find answers: if you want the summary/description of the work to be italicized on your title page for epubs, below is what i added and now it works!

Spoiler:

titlepage_entry:<b class="fff_tp_label" id="${id}_label">${label}:</b> <span class="fff_tp_value" id="${id}_value">${value}</span><br />

wide_titlepage_entries:<b class="fff_tp_label" id="${id}_label">${label}:</b> <span class="fff_tp_value" id="${id}_value">${value}</span><br />

add_to_output_css:
 #description_value {
    font-style:italic;
 }

[JimmXinu]

FYI, the latest test version specifically changes it so you don't need to include wide_titlepage_entries.

[penumbria]

I posted about this before around a month and a half ago and am still having the same issue. When I try to use the plugin to update an epub, to add a new epub, or to update an anthology from an AO3 fic, I get an error message: "HTTP Error in FFF '403 Client Error: Forbidden for URL:"

I've tried using a VPN, I've tried using free public wifi at a restaurant, and I even tried someone else's personal home wifi when I visited them and they live in a different state. It is always the same message.

I know the developer won't work on the issue when it is so localized and not widespread and I get it and understand and that is fine. But even though I can just download epubs from AO3, that doesn't help with ones that are updating regularly. Unless I download a new copy every few days or whenever they update which is a non-starter and waste of time.

Does anyone have any suggestions on how to overcome this error so that I can once again update AO3 fics easily using the plugin? I'm not overly tech savvy or tech lingo knowledgable but I can follow directions.

[Tharos]

Originally Posted by penumbria

https://archiveofourown.org/works/55180027

I was able to load the story normally. Do you only have problems with this story, or with others as well?

[penumbria]

Every single story, whether an anthology, new to my Calibre, or updating an existing fic. They won't work for me. I get the same error message and have for over a month. I know it is a me problem not a widespread problem though I don't know why. It just started one day and I can't figure out a fix for it. As I said, I'm not really tech-savvy with this stuff but I've tried what people have suggested. I'm just hoping for a workaround I can use.

[Tharos]

Have you tried it with a new database and a new extension added there?

Specifically, I use the following for AO3 in the personal.ini:

[archiveofourown.org]
username:Maysupersecretusername
password:365Dayswithfreebeer
is_adult:true
extragenres:
extracategories:
extratags:
custom_columns_settings:
 category=>#ts
 fandoms=>#ts

There might be some nonsense in there, but it works for me.


Ok, I don't think I need to mention that these are not my real login details, do I?

[JimmXinu]

Originally Posted by penumbria

Every single story, whether an anthology, new to my Calibre, or updating an existing fic. They won't work for me. I get the same error message and have for over a month. I know it is a me problem not a widespread problem though I don't know why. It just started one day and I can't figure out a fix for it. As I said, I'm not really tech-savvy with this stuff but I've tried what people have suggested. I'm just hoping for a workaround I can use.

The only idea I have (and may have mentioned before), is to turn off always_login if you have it set true.

[ReikoLJ]

Hey there, first of all I love this plugin and have been using it successfully for many years across multiple devices and computers.
Unfortunately it has been behaving oddly for me lately. A few weeks back I came to use it and when I clicked on the 'FanFicFare' icon in the ribbon on calibre, nothing happened. No errors but no pop for asking for the usual URLs. I can open up all the other options within it by clicking the arrow menu button but even from there if I navigate to 'Download from URLs', nothing launches. Just silent failing

I uninstalled the plugin and reinstalled it but it didn't fix it. So I thought I would leave it alone for a bit until a new version came out. Today, I updated both calibre and the plugin but it's still doing it so I'm at a bit of a loss now.
Not sure if it logs anywhere? I couldn't see anything in the settings about a log location.

Hope you can help, thanks!

[JimmXinu]

You can restart Calibre in debug more (under Calibre's Preferences drop down), try again and then post the text log file you get after you quit Calibre.

As a new MobileRead user, you might not be able to attach files to posts right away. In which case, I suggest posting it to a file host site somewhere and link to it from here.

[TaviCalderon]

Originally Posted by JimmXinu

Now you can add calibre_std_rating to titlepage_entries. Note that it shows up as a 1-5 number. You can change that to some form of star using replace_metadata if you like.

hi again!

you mentioned this in an earlier conversation about another fix. how would i use replace_metadata to accomplish this? i tried adding the below to [defaults], [epub], and the [archiveofourown] sections but none of them actually worked.

replace_metadata:
 rating=>1=>★
 rating=>2=>★★
 rating=>3=>★★★
 rating=>4=>★★★★
 rating=>5=>★★★★★

[JimmXinu]

Originally Posted by TaviCalderon

hi again!

you mentioned this in an earlier conversation about another fix. how would i use replace_metadata to accomplish this? i tried adding the below to [defaults], [epub], and the [archiveofourown] sections but none of them actually worked.

replace_metadata:
 rating=>1=>★
 rating=>2=>★★
 rating=>3=>★★★
 rating=>4=>★★★★
 rating=>5=>★★★★★

Did you try using calibre_std_rating instead of rating? Because rating is different.