Hi,
It should work right out of the bat.
`The way the plugin is designed is by using individual strings, making it quite intuitive not having to create a separate page for each translated page.
As pages are dynamically created they are not found in “pages – all pages / posts – all posts / product – all products / etc.”
This mean that by default you cannot see the page/post/product in the second language (search bar) until someone (you or a user) enter especially on the page/posting/translated product.
After someone accesses the product; that product will appear in the search bar.
Hi Christian,
I get that. and we did it, we ensured all the products and pages were opened so that the translation will be stored on the database and can be searched. but we only the search is only applied to the language. Like for example, on our english page, we can search for anything in english language only. if we put korean characters it will not show. also the other way around, but we did add english characters now so using english text in korean will show results.
https://www.familyk.ae/ – here is our website for reference. Is this because of the translation plugin or search plugin.
thanks
Unfortunately there is a limitation to how well this will work and search will return results in all languages at once. It’s just that if you search for something in english, chances are most results will be those in english, not the other languages. And vice-versa.
For the time being we can’t limit 100% to show results from just that language you’re currently on.
