Fixes - first batch

mnocon · mnocon · commit 71f58902709b · 2026-04-23T12:55:55.000+02:00
diff --git a/code_samples/back_office/components/twig_components.yaml b/code_samples/back_office/components/twig_components.yaml
@@ -12,7 +12,6 @@ ibexa_twig_components:
             priority: 0
             arguments:
                 content: '<b>Hello world!</b>'
-    admin-ui-user-menu:
         duplicated_user_menu:
             type: menu
             arguments:
diff --git a/code_samples/back_office/online_editor/config/packages/custom_plugin.yaml b/code_samples/back_office/online_editor/config/packages/custom_plugin.yaml
diff --git a/code_samples/front/shop/order-management/config/packages/ibexa.yaml b/code_samples/front/shop/order-management/config/packages/ibexa.yaml
@@ -65,7 +65,7 @@ framework:
                     to:
                         - dropped
 
-// ...
+# ...
 
 ibexa:
     repositories:
diff --git a/code_samples/front/shop/payment/src/bundle/Resources/config/services/payment_method.yaml b/code_samples/front/shop/payment/src/bundle/Resources/config/services/payment_method.yaml
@@ -8,7 +8,7 @@ services:
             $domain: <translation_domain>
         tags:
             - { name: ibexa.payment.payment_method.type, alias: new_payment_method_type }
-services:
+
     App\Payment\PaymentMethod\Voter\NewPaymentMethodTypeVoter:
         tags:
-            - { name: ibexa.payment.payment_method.voter, type: new_payment_method_type }
+            - { name: ibexa.payment.payment_method.voter, type: new_payment_method_type }
diff --git a/code_samples/recommendations/config/packages/ibexa_connector_raptor.yaml b/code_samples/recommendations/config/packages/ibexa_connector_raptor.yaml
@@ -9,8 +9,8 @@ ibexa:
                 # Raptor Recommendations API key
                 recommendations_api_key: ~ # Required
 
-                # Raptor Recommendations API URL, optional, set by default
-                recommendations_api_url: '%ibexa.connector.raptor.recommendations.api_url%'
+                # Raptor Recommendations API URI, optional, set by default
+                recommendations_api_uri: '%ibexa.connector.raptor.recommendations.api_uri%'
 ibexa_connector_raptor:
     # When enabled, tracking exceptions are thrown instead of being silently handled
     strict_exceptions: true
diff --git a/docs/administration/configuration/dynamic_configuration.md b/docs/administration/configuration/dynamic_configuration.md
@@ -18,7 +18,7 @@ parameters:
     # Internal configuration
     ibexa.site_access.config.default.content.default_ttl: 60
     ibexa.site_access.config.site_group.content.default_ttl: 3600
- 
+
     # Here "myapp" is the namespace, followed by the SiteAccess name as the parameter scope
     # Parameter "my_param" will have a different value in site_group and admin_group
     myapp.site_group.my_param: value
diff --git a/docs/api/graphql/graphql_customization.md b/docs/api/graphql/graphql_customization.md
@@ -68,9 +68,9 @@ Mutation:
             createSomething:
                 builder: Mutation
                 builderConfig:
-                        inputType: CreateSomethingInput
-                        payloadType: SomethingPayload
-                        mutateAndGetPayload: '@=mutation('CreateSomething', [value])'
+                    inputType: CreateSomethingInput
+                    payloadType: SomethingPayload
+                    mutateAndGetPayload: "@=mutation('CreateSomething', [value])"
 
 CreateSomethingInput:
     type: relay-mutation-input
