[GUI Plugin] FanFicFare

[JimmXinu]

Has anyone tried a higher slow_down_sleep_time setting for StoriesOnline?

Setting Default is only 1. Longer sleeps may help.

[JimmXinu]

New Test Version Posted

2023-06-18
- Add use_workskin option for AO3 (& squidgeworld). PR#967, thanks niacdoial

[ownedbycats]

Originally Posted by JimmXinu

New Test Version Posted

2023-06-18
- Add use_workskin option for AO3 (& squidgeworld). PR#967, thanks niacdoial

Description of this? I have a few fics that have additional CSS due to workskins and wonder if this can replace it.

[Amalthia]

Hello,

I'm seeing this error message when I try to download a story from AO3.

Malformed id selector at position 0
  line 1:
#1
^
(redacted)

Amalthia

Moderator Notice

NSFW link removed

[JimmXinu]

Originally Posted by ownedbycats

Description of this? I have a few fics that have additional CSS due to workskins and wonder if this can replace it.

Does what it says on the tin: use story's workskin. See the PR #967 for full details.

Originally Posted by Amalthia

I'm seeing this error message when I try to download a story from AO3.

Malformed id selector at position 0
  line 1:
#1
^
(redacted for NSFW)

Already fixed in the posted test version. See issue #966 for full details.

[Amalthia]

Thanks for the fast response!

[ownedbycats]

a while ago, I mentioned having trouble getting the add_to_output_css working on a specific story - it was one of the few AO3 fics I read on the site because of this. I just tried use_workskin and it worked

[DirCat]

It's not very important (it'll be downloaded next time it comes up in my email notification), but I thought you might want to see the error I got when I tried downloading a story. (I used the "Copy to clipboard" feature to show it.)

Status
Title
Author
Comment
URL
Error
Valley of the Shadow: Act III
potionpen
Malformed id selector at position 0
line 1:
#1
^
https://archiveofourown.org/works/11661429

[JimmXinu]

Originally Posted by DirCat

Malformed id selector at position 0
line 1:
#1
^

Already fixed in test version. And reported again 3 posts above.

[FandomWitch]

When cleaning my metadata I have the relationships (romantic and platontic) go into two different columns. One is the tag like, filterable, and the other is text, for use on the cover. This also allows me to edit the relationships that appear on my generated cover without affecting the actual relationships applied to the fanfic.

This was working fine (not many needed editing, totally possible manually) until I started to archive my favorite Doctor Who fics. With the various incarnations I added a The Doctor[& or /]Character metadata split. This means that a fic's cover will have both "Eleventh Doctor & Clara" as well as "The Doctor & Clara". I would like the split to not apply to the cover column but still be in the taglike filtering one. Is there a way to exclude the split from the cover column?

[ownedbycats]

For somewhat similar issues, I've created a new entry, copied the existing entry to it, and modified the new entry.

Roughly something like this - I'm a bit slow at the moment so i may have made a mistake.

[defaults]

## Creates an entry for use in the title-pages. Leading comma is because it concats to existing entries.
add_to_extra_valid_entries:,titlepage_ships

## This adds the existing ships to the new category.
include_in_titlepage_ships:ships

## Now you can run include, exclude, or replace_metadata on your titlepage_ships without it affecting the main one.
replace_metadata
 titlepage_ships=>whatever=>some ship

exclude_metadata_post:
 titlepage_ships==some ship

## Now send that to your column.
custom_columns_settings: 
titlepage_ships=>#covercolumn

[FandomWitch]

ownedbycats, thank you so much! Especially for such an easy to implement fix. This works great and it will let me tweak things even more!

[ownedbycats]

I forgot to mention this: any changes done on ships (replaces and the like) will also carry over to titlepage_ships. I think you can append .NOREPL to prevent this.

[ownedbycats]

Out of curiosity: Does NOREPL also affect the include/exclude metadatas? for example, if you exclude something, would it still appear in a NORPL'd 'copy category'?

[JimmXinu]

'.NOREPL' tells the system to *not* apply in/exclude/replace_metadata -- Only works on include_in_ lines.