Quote:
Originally Posted by ownedbycats
Question: What does an "uninitialized error" mean in the browser cache? Thankfully I got it working after clearing cache and reloading the chapters into it.
|
No idea. That string doesn't appear in the FFF code.
Quote:
Originally Posted by surpachup
I made an example in which:
- #tw is a custom column which should only contain death or mcd if any
- tags is the default tags column which should only contain alternate canon or modern
I tested it with this https://archiveofourown.org/works/41674563 and #kudos, #fandom, #notes and #ships (old settings) are populated but not tags and #tw |
It works better to use [code] around config blocks rather than [quote]. The '#' button in the 'advanced' post editor.
Code:
add_to_replace_metadata:
au=~Alternate Canon|Deviates From Canon|Alternate Universe \- Canon Divergence|[Ff]ix-[Ii]t=>alternate canon&&category=~Harry Potter|Cursed Child
au=~[Mm]odern [Ee]ra=>modern
tw=~Minor Character Death=>death
tw=~Major Character Death=>mcd
You can't use =~ there in
replace_metadata, it's only for
include/exclude_metadata_pre/post or conditionals in
replace_metadata. Yes, it's inconsistent.
include_in_tags does nothing, FFF doesn't have a metadata entry named tags. (As standard--it can be defined for individual sites or by users.)
Code:
include_subject_tags:
The Calibre Tags column is treated special for historical reasons. The
include_subject_tags setting controls what goes into Tags.
This clears the
include_subject_tags setting, telling FFF not to set anything in Calibre's Tags field. (Unless you also have
extra_subject_tags set--which is 3/4 deprecated.)