diff --git a/docs/api/rest_api/rest_api_authentication.md b/docs/api/rest_api/rest_api_authentication.md
@@ -325,10 +325,15 @@ For more information, see [HTTP Authentication: Basic and Digest Access Authenti
 If the installation has a dedicated host for REST, you can enable HTTP basic authentication only on this host by setting a firewall like in the following example before the `ibexa_front` one:
 
 ```yaml
+security:
+    firewalls:
+        # ...
         ibexa_rest:
             host: ^api\.example\.com$
             http_basic:
                 realm: Ibexa DXP REST API
+        #ibexa_front
+        # ...
 ```
 
 !!! caution "Back office uses REST API"
diff --git a/docs/commerce/checkout/reorder.md b/docs/commerce/checkout/reorder.md
@@ -54,11 +54,11 @@ framework:
             places:
                 !php/const Ibexa\OrderManagement\Value\Status::COMPLETED_PLACE:
                     metadata:
-                        ...
+                        # ...
                         can_be_reordered: true
                 !php/const Ibexa\OrderManagement\Value\Status::CANCELLED_PLACE:
                     metadata:
-                        ...
+                        # ...
                         can_be_reordered: true
 
 ```
diff --git a/docs/commerce/payment/payum_integration.md b/docs/commerce/payment/payum_integration.md
@@ -43,7 +43,7 @@ ibexa_connector_payum:
         refunded: cancelled
         captured: pending
         authorized: authorized
-[...]
+# ...
 ```
 
 ## Payment service name translations
diff --git a/docs/content_management/data_migration/managing_migrations.md b/docs/content_management/data_migration/managing_migrations.md
@@ -50,7 +50,7 @@ You can configure a different folder by using the following settings:
 
 ``` yaml
 ibexa_migrations:
-    migration_directory: %kernel.project_dir%/src/Migrations/MyMigrations/
+    migration_directory: '%kernel.project_dir%/src/Migrations/MyMigrations/'
     migrations_files_subdir: migration_files
 ```
 
@@ -64,7 +64,6 @@ ibexa_migrations:
     ``` yaml
     ibexa_migrations:
         migration_directory: '%kernel.project_dir%/data/<repository>'
-        ...
     ```
 
     Then, when you run the migration command, you must use the [`--siteaccess` option](exporting_data.md#siteaccess) and provide the name of the SiteAccess that you want to migrate.
diff --git a/docs/content_management/field_types/field_type_storage.md b/docs/content_management/field_types/field_type_storage.md
@@ -147,7 +147,7 @@ services:
         autoconfigure: true
         public: false
 
-    App\FieldType\MyField\Storage\MyFieldStorage: ~
+    App\FieldType\MyField\Storage\MyFieldStorage:
         tags:
             - {name: ibexa.field_type.storage.external.handler, alias: myfield}
 ```
diff --git a/docs/content_management/images/add_image_asset_from_dam.md b/docs/content_management/images/add_image_asset_from_dam.md
@@ -49,15 +49,15 @@ Next, in `config/packages/ibexa.yaml`, set the `dam.html.twig` template for the
 For more information about displaying content, see [Content rendering](render_content.md).
 
 ``` yaml
- ibexa:
-   system:
-     site:
-       content_view:
-         embed:
-           image_dam:
-             template: '@ibexadesign/embed/dam.html.twig'
-             match:
-               Identifier\ContentType: <dam_image_content_type_identifier>
+ibexa:
+    system:
+        site:
+            content_view:
+                embed:
+                    image_dam:
+                        template: '@ibexadesign/embed/dam.html.twig'
+                        match:
+                           Identifier\ContentType: <dam_image_content_type_identifier>
 ```
 
 In your [configuration file](configuration.md#configuration-files) add the following configuration:
diff --git a/docs/content_management/url_management/url_management.md b/docs/content_management/url_management/url_management.md
@@ -67,13 +67,13 @@ ibexa:
             url_checker:
                 handlers:
                     http:
-                    	enabled: true
-                    	batch_size: 64
+                        enabled: true
+                        batch_size: 64
                     https:
-                    	enabled: true
-                    	ignore_certificate: false
+                        enabled: true
+                        ignore_certificate: false
                     mailto:
-                    	enabled: false
+                        enabled: false
 ```
 
 Available options are protocol-specific.
@@ -128,7 +128,6 @@ Then you must register the service with an `ibexa.url_checker.handler` tag, like
 ```yaml
 app.url_checker.handler.custom:
     class: 'App\URLChecker\Handler\CustomHandler'
-    ...
     tags:
         - { name: ibexa.url_checker.handler, scheme: custom }
 ```
diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md b/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md
@@ -291,7 +291,7 @@ With the same content structure as above, the `[Child]` location is moved below
 
 The new structure is then:
 
-```yaml
+```text
    - [Home] (content-id=52, location-id=2)
      ez-all c52 ct42 l2 pl1 p1 p2
      |
diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md b/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md
@@ -142,6 +142,9 @@ ibexa:
 If the Varnish server is protected by Basic Auth, specify the Basic Auth credentials within the `purge_servers` setting using the format:
 
 ``` yaml
+ibexa:
+    system:
+        my_siteaccess_group:
             http_cache:
                 purge_servers: [http://myuser:mypasswd@my.varnish.server:8081]
 ```
diff --git a/docs/recommendations/raptor_integration/connector_installation_configuration.md b/docs/recommendations/raptor_integration/connector_installation_configuration.md
@@ -35,7 +35,7 @@ To configure the Raptor connector, use the `ibexa.system.<scope>.connector_rapto
     - `client` - tracking is executed in the browser using JavaScript snippets generated by the [Twig functions](recommendations_twig_functions.md) and included in the templates. This approach may be blocked by ad blockers.
     - `server` - tracking is handled on the backend, with events sent directly to the tracking API. It's not affected by ad blockers.
 - `recommendations_api_key` - an API key used to authenticate requests to the Recommendations API. This key allows the connector to retrieve personalized recommendations from the recommendation engine. You can find this value as ["API key"](connector_installation_configuration.md#recommendations-api-key) in Raptor Control Panel.
-- `recommendations_api_url` (optional) - overrides the default Raptor address, do not set it unless a custom endpoint is required.
+- `recommendations_api_uri` (optional) - overrides the default Raptor address, do not set it unless a custom endpoint is required.
 
 By default, `tracking_type` is set to `client` as client-side tracking is the standard Raptor mode.
 To understand the differences between client and server tracking types, including their advantages and disadvantages, refer to the [Raptor documentation](https://content.raptorservices.com/help-center/client-side-vs.-server-side-tracking).
diff --git a/docs/release_notes/ez_platform_v2.4.md b/docs/release_notes/ez_platform_v2.4.md
@@ -197,18 +197,18 @@ The biggest benefit of this feature is saving load time on complex landing pages
     2\. Add the following configuration to `/app/config/config.yml`
 
     ``` yaml
-     lexik_jwt_authentication:
-         secret_key: '%secret%'
-         encoder:
+    lexik_jwt_authentication:
+        secret_key: '%secret%'
+        encoder:
              signature_algorithm: HS256
          # Disabled by default, because Page Builder uses custom extractor
-         token_extractors:
-             authorization_header:
-                 enabled: false
-             cookie:
-                 enabled: false
-             query_parameter:
-                 enabled: false
+        token_extractors:
+            authorization_header:
+                enabled: false
+            cookie:
+                enabled: false
+            query_parameter:
+                enabled: false
     ```
 
     By default `HS256` is used as signature algorithm for generated token but we strongly recommend switching to SSH keys.
@@ -218,23 +218,23 @@ The biggest benefit of this feature is saving load time on complex landing pages
     3\. Add `EzSystems\EzPlatformPageBuilder\Security\EditorialMode\TokenAuthenticator` authentication provider to `ezpublish_front` firewall before `form_login` in `app/config/security.yml`:
 
     ``` yaml
-     security:
+    security:
          # ...
-         firewalls:
-             ezpublish_front:
-                 # ...
-                 simple_preauth:
-                     authenticator: 'EzSystems\EzPlatformPageBuilder\Security\EditorialMode\TokenAuthenticator'
-                 form_login:
-                     require_previous_session: false
-                 # ...
+        firewalls:
+            ezpublish_front:
+                # ...
+                simple_preauth:
+                    authenticator: 'EzSystems\EzPlatformPageBuilder\Security\EditorialMode\TokenAuthenticator'
+                form_login:
+                    require_previous_session: false
+                # ...
     ```
 
     4\. Make sure that parameter `page_builder.token_authenticator.enabled` has value `true`. If the parameter isn't present, add it to `/app/config/config.yml`:
 
     ``` yaml
-     # ...
-     parameters:
+    # ...
+    parameters:
         # ...
         page_builder.token_authenticator.enabled: true
     ```
diff --git a/docs/search/search_engines/elasticsearch/configure_elasticsearch.md b/docs/search/search_engines/elasticsearch/configure_elasticsearch.md
@@ -182,7 +182,7 @@ If your Elasticsearch server is protected by HTTP authentication, you must provi
 In the basic authentication, you must pass the following parameters:
 
 ``` yaml
-<connection_name>
+<connection_name>:
     # ...
     authentication:
         type: basic
@@ -377,36 +377,36 @@ Index names use the following pattern:
     You can create index templates with settings that apply to a specific language only, for example, to eliminate stop words from the index, or help divide concatenations.
     You use patterns to identify index templates that contain settings specific for a given language:
 
-  ``` yaml
-  ibexa_elasticsearch:
+``` yaml
+ibexa_elasticsearch:
     # ...
     index_templates:
         default_en_us:
             patterns: ['default_*', '*eng_us*']
-            # ...
-  ```
+        # ...
+```
 
 - `settings` - Settings under this key control all aspects related to an index.
 
 For more information and a list of available settings, see [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/8.19/index-modules.html#index-modules-settings).
 
     For example, you can define settings that convert text into a format that is optimized for search, like a normalizer that changes a case of all phrases in the index:
 
-  ``` yaml
-    ibexa_elasticsearch:
-        # ...
-            index_templates:
-                default:
-                    # ...
-                    settings:
-                        analysis:
-                            normalizer:
-                                lowercase_normalizer:
-                                    type: custom
-                                    char_filter: []
-                                    filter: lowercase
-                                    # ...
-  ```
+``` yaml
+ibexa_elasticsearch:
+    # ...
+    index_templates:
+        default:
+            # ...
+            settings:
+                analysis:
+                    normalizer:
+                        lowercase_normalizer:
+                            type: custom
+                            char_filter: []
+                            filter: lowercase
+                            # ...
+```
 
 - `mappings` - Settings under this key define mapping for fields in the index.
 
diff --git a/docs/search/search_engines/solr_search_engine/install_solr.md b/docs/search/search_engines/solr_search_engine/install_solr.md
@@ -160,9 +160,9 @@ The Solr Search Engine Bundle can be configured in many ways.
 The config further below assumes you have parameters set up for Solr DSN and search engine *(however both are optional)*, for example:
 
 ``` yaml
-    env(SEARCH_ENGINE): solr
-    env(SOLR_DSN): 'http://localhost:8983/solr'
-    env(SOLR_CORE): collection1
+env(SEARCH_ENGINE): solr
+env(SOLR_DSN): 'http://localhost:8983/solr'
+env(SOLR_CORE): collection1
 ```
 
 ### Configure Solr version
diff --git a/docs/templating/templates/view_matcher_reference.md b/docs/templating/templates/view_matcher_reference.md
@@ -235,7 +235,7 @@ match:
 
 ``` yaml
 match:
-    '@Ibexa\Taxonomy\View\Matcher\TaxonomyEntryBased\Id': [1, 2, 3]'
+    '@Ibexa\Taxonomy\View\Matcher\TaxonomyEntryBased\Id': [1, 2, 3]
 ```
 
 ## Taxonomy entry identifier
@@ -264,4 +264,4 @@ match:
 ``` yaml
 match:
     '@Ibexa\Taxonomy\View\Matcher\TaxonomyEntryBased\Taxonomy': 'product_category'
-```
+```
diff --git a/docs/users/invitations.md b/docs/users/invitations.md
@@ -30,13 +30,13 @@ If the SiteAccess isn't set, it falls back to the default `site` value.
 For example, use the following [configuration](configuration.md#configuration-files):
 
 ```yaml
- ibexa:
-     system:
-         <scope>:
-             user_invitation:
-                 hash_expiration_time: P7D
-                 templates:
-                     mail: "@@App/invitation/mail.html.twig"
+ibexa:
+    system:
+        <scope>:
+            user_invitation:
+                hash_expiration_time: P7D
+                templates:
+                    mail: "@@App/invitation/mail.html.twig"
 ```
 
 Here, you can specify which template should be used for the invitation mail, and what should be the expiration time for the invitation link included in that mail.
diff --git a/docs/users/user_authentication.md b/docs/users/user_authentication.md
diff --git a/tests/yaml-validation-baseline.yaml b/tests/yaml-validation-baseline.yaml

-Original file line number
+Diff line change
                     to:
                         - dropped
 -// ...
 +# ...
 ibexa:
     repositories: