From d03fabb10f784b13467c297f6ddc64bfc1f75b2d Mon Sep 17 00:00:00 2001 From: Adrien Dupuis <61695653+adriendupuis@users.noreply.github.com> Date: Mon, 24 Aug 2026 10:15:53 +0200 Subject: [PATCH 1/3] translations_management.md: Fix PHP API Ref link It generates "https://doc.ibexa.co/en/5.0//api/php_api/php_api_reference/namespaces/ibexa-contracts-translationsmanagement.html" which is a redirection --- .../translations_management/translations_management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/multisite/translations_management/translations_management.md b/docs/multisite/translations_management/translations_management.md index 3bbd07fd59..71682f0343 100644 --- a/docs/multisite/translations_management/translations_management.md +++ b/docs/multisite/translations_management/translations_management.md @@ -15,6 +15,6 @@ Translations management helps [[= product_name =]] developers and editors delive "multisite/translations_management/translate_with_cli", "multisite/translations_management/extend_translations_management", "api/event_reference/translations_management_events", - ("/api/php_api/php_api_reference/namespaces/ibexa-contracts-translationsmanagement.html", "PHP API Reference", "Ibexa\\Contracts\\TranslationsManagement"), + ("api/php_api/php_api_reference/namespaces/ibexa-contracts-translationsmanagement.html", "PHP API Reference", "Ibexa\\Contracts\\TranslationsManagement"), ], columns=3) =]] From 35a18b8fb2fae12af90ba83daf3a5a2b20651b28 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Noco=C5=84?= Date: Mon, 24 Aug 2026 10:41:47 +0200 Subject: [PATCH 2/3] Adjusted links after Symfony doc changes --- .../administration/back_office/customize_search_suggestion.md | 2 +- docs/administration/configuration/configuration.md | 2 +- .../project_organization/project_organization.md | 2 +- docs/api/php_api/php_api.md | 4 ++-- .../rest_api/extending_rest_api/creating_new_rest_resource.md | 2 +- docs/commerce/checkout/checkout.md | 2 +- docs/commerce/checkout/configure_checkout.md | 2 +- docs/content_management/field_types/type_and_value.md | 2 +- docs/content_management/workflow/workflow_api.md | 2 +- docs/release_notes/ez_platform_v3.0_deprecations.md | 2 +- docs/search/search_criteria_and_sort_clauses.md | 2 +- 11 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/administration/back_office/customize_search_suggestion.md b/docs/administration/back_office/customize_search_suggestion.md index dc185ac40b..14455c6e90 100644 --- a/docs/administration/back_office/customize_search_suggestion.md +++ b/docs/administration/back_office/customize_search_suggestion.md @@ -152,7 +152,7 @@ The template for the product suggestion item follows, named `templates/themes/ad ## Replace default suggestion source -To replace the default suggestion source, [decorate]([[= symfony_doc =]]/service_container/service_decoration.html) the built-in `BuildSuggestionCollectionEvent` subscriber with your own: +To replace the default suggestion source, [decorate]([[= symfony_doc =]]/service_container/decoration.html) the built-in `ContentSuggestionSubscriber` subscriber with your own: ```yaml services: diff --git a/docs/administration/configuration/configuration.md b/docs/administration/configuration/configuration.md index 5ff421bebb..e6e8e375b1 100644 --- a/docs/administration/configuration/configuration.md +++ b/docs/administration/configuration/configuration.md @@ -48,7 +48,7 @@ These files contain additional settings and point to the general (not environmen !!! note Configuration is tightly related to the [service container](php_api.md#service-container). - To fully understand it, you must be familiar with the service container and [its configuration]([[= symfony_doc =]]/service_container.html#service-parameters). + To fully understand it, you must be familiar with the service container and [its configuration]([[= symfony_doc =]]/service_container.html#service-container-parameters). Basic configuration handling in [[= product_name =]] is similar to what is commonly possible with Symfony. You can define key/value pairs in your configuration files. diff --git a/docs/administration/project_organization/project_organization.md b/docs/administration/project_organization/project_organization.md index 5803cea48d..c78d09cf3e 100644 --- a/docs/administration/project_organization/project_organization.md +++ b/docs/administration/project_organization/project_organization.md @@ -36,7 +36,7 @@ For more information, see [Configuration](configuration.md). If you're keeping some of your code in a bundle, dealing with core bundle semantic configuration can be tedious if you maintain it in the main `config/packages/ibexa.yaml` configuration file. -You can import configuration from a bundle by following the Symfony tutorial [How to Import Configuration Files/Resources]([[= symfony_doc =]]/service_container/import.html). +You can import configuration from a bundle by following the Symfony tutorial [How to Import Configuration Files/Resources]([[= symfony_doc =]]/service_container.html#service-container-imports-directive). ## Versioning a project diff --git a/docs/api/php_api/php_api.md b/docs/api/php_api/php_api.md index 29fd731ce1..4c8f2e8eab 100644 --- a/docs/api/php_api/php_api.md +++ b/docs/api/php_api/php_api.md @@ -47,7 +47,7 @@ The full list of available services covers: You can access the PHP API by injecting relevant services into your code: - By using [auto-wiring]([[= symfony_doc =]]/service_container/autowiring.html), and the service class name in the `Ibexa\Contracts` namespace (see `bin/console debug:autowiring | grep Ibexa.Contracts`). -- By using [service parameters]([[= symfony_doc =]]/service_container.html#service-parameters), and service aliases (see `bin/console debug:autowiring | grep ibexa.api`). +- By using [service parameters]([[= symfony_doc =]]/service_container.html#service-container-parameters), and service aliases (see `bin/console debug:autowiring | grep ibexa.api`). - By using the repository's `get[ServiceName]()` methods, for example, [`Repository::getContentService()`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Repository.html#method_getContentService), or [`getUserService()`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Repository.html#method_getUserService). (Prefer injecting several Repository's dedicated services instead of the whole Repository if the Repository itself isn't needed.) @@ -163,7 +163,7 @@ try { [[= product_name =]] uses the [Symfony service container]([[= symfony_doc =]]/service_container.html) for dependency resolution. -[Symfony dependency injection]([[= symfony_doc =]]/components/dependency_injection.html) ensures that any required services are available in your custom code (for example, controllers) when you inject them into the constructor. +[Symfony dependency injection]([[= symfony_doc =]]/service_container.html) ensures that any required services are available in your custom code (for example, controllers) when you inject them into the constructor. Symfony service container uses service tags to dedicate services to a specific purpose. They're usually used for extension points. diff --git a/docs/api/rest_api/extending_rest_api/creating_new_rest_resource.md b/docs/api/rest_api/extending_rest_api/creating_new_rest_resource.md index ccb0a79740..a140470749 100644 --- a/docs/api/rest_api/extending_rest_api/creating_new_rest_resource.md +++ b/docs/api/rest_api/extending_rest_api/creating_new_rest_resource.md @@ -194,7 +194,7 @@ ibexa_rest: The `router.generate` renders a URI based on the name of the route and its parameters. The parameter values can be a real value or a placeholder. For example, `'router.generate("ibexa.rest.load_location", {locationPath: "1/2"})'` results in `/api/ibexa/v2/content/locations/1/2` while `'router.generate("ibexa.rest.load_location", {locationPath: "{locationPath}"})'` gives `/api/ibexa/v2/content/locations/{locationPath}`. -This syntax is based on Symfony's [expression language]([[= symfony_doc =]]/components/expression_language.html), an extensible component that allows limited/readable scripting to be used outside the code context. +This syntax is based on Symfony's [expression language]([[= symfony_doc =]]/expression_language.html), an extensible component that allows limited/readable scripting to be used outside the code context. In this example, `app.rest.greeting` is available in every SiteAccess (`default`): diff --git a/docs/commerce/checkout/checkout.md b/docs/commerce/checkout/checkout.md index 5759a6c288..dc9ff161e9 100644 --- a/docs/commerce/checkout/checkout.md +++ b/docs/commerce/checkout/checkout.md @@ -15,7 +15,7 @@ From the front-end perspective, it's a reusable component that provides access t Depending on the model of shopping process that you need to use, the checkout process can range between a straightforward and extremely complicated one. To allow for this variation, the component is highly configurable and extensible: -- Like the editorial workflow, it relies on [Symfony Workflow]([[= symfony_doc =]]/components/workflow.html) +- Like the editorial workflow, it relies on [Symfony Workflow]([[= symfony_doc =]]/workflow.html) - It exposes [PHP API](checkout_api.md) that allows for workflow manipulation - It exposes Twig functions used for checkout rendering diff --git a/docs/commerce/checkout/configure_checkout.md b/docs/commerce/checkout/configure_checkout.md index d302f9e55a..4651b771bf 100644 --- a/docs/commerce/checkout/configure_checkout.md +++ b/docs/commerce/checkout/configure_checkout.md @@ -13,7 +13,7 @@ When you work with your Commerce implementation, you can review and modify the c ## Configure checkout workflow -Checkout workflow relies on [Symfony Workflow]([[= symfony_doc =]]/components/workflow.html). +Checkout workflow relies on [Symfony Workflow]([[= symfony_doc =]]/workflow.html). Each transition represents a separate checkout step. By default, the checkout process is configured to render each step based on a separate set of libraries and templates. diff --git a/docs/content_management/field_types/type_and_value.md b/docs/content_management/field_types/type_and_value.md index 085755f52b..8fdb5a7000 100644 --- a/docs/content_management/field_types/type_and_value.md +++ b/docs/content_management/field_types/type_and_value.md @@ -135,7 +135,7 @@ services: ### `parent` -As described in the [Symfony service container documentation]([[= symfony_doc =]]/service_container/parent_services.html), the `parent` config key indicates that you want your service to inherit from the parent's dependencies, including constructor arguments and method calls. +As described in the [Symfony service container documentation]([[= symfony_doc =]]/service_container/advanced_definitions.html#parent-services), the `parent` config key indicates that you want your service to inherit from the parent's dependencies, including constructor arguments and method calls. This helps to avoid repetition in your field type configuration and keeps consistency between all field types. If you need to inject other services into your Type class, skip using the `parent` config key. diff --git a/docs/content_management/workflow/workflow_api.md b/docs/content_management/workflow/workflow_api.md index bb822c7f08..a0f7560193 100644 --- a/docs/content_management/workflow/workflow_api.md +++ b/docs/content_management/workflow/workflow_api.md @@ -30,7 +30,7 @@ To get information about a specific workflow for a content item, use [`WorkflowS !!! tip - `marking`, a term from [Symfony Workflow]([[= symfony_doc =]]/components/workflow.html), + `marking`, a term from [Symfony Workflow]([[= symfony_doc =]]/workflow.html), refers to a state in a workflow. If you already have a [`VersionInfo`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-VersionInfo.html) object, use [`WorkflowServiceInterface::loadWorkflowMetadataForVersionInfo`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Workflow-Service-WorkflowServiceInterface.html#method_loadWorkflowMetadataForVersionInfo) to avoid loading the full [`Content`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Content.html). diff --git a/docs/release_notes/ez_platform_v3.0_deprecations.md b/docs/release_notes/ez_platform_v3.0_deprecations.md index 81c187b322..7347eeca0e 100644 --- a/docs/release_notes/ez_platform_v3.0_deprecations.md +++ b/docs/release_notes/ez_platform_v3.0_deprecations.md @@ -474,7 +474,7 @@ Don't store the values globally. Every time the value is needed call `ConfigReso #### AbstractController The `eZ\Bundle\EzPublishCoreBundle\Controller` now extends `Symfony\Bundle\FrameworkBundle\Controller\AbstractController` instead of `Symfony\Bundle\FrameworkBundle\Controller\Controller` which has limited access to the [service container](https://doc.ibexa.co/en/3.3/api/public_php_api/#service-container). -For details, see [Service Subscribers Locators]([[= symfony_doc =]]/service_container/service_subscribers_locators.html). +For details, see [Service Subscribers Locators]([[= symfony_doc =]]/service_container/subscribers_locators.html). The `Symfony\Bundle\FrameworkBundle\Command\ContainerAwareCommand` is deprecated, use `Symfony\Component\Console\Command\Command` instead. diff --git a/docs/search/search_criteria_and_sort_clauses.md b/docs/search/search_criteria_and_sort_clauses.md index 0fb9e40b31..8dbee53d2d 100644 --- a/docs/search/search_criteria_and_sort_clauses.md +++ b/docs/search/search_criteria_and_sort_clauses.md @@ -103,7 +103,7 @@ Ibexa\Core\Search\Legacy\Content\Location\Gateway\SortClauseHandler\Location\Dep - {name: ibexa.search.legacy.gateway.sort_clause_handler.location} ``` -For more information about passing parameters, see [Symfony Service Container documentation]([[= symfony_doc =]]/service_container.html#service-parameters). +For more information about passing parameters, see [Symfony Service Container documentation]([[= symfony_doc =]]/service_container.html#service-container-parameters). ## Search using custom Field Criterion [REST] From 5123e28cc0576c4a5f32acc20c7af77d640a456b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tomasz=20D=C4=85browski?= <64841871+dabrt@users.noreply.github.com> Date: Mon, 24 Aug 2026 11:34:44 +0200 Subject: [PATCH 3/3] Fix a broken link in release notes (#3364) --- docs/release_notes/ibexa_dxp_v5.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release_notes/ibexa_dxp_v5.0.md b/docs/release_notes/ibexa_dxp_v5.0.md index c51c8ff25c..953486c282 100644 --- a/docs/release_notes/ibexa_dxp_v5.0.md +++ b/docs/release_notes/ibexa_dxp_v5.0.md @@ -53,7 +53,7 @@ Accepted translations are given the "Translated" status. The **Versions** tab shows a **Translation status** column with review status badges for draft translations created with automatic translation. -For more information, see [Translation review](https://doc.ibexa.co/en/5.0/multisite/translations_management/configure_translations_management/translations_management_guide/#translation-review). +For more information, see [Translation review](https://doc.ibexa.co/en/5.0/multisite/translations_management/translations_management_guide/#translation-review). ### Developer experience