[JimmXinu]

Originally Posted by mehetabelo

Adding a custom column entry on the title page doesn't seem to be working for me. ...

The only thing I can think of is that maybe you don't have the checkbox set to send existing calibre columns into FFF update. See attached.

As for extra_titlepage_entries: calibre_cust_words vs add_to_titlepage_entries:,calibre_cust_words, they are slightly different ways to allow additional configuration without replacing lengthy default lines. They were added at different times. You almost certainly should be using one or the other, but not both.

The extra_* params came first and only work on a few ini params. In this case, titlepage_entries. When titlepage_entries is used, both titlepage_entries and extra_titlepage_entries are fetched and concatenated. Both follow the ordinary section precedence rules for FFF ini params.

The ordinary precedence order for sections (using epub from dramione.org as an example) from least to most is:

1. [defaults]
2. [dramione.org]
3. [epub]
4. [dramione.org:epub]
5. [overrides]

A param key word in [defaults] is the most general version and will be 'overwritten' by the same key word in any lower section. The param key word in [overrides], the highest precedence section, beats everything else. (It actually works by looking in each section from [overrides] to [defaults] and stopping at the first one it finds.)

So you can set extra_titlepage_entries in [dramione.org] without overwriting titlepage_entries from [defaults]. But only once. If you set extra_titlepage_entries in [epub], it overwrites the version from [dramione.org]

The 'add_to_' mechanism was added later to both generalize it for all ini params and add more flexibility to allow more specific sections to 'add to' the ini params from more general sections without having to repeat everything. The interesting part is that each section's add_to_s are applied and from most general to most specific:

Here's an example from my own personal.ini:

[defaults]
add_to_replace_metadata:
 genre=>Comedy=>Humor
 category=>StarTrek=>Star Trek
 category=>Warhammer 40,000=>Warhammer 40k

[epub]
add_to_replace_metadata:
 fulldownload=>^.*$=>Yes

[forums.spacebattles.com]
add_to_replace_metadata:
 title=>Wail of the Banshee 3: Boxhead Blues and the Zombocalypse=>Wail of the Banshee

When I download a story from forums.spacebattles.com, my effective replace_metadata is:

replace_metadata:
#from [defaults]
 genre=>Comedy=>Humor
 category=>StarTrek=>Star Trek
 category=>Warhammer 40,000=>Warhammer 40k
#from [forums.spacebattles.com]
 title=>Wail of the Banshee 3: Boxhead Blues and the Zombocalypse=>Wail of the Banshee
#from [epub]
 fulldownload=>^.*$=>Yes

The 'gotcha' about 'add_to_' is that it's a string concatenation, which is why you need the include the leading ',' when it's a list like titlepage_entries instead of replace_metadata.

This really isn't as complex in practice as it is to explain. The code for it is only a few lines.