-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can we support multiple languages ? #234
Comments
@mobilelifeful edited your original issue to just the parts provided, and removed the template parts for brevity. |
Looks like there's a whole section on this over at https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/ We also have a touch of WPML support enabled as well with the plugin, in case that's what you're using for your internationalization Beyond that, we're admittedly pretty limited out of box for configuration for handling multiple languages in a given site owner's indexes, but I have to imagine it's possible to accomplish overall with our hooks system to configure as needed. |
Using translatepress plugin to help me translate the site, search-wpml-algolia plugin uses some of WebDevStudios code, wonder if WebDevStudios can support multiple languages search when translatepress is used. |
I suspect it's possible as a whole already, as we have all of the facility to index content, the question is really how to best do that with the least amount of work. Biggest thing is keeping the content potentially separate, and serving the correct version to users, based on chosen language when viewing the site. |
no, I tested it, wp-search-with-algolia work with multiple languages when search-wpml-algolia plugin is installed which also requires WPML is installed, |
If we're going to aim for adding out-of-box support, we'd definitely need to test and confirm behavior, and I know all of our WPML integrations are over in https://github.com/WebDevStudios/wp-search-with-algolia/blob/main/includes/class-algolia-compatibility.php which is mostly checking if WPML is enabled, and then doing language switching. We'd need to explore doing the same, but with TranslatePress instead. |
Any option we can enable to provide the log ? |
Adding this issue here just for reference: algolia/algoliasearch-wordpress#567 |
Looks like TranslatePress does a lot of custom tables to store translations and somehow maps them to the correct spot.
This will make it difficult to index, as compared to other internationalization plugins that rely on unique post entries that are easy to get indexed. |
Describe the bug
A clear and concise description of what the bug is.
A site build in English and Spanish, each post and page are organized in www.example.com/en or www.example.com/es
The text was updated successfully, but these errors were encountered: