IBX-10684: Document translation management - #3249
Open
dabrt wants to merge 19 commits into
Open
Conversation
adriendupuis
marked this pull request as draft
June 19, 2026 07:12
mikadamczyk
reviewed
Jun 22, 2026
dabrt
marked this pull request as ready for review
June 25, 2026 12:41
Co-Authored-By: dabrt <dabrt@users.noreply.github.com> Co-Authored-By: Marek Nocoń <mnocon@users.noreply.github.com>
code_samples/ change report
|
ciastektk
requested changes
Jul 28, 2026
Comment on lines
+179
to
+198
| ## Manage language pairs programmatically | ||
|
|
||
| To manage language pairs programmatically, create a service class and inject `LanguagePairServiceInterface` into its constructor. | ||
| Symfony autowires it automatically so no manual service configuration is needed. | ||
|
|
||
| ``` php hl_lines="2" | ||
| [[= include_code('code_samples/translations_management/src/TranslationsManagement/TranslationPairManager.php', 14, 35) =]] | ||
| ``` | ||
|
|
||
| The service exposes the following methods: | ||
|
|
||
| | Method | Description | | ||
| |---|---| | ||
| | `createLanguagePair()` | Create a new language pair. Pass `true` as the fourth argument to overwrite an existing pair with the same source and target. | | ||
| | `updateLanguagePair()` | Update an existing language pair by ID. | | ||
| | `syncLanguagePairsForSourceAndProvider()` | Synchronize all target languages for a given source language and provider. | | ||
| | `loadLanguagePairs()` | Load all configured language pairs. | | ||
| | `deleteLanguagePairById()` | Delete a language pair by ID. | | ||
| | `deleteLanguagePairsForProvider()` | Delete all language pairs associated with a given provider. | | ||
|
|
Contributor
There was a problem hiding this comment.
IMO, this should be dropped because LanguagePairServiceInterface is not a contract and should not be exposed as example to manage Language Pairs outside of the translations management bundle.
|
|
||
| The [side-by-side translation view]([[= user_doc =]]/content_management/translate_content/#side-by-side-translation-view) is a two-column content editing interface where the source column is read-only and the target column is an editable form. | ||
|
|
||
| Content types that contain the `ibexa_landing_page` or `ibexa_form` fields are not supported, and editors can open them in the standard single-language editor only. |
Contributor
There was a problem hiding this comment.
Maybe we should to clarify that excluding a content type from the side-by-side view does not make it untranslatable. Landing Page and other excluded content types can still be auto-translated through the standard translation flow and the CLI command - only the side-by-side editing interface is unavailable for them.
2 tasks
Co-authored-by: Tomasz Kryszan <tomasz.kryszan@ibexa.co>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document translation management
Checklist