The title and meta tags editing tool must support localization. But, it currently does not, making the tool completely useless for multilingual communities.

I'm not sure I follow? Just use the primary community language for those fields.

 

I'm not sure I follow? Just use the primary community language for those fields.

When a community is multilingual, it does not have a 'primary community language.' When a community has a 'primary community language,' it is not a multilingual community by definition.

Yes, but meta tags are one and done, you can't serve them up in different languages based on the viewer. It'll confuse Google, et al.

 

Yes, but meta tags are one and done, you can't serve them up in different languages based on the viewer. It'll confuse Google, et al.

That's not quite true. This tool also manipulates titles, which are translatable at the category name level. However, they become untranslatable when you use this tool.

This means that while forum section titles can be translatable even in the current state of the software, using this tool effectively breaks that ability, as you are forced to stick with only one language.

The category names are just an example. The same problem exists everywhere, especially important in the forum's main page title.

Edited October 14, 2024Oct 14 by aia

 

That's not quite true. This tool also manipulates titles, which are translatable at the category name level. However, they become untranslatable when you use this tool.

This means that while forum section titles can be translatable even in the current state of the software, using this tool effectively breaks that ability, as you are forced to stick with only one language.

The category names are just an example. The same problem exists everywhere, especially important in the forum's main page title.

This is true, but guests and bots will get whatever your default language is, so just use that language for any custom meta tags. Google isn't going to sign up, log in and change languages, so don't worry about that aspect.

 

but guests and bots will get whatever your default language is

That's not true, guests and bots will receive whatever is set in their Accept-Language header, which is configured at the browser level for users.

Additionally, we have more than just guests and bots in our communities. All users are affected by this issue, regardless of whether they are bots, guests, or logged-in users.

Edited October 14, 2024Oct 14 by aia