[GUI Plugin] FanFicFare

[Atherton25]

Thanks. Knowing what it was, I got the first 15 then manually added chapter 16. Once I'd done that everything worked when I tried to update it. I wonder how all that nesting happens, if it's a bug in their software or something imported that does that shit.

[JimmXinu]

As near as I can tell, converting a BeautifulSoup4 (4.10.0 to be exact) soup back to a text (str(soup)) in Calibre 6.10.0 some how crashes out instead of raising the appropriate RecursionError.

But trying it in Calibre 5.44 (BS4 version:4.9.1) does raise the error appropriately.

I forced my CLI python install to BeautifulSoup4 v4.10.0 and it worked as expected, raising RecursionError, suggesting it's something Calibre specific, not BS4.10.

This is not, apparently, limited to Calibre background job procs either. Running it in the foreground will also immediately cause the Calibre GUI to exit without any warning or details, even in debug mode.

I've opened a calibre bug(2000888) to bring this to Kovid's attention.

[ownedbycats]

Originally Posted by criscros

I have a couple of webnovels that have been stubbed, so now FFF won't update because the chapters are different. If I do overwrite always, I lose the missing chapters.
Is there a way to update and not lose chapters?

Originally Posted by ownedbycats

I'd suggest just renaming to FanficTitle (Old Version) and downloading new; often removed chapters are indicative of big rewrites.

Originally Posted by criscros

Makes sense. Even though I probably wouldn't reread the rewrite, I'd like the old chapters to be able to back reference things.
Thanks!

Just had a similar incident. The author had completed a fanfic, and removed one chapter midway through. As I didn't want to mess up my Kobo bookmarks, here's what I did:

1. Save a copy of the existing epub outside of Calibre.
2. Run 'overwrite always' on the fanfic.
3. Open both copies in ebook-edit. Take the last chapter of the overwritten version, rename it, and copy it to the other version.
4. Make other changes in the backed-up copy (table of contents, title page, etc).
5. Copy the modified backed-up copy back into Calibre. Fix the chapter numbers.

Two caveats:
1. This won't work for further updates. This fic was completed.
2. The word count on the title page will be wrong, if that bothers you much.

[Amalthia]

Hi,

I've noticed that my custom column for "genre" doesn't seem to be working for restricted access stories on A03.

I'm getting other information from the metadata for the restricted access stories, like "Characters," "Warnings," "Relationships," "Challenges," and "Categories." However, the "Additional Tags" information isn't downloading into my "genre" custom column.

These are my settings in my personal.ini.

extra_valid_entries:fandoms,comments,kudos,collections,freeformtags,freefromtags,ao3categories,chapterslashtotal

include_in_genre: freeformtags

custom_columns_settings:
 genre=>#newgenre,r

Here is a link to a restricted access story that has "Additional tags:" https://archiveofourown.org/works/37166770

Please let me know if you require any additional information.

Thanks,
Amalthia

[ownedbycats]

Speaking of AO3 authors and restricted access, I just found out a day or two ago that a lot of authors are putting their stories behind the login barrier because there's a publisher scraping AO3 fics to sell on various sites. (Amazon's pulled them down, at least.)

[JimmXinu]

Originally Posted by JimmXinu

As near as I can tell, converting a BeautifulSoup4 (4.10.0 to be exact) soup back to a text (str(soup)) in Calibre 6.10.0 some how crashes out instead of raising the appropriate RecursionError.
...
I've opened a calibre bug(2000888) to bring this to Kovid's attention.

FYI, Kovid's dealt with this, it was an issue with the windows version using a smaller stack size by default. Next version of Calibre should correctly raise RecursionError again.

Note that this won't fix the issue with too many nested tags--it will just report it correctly. Will allow continue_on_chapter_error:true to handle it.

[JimmXinu]

Originally Posted by Amalthia

I've noticed that my custom column for "genre" doesn't seem to be working for restricted access stories on A03.

For a while, I thought I was seeing this, too. But it turns out I had the lookup name of the column wrong (#newgenre vs #newgenres). Once that was corrected, it worked fine.

So all I can suggest is double & triple checking your column name...

[criscros]

Originally Posted by ownedbycats

1. This won't work for further updates. This fic was completed.

The stubbed ones I'm following are ongoing, so easier to have a copy before the stub. I've edited several other fics, so at some point I may combine what I have. Thanks!

[Amalthia]

Originally Posted by JimmXinu

For a while, I thought I was seeing this, too. But it turns out I had the lookup name of the column wrong (#newgenre vs #newgenres). Once that was corrected, it worked fine.

So all I can suggest is double & triple checking your column name...

Hi,

If the lookup name was incorrect, wouldn't it fail for all A03 downloads? Right now, it's working for non-restricted stories. It's only failing to download genre information for restricted stories.

Thanks,
Amalthia

[JimmXinu]

Originally Posted by Amalthia

If the lookup name was incorrect, wouldn't it fail for all A03 downloads? Right now, it's working for non-restricted stories. It's only failing to download genre information for restricted stories.

A good point.

Do you use always_login:true for AO3? If not, does it change things if you temporarily set that?

Do you use a customized AO3 site skin? That might change things enough to break parsing...

[Amalthia]

Originally Posted by JimmXinu

A good point.

Do you use always_login:true for AO3? If not, does it change things if you temporarily set that?

Do you use a customized AO3 site skin? That might change things enough to break parsing...

I changed my AO3 setting from always_login:false to always_login:true and downloaded the restricted story, it didn't fill in the genre information. Everything else came through though.

Amalthia

[Amalthia]

Originally Posted by JimmXinu

A good point.

Do you use a customized AO3 site skin? That might change things enough to break parsing...

I'm using the default AO3 site skin.

[JimmXinu]

Originally Posted by Amalthia

I changed my AO3 setting from always_login:false to always_login:true and downloaded the restricted story, it didn't fill in the genre information. Everything else came through though.

What about other stories that aren't restricted? Do they get genre while logged in?

UPDATE: Another question: Do you see the Genre correctly in the title page inside the book? (Assuming you display it, it is by default.)

[ownedbycats]

another thought. from the default.ini:

## (Plugin Only) - You can also populate calibre custom columns with
## the site specific metadata using custom_columns_settings (but only
## if 'Allow custom_columns_settings from personal.ini' is checked in
## the plugin GUI config.)  There are three parts, the entry name,
## then the label of the calibre custom column, then (optionally) a
## 'mode'.  'r' to Replace any existing values, 'a' to Add to existing
## value (use with tag-like columns), and 'n' for setting on New books
## only.  (Default is 'r'.)

do you get different results with 'a' rather than 'r'?

[JimmXinu]

Amalthia, you might try running Calibre in Debug mode (under Preferences dropdown) while downloading and we'll see if there's any clues in the debug log.