Allow to programatically skip translation process

Created on 16 July 2024, 9 months ago

Problem/Motivation

In some use cases we might want to entirely skip the translation process when saving entities to improve performances and save money (API usage is not free).

Example use case:
I need to create an update task to set a new untranslatable field value on all my nodes. This should not be impacted by TMGMT as this has no impact on translations.

Proposed resolution

Allow the developer to set a flag on the entity to skip the translation process, similar that what Search API does with its search_api_skip_tracking property.

Feature request
Status

Active

Version

1.0

Component

Source: Node

Created by

🇫🇷France duaelfr Montpellier, France

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

Merge Requests

Comments & Activities

  • Issue created by @duaelfr
  • Pipeline finished with Failed
    9 months ago
    Total: 325s
    #225614
  • Status changed to Needs review 9 months ago
  • 🇫🇷France duaelfr Montpellier, France
  • 🇫🇷France duaelfr Montpellier, France

    FYI phpunit failure on the MR seems unrelated

  • Status changed to Needs work 5 months ago
  • 🇨🇭Switzerland berdir Switzerland

    Open to the idea, but I'd prefer to add something to ContinuousManager instead of undocumented properties, I have no idea when we'll manage that, but I want to deprecate and remove the ability to put arbitrary stuff on content entities.

    Could be a new method to set a flag and then getContinuousJobs() would just return nothing, or an explicit method to check for that.

Production build 0.71.5 2024