You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The topic itself gets correctly translated but not the topic area linked to it, even though the topic area has its localized data defined.
Correct would be:
I tried to translate the slugs of the topic_area as well, but upon saving, a Topic always saves the 'DE' slug of the topic_area regardless of the language. I'm not sure if this is causing the behavior:
title: Abfall
topic_area: umwelt
updated_by: df6eb467-9bfd-4972-ba55-21428e1f1454
updated_at: 1705573702
blueprint: topic
localizations:
fr:
title: Déchets
topic_area: umwelt <- This slug stays on default language even if the slug in the "FR" version is defined as "environnement".
slug: abfall
updated_by: df6eb467-9bfd-4972-ba55-21428e1f1454
updated_at: 1707236200
How to reproduce
Start a Statamic Multisite Project.
Create a Taxonomy for all languages.
Create a second Taxonomy for all languages.
Link the second Taxonomy to the first with a Taxonomy Terms field. This establishes a relationship between the two taxonomies, allowing terms from the second taxonomy to be associated with terms from the first.
Add a Term for both taxonomies (test content) in all languages. Ensure that you provide translations for these terms in all the languages supported by your multisite setup.
In the term of the first taxonomy, link the term of the second taxonomy with the Taxonomy Terms field. This step involves selecting a term from the second taxonomy to associate with a term from the first taxonomy.
Save your changes.
Open the GraphQL Editor (make sure to enable the GraphQL API and allow the created taxonomies). This involves configuring your Statamic settings to ensure that GraphQL is enabled and that the newly created taxonomies are accessible via the GraphQL API.
Use the query from the "Bug description" but replace the names so that it matches with the created Taxonomies and languages.
Now filter by site, and you will see that the linked taxonomy doesn't get translated. This indicates that while the primary taxonomy term translates according to the site language, the linked taxonomy term does not, retaining its default language instead.
Bug description
We have a Taxonomy named "Topics". It contains a text field "title" and a Taxonomy Terms field "topic_area" (a taxonomy linked to a taxonomy).
We use the "topic_area" field to group the topics for a filter in our frontend.
Both Taxonomies exist in multiple languages: DE, FR, IT.
Correct
This is the query to fetch the topics in DE:
Correct result:
Incorrect
When filtered by e.g. FR language
Expected
The topic itself gets correctly translated but not the topic area linked to it, even though the topic area has its localized data defined.
Correct would be:
To mention
I tried to translate the slugs of the topic_area as well, but upon saving, a Topic always saves the 'DE' slug of the topic_area regardless of the language. I'm not sure if this is causing the behavior:
How to reproduce
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
None
Additional details
No response
The text was updated successfully, but these errors were encountered: