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
Searching was requested in bug #7 which was closed for an unrelated question tacked on to the issue, but not being able to search is still an issue.
In order to make translated columns searchable they would need to be split out like the slug, instead of stored in the data json.
Since we already have a working mechanism for the slugs, how hard would it be to allow arbitrary columns to have their localized versions stored in separate columns instead of in the data json? From there all you need is a tweaked search query and you've got working multilingual search.
The text was updated successfully, but these errors were encountered:
Searching was requested in bug #7 which was closed for an unrelated question tacked on to the issue, but not being able to search is still an issue.
In order to make translated columns searchable they would need to be split out like the slug, instead of stored in the data json.
Since we already have a working mechanism for the slugs, how hard would it be to allow arbitrary columns to have their localized versions stored in separate columns instead of in the data json? From there all you need is a tweaked search query and you've got working multilingual search.
The text was updated successfully, but these errors were encountered: