Menu
Feedback
Known issues
Search Resolver applying Messages translations over already translated content
Intelligent Search
ID: 865918
Backlog
Published on7/20/2023
Last updated on6/13/2024
1 min read

Summary

The Search Resolver (GraphQL layer for Intelligent Search) requests translations from the Messages service even for single-language stores or already translated content in a multi-language store.

In practice, these translations are made on top of the same "from" and "to" languages, but if the store has the automatic translation feature enabled, the string may change to something unexpected.

This affects especially strings with multiple words that may be considered from different languages, such as English words in the name of a product name that is majorly in French, and potentially dates (between the "dd/mm/yyyy" and "mm/dd/yyyy" notations).

Simulation

  • Translate any content from the store's catalog to a language different from the default;
  • Make sure there is still at least one word in a different language than the translated one;
  • Check the storefront; it won't match the translation.

Workaround

  • Disable the automatic translation;
  • Create translations for these contents using the same language as "from" and "to", for example, translating it from "fr-FR" to "fr-FR".
Contributors
1
Photo of the contributor
+ 1 contributors
Was this helpful?
Yes
No
Suggest Edits (GitHub)
Contributors
1
Photo of the contributor
+ 1 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX Community
Join our community
Request VTEX support
For personalized assistance, contact our experts
Open a support ticket
GitHubDeveloper PortalCommunityFeedback