[GUI Plugin] FanFicFare

[JimmXinu]

Originally Posted by culytera

I assume there's no way to only affect chapters in an epub's TOC metadata using chapter_title_x_patterns while having a different pattern for the chapter pages (via chapter_start) and/or the TOC page (if you have include_tocpage set to true).

You can set add_chapter_numbers:toconly or customize chapter beginning HTML to use ${origchapter} instead of ${chapter} but that's about it.

[JimmXinu]

New Test Version Posted

2024-02-05
- adapter_literotica: Allow for empty div.aa_ht tags, remove extra None from text
- adapter_wwwutopiastoriescom: Remove author page get, add extracategories instead. Site static now.

Note that utopiastories is a static site now and has several story and author pages missing--including many if not most of the 17 total stories marked 'fanfiction'.

[culytera]

Originally Posted by JimmXinu

You can set add_chapter_numbers:toconly or customize chapter beginning HTML to use ${origchapter} instead of ${chapter} but that's about it.

Good enough for me so far. I'll know eventually if these settings still work well when a fic updates. I don't have the separate TOC page enabled so the "title ()" doesn't matter to me.

add_chapter_numbers:toconly
mark_new_chapters:latestonly
chapter_title_def_pattern:${title}
chapter_title_add_pattern:${title} (${date})
chapter_title_new_pattern:${title} (${date}) | NEW
chapter_title_addnew_pattern:${title} (${date}) | NEW

[JimmXinu]

New Test Version Posted

2024-02-06
- Add include_images:coveronly option for #1037

[ownedbycats]

It's not a huge issue, but I've come across it four or five times in the last month or so:

I receive an email about a new chapter on ffnet. After clearing browser cache, I open it. Almost invariably I get the cloudflare "checking your browser..." message and then it opens.

Afterwards, though, open_pages_in_browser:true then opens the new chapter (occasionally several times) as though it hadn't cached.

The download is successful, so this is just an annoyance really. Any idea why it might be happening?

[JimmXinu]

When CF intervenes the URL used is changed, there's a parameter added. That's why I tell people to click to chapter 2 then '< Prev' button.

I don't have an explanation for why open_pages_in_browser opens it more than once, but I do see that sometimes, too.

[TheOne320]

Is there any way to get rid of the "this story is stolen" "Amazon blabla" warnings that get added to every RoyalRoad story when downloading them with FanFicFare?

[JimmXinu]

The last released version of FFF had code to address that.

If it's not working, that means they changed it again. See Issue #1028 for prior discussion.

[Mandabar]

Originally Posted by JimmXinu

Issue #1028

Oh wow, I didn't even notice this was a thing. I hadn't read any of my RR books in a while.

Damn.. that means everything I updated in my monthly/bi-monthly update in Jan for RR was tainted. Ugh. Seems my files on the 8th are fine, the ones on the 21st or afterward are not.

I'm going to have to find a way to edit hundreds of files automagically for this. Urgh. Wonder if Windows Grep will work on EPUB.

[JimmXinu]

Using Action Chains and Edit Chains together can run edits on multiple epubs at a time.

[Mandabar]

Originally Posted by JimmXinu

Using Action Chains and Edit Chains together can run edits on multiple epubs at a time.

Oh thanks Jimm! That's going to help a ton! Windows Grep wasn't working out for me at first try, and that was going to be a per-phrase thing.

Now to figure out these new plugins. Hmm.
Going to have to figure out a regular expression to use... and to figure out how to do regular expressions in general. Every time I use them I have to relearn it enough to apply it LOL.

[TheOne320]

Originally Posted by JimmXinu

The last released version of FFF had code to address that.

If it's not working, that means they changed it again. See Issue #1028 for prior discussion.

Thanks, I think you are right. Stuff I downloaded yesterday does not include any of those messages but stuff that I downloaded on 2 February has those messages. That means I will just have to overwrite my files that have this problem.

[veviara]

I'm trying to customise my logpage and I've run into a problem:
I've edited logpage_entry such that there's a line break after each entry:

logpage_entry:<b>${label}:</b> <span id="${id}">${value}</span><br />

But now all entries are included every time regardless of whether they have changed or not.
Removing the above line solves that problem (on the second run).
Curiously enough though: Re-inserting the line apparently does not cause the problem to re-appear! Instead it now works exactly as I intended it to from the beginning. (though I'm strongly suspecting that won't be the case the second any of the values other than 'createDate' actually change).

Upon closer inspection of the produced files I'm thinking that it probably has something to do with the fact that there are no line breaks in the html file when I use my custom entry. So now my questions are:
1) Am I right?
2) How should I do this?

(I tried just appending various versions of '\n', '{\n}', and {\\n} with absolutely no results to show for it. I mean I didn't think it'd make much of a difference, but one can always hope right!).

Extra info: I've been testing this by editing my personal.ini and running fff with the setting 'update epub always'.

[JimmXinu]

Originally Posted by veviara

I'm trying to customise my logpage and I've run into a problem:
I've edited logpage_entry such that there's a line break after each entry:

logpage_entry:<b>${label}:</b> <span id="${id}">${value}</span><br />

But now all entries are included every time regardless of whether they have changed or not.

...

Upon closer inspection of the produced files I'm thinking that it probably has something to do with the fact that there are no line breaks in the html file when I use my custom entry. So now my questions are:

You are correct.

Rather than parse the HTML entirely, FFF is doing very basic string searches for '<span id="%s">'%entry and '</span>\n'

I'll put out a test version shortly that removes the unnecessary \n.

FYI, To get more spacing in the HTML you can do this:

logpage_entry:
 <b>${label}:</b> <span id="${id}">${value}</span>
 <br/>

Note the leading spaces. This version will work correctly with the existing released code.

I think this may be the first time I've heard of anyone--other than me--using the log file feature.

[JimmXinu]

New Test Version Posted

2024-02-05
- Don't do random lang anymore in test1--changes series sort in Calibre.
- Don't need \n after </span> looking for log entries.