[Links] Converted links to 4.6 from main

docs/administration/back_office/back_office_configuration.md

@@ -8,7 +8,7 @@ description: Configure default upload locations, pagination limits, and more set
 ## Pagination limits
 
 Default pagination limits for different sections of the back office can be defined through respective settings in
-[`ezplatform_default_settings.yaml`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/config/ezplatform_default_settings.yaml#L7)
+[`ezplatform_default_settings.yaml`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/config/ezplatform_default_settings.yaml#L7)
 
 You can set the pagination limit for user settings under the `ibexa.system.<scope>.pagination_user` [configuration key](configuration.md#configuration-files):
 

docs/administration/back_office/back_office_elements/custom_components.md

@@ -18,22 +18,22 @@ App\Component\MyNewComponent:
 
 `group` indicates where the widget is displayed. The available groups are:
 
-- [`stylesheet-head`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/ui/layout.html.twig#L101)
-- [`script-head`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/ui/layout.html.twig#L102)
-- [`stylesheet-body`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/ui/layout.html.twig#L210)
-- [`script-body`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/ui/layout.html.twig#L211)
-- [`content-edit-form-before`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/user/edit.html.twig#L37)
-- [`content-edit-form-after`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/user/edit.html.twig#L47)
-- [`content-create-form-before`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/user/create.html.twig#L37)
-- [`content-create-form-after`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/user/create.html.twig#L45)
-- [`dashboard-blocks`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/ui/dashboard/dashboard.html.twig#L30)
-- [`dashboard-all-tab-groups`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/ui/dashboard/block/all.html.twig#L6)
-- [`dashboard-my-tab-groups`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/ui/dashboard/block/me.html.twig#L6)
-- [`content-type-tab-groups`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/content_type/index.html.twig#L37)
+- [`stylesheet-head`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/ui/layout.html.twig#L101)
+- [`script-head`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/ui/layout.html.twig#L102)
+- [`stylesheet-body`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/ui/layout.html.twig#L210)
+- [`script-body`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/ui/layout.html.twig#L211)
+- [`content-edit-form-before`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/user/edit.html.twig#L37)
+- [`content-edit-form-after`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/user/edit.html.twig#L47)
+- [`content-create-form-before`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/user/create.html.twig#L37)
+- [`content-create-form-after`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/user/create.html.twig#L45)
+- [`dashboard-blocks`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/ui/dashboard/dashboard.html.twig#L30)
+- [`dashboard-all-tab-groups`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/ui/dashboard/block/all.html.twig#L6)
+- [`dashboard-my-tab-groups`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/ui/dashboard/block/me.html.twig#L6)
+- [`content-type-tab-groups`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/content_type/index.html.twig#L37)
 - `calendar-widget-before`
-- [`login-form-before`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/account/login/index.html.twig#L7)
-- [`login-form-after`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/account/login/index.html.twig#L70)
-- [`global-search`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/views/themes/admin/ui/layout.html.twig#L129)
+- [`login-form-before`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/account/login/index.html.twig#L7)
+- [`login-form-after`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/account/login/index.html.twig#L70)
+- [`global-search`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/views/themes/admin/ui/layout.html.twig#L129)
 
 ## Base component classes
 

docs/administration/back_office/back_office_elements/extending_thumbnails.md

@@ -58,7 +58,7 @@ At this point you can go to the back office and check the results.
 !!! note "Thumbnail mechanism "
 
     This strategy overrides all generated thumbnails. You can specify a specific content type.
-    See the example [here](https://github.com/ibexa/user/blob/main/src/lib/Strategy/DefaultThumbnailStrategy.php)
+    See the example [here](https://github.com/ibexa/user/blob/4.6/src/lib/Strategy/DefaultThumbnailStrategy.php)
 
 
 ## Other fields as thumbnails

docs/administration/back_office/back_office_elements/importing_assets_from_bundle.md

@@ -32,7 +32,7 @@ To import CSS files only, use:
 
     After you add new files, run `php bin/console cache:clear`.
 
-    For a full example of importing asset configuration, see [`ibexa.config.js`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/encore/ibexa.config.js)
+    For a full example of importing asset configuration, see [`ibexa.config.js`](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/Resources/encore/ibexa.config.js)
 
 To edit existing configuration entries, either in the bundle's `Resources/encore/` folder, or in the `encore` folder in the root folder of your project, create an `ibexa.config.manager.js` file:
 
@@ -74,7 +74,7 @@ module.exports = (ibexaConfig, ibexaConfigManager) => {
 
     After you add new files, run `php bin/console cache:clear`.
 
-    For a full example of overriding configuration, see [`ibexa.config.manager.js`](https://github.com/ibexa/fieldtype-matrix/blob/main/src/bundle/Resources/encore/ibexa.config.manager.js).
+    For a full example of overriding configuration, see [`ibexa.config.manager.js`](https://github.com/ibexa/fieldtype-matrix/blob/4.6/src/bundle/Resources/encore/ibexa.config.manager.js).
 
 To add a new configuration under your own namespace and with its own dependencies, create an `ibexa.webpack.custom.config.js` file that you create either in the bundle's `Resources/encore/` folder, or in the `encore` folder in the root directory of your project, for example:
 

docs/administration/back_office/back_office_tabs/back_office_tabs.md

@@ -63,7 +63,7 @@ You can also influence tab display (for example, order tabs, remove, or modify t
 
 ## Tab groups
 
-You can create new tab groups by using the [`TabsComponent`](https://github.com/ibexa/admin-ui/blob/main/src/lib/Component/TabsComponent.php).
+You can create new tab groups by using the [`TabsComponent`](https://github.com/ibexa/admin-ui/blob/4.6/src/lib/Component/TabsComponent.php).
 
 To create a tab group, register it as a service:
 

docs/administration/back_office/subitems_list.md

@@ -94,7 +94,7 @@ Optionally, Sub-items module can take a following list of props:
 - **items** _{Array}_ - list of location's sub-items
 - **limit** _{Number}_ - items limit count
 - **offset** _{Number}_ - items limit offset
-- **labels** _{Object}_ - list of module labels, see [sub.items.module.js](https://github.com/ibexa/admin-ui/blob/main/src/bundle/ui-dev/src/modules/sub-items/sub.items.module.js) for details. Contains definitions for sub components:
+- **labels** _{Object}_ - list of module labels, see [sub.items.module.js](https://github.com/ibexa/admin-ui/blob/4.6/src/bundle/ui-dev/src/modules/sub-items/sub.items.module.js) for details. Contains definitions for sub components:
     - **subItems** _{Object}_ - list of sub-items module labels
     - **tableView** _{Object}_ - list of table view component labels
     - **tableViewItem** _{Object}_ - list of table item view component labels

docs/api/graphql/graphql_custom_ft.md

@@ -86,7 +86,7 @@ To do that, you need to replace `mapXXX` by the method it's in:
 
 It's required for every implemented method, so that other mappers are called for the other field types.
 
-The [`RelationFieldDefinitionMapper`](https://github.com/ibexa/graphql/blob/main/src/lib/Schema/Domain/Content/Mapper/FieldDefinition/RelationFieldDefinitionMapper.php) example:
+The [`RelationFieldDefinitionMapper`](https://github.com/ibexa/graphql/blob/4.6/src/lib/Schema/Domain/Content/Mapper/FieldDefinition/RelationFieldDefinitionMapper.php) example:
 
 ```php hl_lines="14"
 class RelationFieldDefinitionMapper extends DecoratingFieldDefinitionMapper implements FieldDefinitionMapper
@@ -172,4 +172,4 @@ The following variables are available in the resolver's expression:
 - `location` is the content item's resolved location. For more information, see [Querying Locations](graphql_queries.md#querying-locations)
 - `item` is the content together with its location `\Ibexa\GraphQL\Value\Item`
 
-`RelationFieldValueBuilder` or `SelectionFieldValueBuilder` can be used as examples.
+`RelationFieldValueBuilder` or `SelectionFieldValueBuilder` can be used as examples.

docs/api/php_api/php_api.md

@@ -71,7 +71,7 @@ To create and modify repository values, use data structures, such as [`ContentSe
 
 ### Value info objects
 
-Some complex value objects have an `Info` counterpart, for example [`ContentInfo`](https://github.com/ibexa/core/blob/main/src/contracts/Repository/Values/Content/ContentInfo.php) for [`Content`](https://github.com/ibexa/core/blob/main/src/contracts/Repository/Values/Content/Content.php).
+Some complex value objects have an `Info` counterpart, for example [`ContentInfo`](https://github.com/ibexa/core/blob/4.6/src/contracts/Repository/Values/Content/ContentInfo.php) for [`Content`](https://github.com/ibexa/core/blob/4.6/src/contracts/Repository/Values/Content/Content.php).
 These objects provide you with lower-level information.
 For instance, `ContentInfo` contains `currentVersionNo` or `remoteId`, while `Content` enables you to retrieve fields, content type, or previous versions.
 

docs/content_management/field_types/field_type_reference/richtextfield.md

@@ -116,7 +116,7 @@ The RichText format enriches [DocBook](https://docbook.org/) with the following
 !!! note "Unsupported DocBook elements"
 
     Some DocBook elements aren't supported by RichText.
-    Refer to [`ezpublish.rng`](https://github.com/ibexa/fieldtype-richtext/blob/main/src/bundle/Resources/richtext/schemas/docbook/ezpublish.rng#L137) for a full list.
+    Refer to [`ezpublish.rng`](https://github.com/ibexa/fieldtype-richtext/blob/4.6/src/bundle/Resources/richtext/schemas/docbook/ezpublish.rng#L137) for a full list.
 
 ### Online Editor elements
 

docs/content_management/field_types/field_type_search.md

@@ -46,7 +46,7 @@ Default field is typically used by the [`Field` Sort Clause](field_sort_clause.m
 ## Register `Indexable` implementations
 
 Implement `Ibexa\Contracts\Core\FieldType\Indexable` as an extra service and register this Service using the `ibexa.field_type.indexable` tag.
-Example from [`indexable_fieldtypes.yaml`](https://github.com/ibexa/core/blob/main/src/lib/Resources/settings/indexable_fieldtypes.yml):
+Example from [`indexable_fieldtypes.yaml`](https://github.com/ibexa/core/blob/4.6/src/lib/Resources/settings/indexable_fieldtypes.yml):
 
 ``` yaml
 Ibexa\Core\FieldType\Keyword\SearchField:

docs/content_management/field_types/field_type_storage.md

@@ -65,7 +65,7 @@ Just like a Type, a Legacy Converter needs to be registered and tagged in the [s
 
 #### Registering a converter
 
-The registration of a `Converter` currently works through the `$config` parameter of [`Ibexa\Core\Persistence\Legacy\Handler`](https://github.com/ibexa/core/blob/main/src/lib/Persistence/Legacy/Handler.php).
+The registration of a `Converter` currently works through the `$config` parameter of [`Ibexa\Core\Persistence\Legacy\Handler`](https://github.com/ibexa/core/blob/4.6/src/lib/Persistence/Legacy/Handler.php).
 
 Those converters also need to be correctly exposed as services and tagged with `ibexa.field_type.storage.legacy.converter`:
 
@@ -84,7 +84,7 @@ The tag has the following attribute:
 
 !!! tip
 
-    Converter configuration for built-in field types is located in [`ibexa/core/src/lib/Resources/settings/fieldtype_external_storages.yml`](https://github.com/ibexa/core/blob/main/src/lib/Resources/settings/fieldtype_external_storages.yml).
+    Converter configuration for built-in field types is located in [`ibexa/core/src/lib/Resources/settings/fieldtype_external_storages.yml`](https://github.com/ibexa/core/blob/4.6/src/lib/Resources/settings/fieldtype_external_storages.yml).
 
 ## Storing data externally
 
@@ -154,7 +154,7 @@ services:
 
 The configuration requires providing the `ibexa.field_type.storage.external.handler` tag, with the `alias` attribute being the *fieldTypeIdentifier*. You also have to inject the gateway in `arguments`, [see Gateway-based storage](#gateway-based-storage).
 
-External storage configuration for basic field types is located in [`ibexa/core/src/lib/Resources/settings/fieldtype_external_storages.yml`](https://github.com/ibexa/core/blob/main/src/lib/Resources/settings/fieldtype_external_storages.yml).
+External storage configuration for basic field types is located in [`ibexa/core/src/lib/Resources/settings/fieldtype_external_storages.yml`](https://github.com/ibexa/core/blob/4.6/src/lib/Resources/settings/fieldtype_external_storages.yml).
 
 Using gateway-based storage requires another service implementing `Ibexa\Core\FieldType\StorageGateway` to be injected into the [external storage handler](#storing-data-externally)).
 
@@ -176,7 +176,7 @@ In this case it's recommended to either create base implementation which each ga
 
 !!! tip
 
-    Gateway configuration for built-in field types is located in [`core/src/lib/Resources/settings/storage_engines/`](https://github.com/ibexa/core/tree/main/src/lib/Resources/settings/storage_engines).
+    Gateway configuration for built-in field types is located in [`core/src/lib/Resources/settings/storage_engines/`](https://github.com/ibexa/core/tree/4.6/src/lib/Resources/settings/storage_engines).
 
 ## Storing field type settings externally
 

docs/content_management/field_types/field_types.md

@@ -20,7 +20,7 @@ Field types are responsible for:
 To do so, you need to create a custom field type.
 
 A custom field type must implement the **FieldType Service Provider Interfaces**
-available in the [`Ibexa\Core\FieldType`](https://github.com/ibexa/core/tree/main/src/lib/FieldType) namespace.
+available in the [`Ibexa\Core\FieldType`](https://github.com/ibexa/core/tree/4.6/src/lib/FieldType) namespace.
 
 !!! note "Registration"
 

docs/content_management/field_types/form_and_template.md

@@ -134,7 +134,7 @@ By convention, your block must be named `<fieldTypeIdentifier>_field`.
 
 !!! tip
 
-    Template blocks for built-in field types are available in [`Core/Resources/views/content_fields.html.twig`](https://github.com/ibexa/core/blob/main/src/bundle/Core/Resources/views/content_fields.html.twig).
+    Template blocks for built-in field types are available in [`Core/Resources/views/content_fields.html.twig`](https://github.com/ibexa/core/blob/4.6/src/bundle/Core/Resources/views/content_fields.html.twig).
 
     This template is also exposed as a part of Standard Design, so you can override it with the [design engine](design_engine.md).
     To do so, place the template `themes/standard/content_fields.html.twig` in your `Resources/views` (assuming `ibexa_standard_design.override_kernel_templates` is set to true).
@@ -156,7 +156,7 @@ The block can receive the following variables:
 
 For easier field type template development you can take advantage of all defined blocks by using the [`block()` function](https://twig.symfony.com/doc/3.x/functions/block.html).
 
-You can for example use `simple_block_field`, `simple_inline_field` or `field_attributes` blocks provided in [`content_fields.html.twig`](https://github.com/ibexa/core/blob/main/src/bundle/Core/Resources/views/content_fields.html.twig#L486).
+You can for example use `simple_block_field`, `simple_inline_field` or `field_attributes` blocks provided in [`content_fields.html.twig`](https://github.com/ibexa/core/blob/4.6/src/bundle/Core/Resources/views/content_fields.html.twig#L486).
 
 !!! caution
 

docs/content_management/field_types/type_and_value.md

@@ -151,7 +151,7 @@ This ensures that the initialization steps shared by all field types are execute
 
 !!! tip
 
-    The configuration of built-in field types is located in [`core/src/lib/Resources/settings/fieldtypes.yml`](https://github.com/ibexa/core/blob/main/src/lib/Resources/settings/fieldtypes.yml).
+    The configuration of built-in field types is located in [`core/src/lib/Resources/settings/fieldtypes.yml`](https://github.com/ibexa/core/blob/4.6/src/lib/Resources/settings/fieldtypes.yml).
 
 ### Indexing
 

docs/content_management/file_management/file_management.md

@@ -113,7 +113,7 @@ oneup_flysystem:
                 service: ibexa.io.nfs.adapter.site_access_aware
 ```
 
-To learn how to configure other adapters, see the [bundle's online documentation](https://github.com/1up-lab/OneupFlysystemBundle/blob/main/doc/index.md#step3-configure-your-filesystems).
+To learn how to configure other adapters, see the [bundle's online documentation](https://github.com/1up-lab/OneupFlysystemBundle/blob/4.x/doc/index.md#step3-configure-your-filesystems).
 
 !!! note
 

docs/content_management/images/images.md

@@ -126,7 +126,7 @@ In [[= product_name =]], there are two implementations of the `PlaceholderProvid
 
 ### GenericProvider
 
-The [`GenericProvider`](https://github.com/ibexa/core/blob/main/src/bundle/Core/Imagine/PlaceholderProvider.php) package generates placeholders with basic information about the original image (see [example 1](#configuration-examples)).
+The [`GenericProvider`](https://github.com/ibexa/core/blob/4.6/src/bundle/Core/Imagine/PlaceholderProvider.php) package generates placeholders with basic information about the original image (see [example 1](#configuration-examples)).
 
 ![Placeholder image GenericProvider](placeholder_info.jpg "Example of a generic placeholder image")
 
@@ -143,7 +143,7 @@ The [`GenericProvider`](https://github.com/ibexa/core/blob/main/src/bundle/Core/
 
 ### RemoteProvider
 
-With the [`RemoteProvider`](https://github.com/ibexa/core/blob/main/src/bundle/Core/Imagine/PlaceholderProvider/RemoteProvider.php) you can download placeholders from:
+With the [`RemoteProvider`](https://github.com/ibexa/core/blob/4.6/src/bundle/Core/Imagine/PlaceholderProvider/RemoteProvider.php) you can download placeholders from:
 
  - remote sources, for example, <http://placekitten.com> (see [example 2](#configuration-examples))
  - live version of a site (see [example 3](#configuration-examples))

docs/content_management/rich_text/extend_online_editor.md

@@ -379,7 +379,7 @@ You can modify the order and visibility of buttons that are available in the Onl
 
 For each button you can set `priority`, which defines the order of buttons in the toolbar.
 
-For a full list of standard buttons, see the RichText module's [configuration file](https://github.com/ibexa/fieldtype-richtext/blob/main/src/bundle/Resources/config/prepend/ezpublish.yaml)
+For a full list of standard buttons, see the RichText module's [configuration file](https://github.com/ibexa/fieldtype-richtext/blob/4.6/src/bundle/Resources/config/prepend/ezpublish.yaml)
 
 ## Add CKEditor plugins