Add option to index default translations of entities not available in the requested languages

Created on 27 August 2024, 4 months ago
Updated 15 September 2024, 3 months ago

Problem/Motivation

For a website we're developing, we don't want entities to be excluded from the search index if they aren't available in one of the requested languages. In that case, we want the default translation to be indexed.

Proposed resolution

Add a new setting to the content data source and alter the behaviour if it's enabled.

✨ Feature request
Status

Postponed: needs info

Version

1.0

Component

General code

Created by

πŸ‡§πŸ‡ͺBelgium dieterholvoet Brussels

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @dieterholvoet
  • Merge request !164Add index_missing option β†’ (Open) created by dieterholvoet
  • Status changed to Needs review 4 months ago
  • πŸ‡§πŸ‡ͺBelgium dieterholvoet Brussels
  • Pipeline finished with Failed
    4 months ago
    Total: 365s
    #265823
  • Pipeline finished with Success
    4 months ago
    Total: 432s
    #265827
  • Pipeline finished with Failed
    4 months ago
    Total: 393s
    #265926
  • Status changed to Postponed: needs info 3 months ago
  • πŸ‡¦πŸ‡ΉAustria drunken monkey Vienna, Austria

    Does the β€œLanguage (with fallback)” maybe already provide the functionality you want? This indexes each translation just once, but then matches also the default (or other fallback) translation at search time when a translation in the desired language is not available.

  • πŸ‡§πŸ‡ͺBelgium dieterholvoet Brussels

    No it doesn't. We have separate search indexes per language so we need the fallback to happen add index time, not search time.

  • πŸ‡§πŸ‡ͺBelgium dieterholvoet Brussels

    Never mind, I was able to make it work this way by also indexing content in the fallback language and filtering by language during search time.

Production build 0.71.5 2024