Notebook.ai

Language displays "Language spoken by 0 characters" despite having tons of characters linked in associations.

@kazeharuhime ecoIllusionmaster Illusionmaster forum 3 comments schedule
eco
@kazeharuhime ecoIllusionmaster
Illusionmaster

I'm not sure why this is or how to fix it, but in the top header, any language I go to will display "Language spoken by 0 characters" even if I link it in the characters' "language spoken" field. I've tried unlinking and relinking a language, linking a completely different language and checking it, even creating a new language and linking that, but nothing seems to work. I assume it's doing this because there's no way to link speakers from the language page, perhaps? It's bothersome either way. I'd like it not to just display a 0 when I went through the trouble of linking it to a ton of characters…

flash_on
@andrew flash_onAdmin
verified_user Mod Admin

Hey there! I'll look into this and see what's up – and get it fixed. Thanks for the heads up!

flash_on
@andrew flash_onAdmin
verified_user Mod Admin

It turns out this was a problem with our old linking system (where we had static, hard-coded links between pages instead of our current customizable links), so it's a little more complicated to fix than I thought. However, I've gone ahead and removed the "Language spoken by 0 characters" byline (you can still see how many characters speak a language on the associations tab).

I'll need to do some tweaks first in order to re-enable the automatic counter of characters that speak a language, but in the meantime I've also enabled a feature that lets you write your own byline like you would on other pages: if you edit your Language page template here and add a text field with the label "Description" (in any category you want), then anything you write in that field will automatically populate into the byline field for that language.

For example,

I'll get the automatic counter back soon (which'll automatically display if you don't add your own description field), but hopefully that should help in the meantime (and might be a better solution for some, anyway!).

Thanks for the heads up on this issue!