From b446b901851f15be1f714c8ad153df4cebbdcb61 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Noco=C5=84?= Date: Mon, 27 Apr 2026 16:33:41 +0200 Subject: [PATCH 1/2] Avoid redirects from master to 5.0 --- docs/release_notes/ibexa_dxp_v4.3.md | 10 +++--- docs/release_notes/ibexa_dxp_v4.6.md | 34 +++++++++---------- .../template/components/source.html.twig | 2 +- 3 files changed, 23 insertions(+), 23 deletions(-) diff --git a/docs/release_notes/ibexa_dxp_v4.3.md b/docs/release_notes/ibexa_dxp_v4.3.md index 01341b1f3c..cd21993fec 100644 --- a/docs/release_notes/ibexa_dxp_v4.3.md +++ b/docs/release_notes/ibexa_dxp_v4.3.md @@ -55,8 +55,8 @@ For more information, see [Work with SEO](https://doc.ibexa.co/projects/userguid When querying for products, you can now use one of two price-related Sort Clauses: -- [`BasePrice` Sort Clause](https://doc.ibexa.co/en/master/search/sort_clause_reference/baseprice_sort_clause/) sorts results by the products' base prices -- [`CustomPrice` Sort Clause](https://doc.ibexa.co/en/master/search/sort_clause_reference/customprice_sort_clause/) enables sorting by the custom price configured for the provided customer group. +- [`BasePrice` Sort Clause](https://doc.ibexa.co/en/5.0/search/sort_clause_reference/baseprice_sort_clause/) sorts results by the products' base prices +- [`CustomPrice` Sort Clause](https://doc.ibexa.co/en/5.0/search/sort_clause_reference/customprice_sort_clause/) enables sorting by the custom price configured for the provided customer group. #### Usability improvements @@ -73,7 +73,7 @@ From product's **Completeness** tab you can now jump directly to editing the pro #### Catalog filters -In catalogs, you can now [configure default filters](https://doc.ibexa.co/en/master/pim/pim_configuration/#catalog-filters) that are always added to a catalog, define filter order, and group custom filters. +In catalogs, you can now [configure default filters](https://doc.ibexa.co/en/5.0/pim/pim_configuration/#catalog-filters) that are always added to a catalog, define filter order, and group custom filters. Built-in filters are also divided into groups now for easier browsing. Filtering by the Color attribute is now possible. @@ -115,8 +115,8 @@ The `TaxonomyEntryId` Search Criterion isn't available in Legacy search Engine. ### Other improvements -- You can now [customize Elasticsearch index structure](https://doc.ibexa.co/en/master/search/extensibility/customize_elasticsearch_index_structure/) to manage how documents in the index are grouped. -- A new [`ibexa_seo_is_empty()` Twig function](https://doc.ibexa.co/en/master/templating/twig_function_reference/content_twig_functions/#ibexa_content_name) checks whether SEO data is available for a content item. +- You can now [customize Elasticsearch index structure](https://doc.ibexa.co/en/5.0/search/extensibility/customize_elasticsearch_index_structure/) to manage how documents in the index are grouped. +- A new [`ibexa_seo_is_empty()` Twig function](https://doc.ibexa.co/en/5.0/templating/twig_function_reference/content_twig_functions/#ibexa_content_name) checks whether SEO data is available for a content item. ## Full changelog diff --git a/docs/release_notes/ibexa_dxp_v4.6.md b/docs/release_notes/ibexa_dxp_v4.6.md index 80854abd39..46c05487bc 100644 --- a/docs/release_notes/ibexa_dxp_v4.6.md +++ b/docs/release_notes/ibexa_dxp_v4.6.md @@ -1347,7 +1347,7 @@ on the dashboard within Recent activity block, or on the user profile. ![Recent activity log](img/4.6_activity_list.png "Recent activity log") -For more information, see feature's [User Documentation](https://doc.ibexa.co/projects/userguide/en/master/recent_activity/recent_activity/), and [Developer Documentation](https://doc.ibexa.co/en/master/administration/recent_activity/recent_activity/). +For more information, see feature's [User Documentation](https://doc.ibexa.co/projects/userguide/en/master/recent_activity/recent_activity/), and [Developer Documentation](https://doc.ibexa.co/en/5.0/administration/recent_activity/recent_activity/). ##### Back office search @@ -1363,7 +1363,7 @@ In the search result page, a spellcheck suggestion can be made. For example, if the searched text is "Comany", the result page may ask "Did you mean company?", which is clickable to relaunch the search with this word. -For more information, see [User Documentation](https://doc.ibexa.co/projects/userguide/en/master/search/search_for_content/), and how to [customize autocompletion suggestions](https://doc.ibexa.co/en/master/administration/back_office/customize_search_suggestion/). +For more information, see [User Documentation](https://doc.ibexa.co/projects/userguide/en/master/search/search_for_content/), and how to [customize autocompletion suggestions](https://doc.ibexa.co/en/5.0/administration/back_office/customize_search_suggestion/). ###### Filtering and sorting @@ -1371,7 +1371,7 @@ The search result page can be sorted in other orders than relevance. Name, publi Filters can be applied to the search page to narrow down the results. -For more information, see [User Documentation](https://doc.ibexa.co/projects/userguide/en/master/search/search_for_content/#filtered-search), and how to [customize search sorting](https://doc.ibexa.co/en/master/administration/back_office/customize_search_sorting/). +For more information, see [User Documentation](https://doc.ibexa.co/projects/userguide/en/master/search/search_for_content/#filtered-search), and how to [customize search sorting](https://doc.ibexa.co/en/5.0/administration/back_office/customize_search_sorting/). ##### New and updated content type icons @@ -1439,7 +1439,7 @@ For more information, see [Create product types](https://doc.ibexa.co/projects/u VAT rates configuration has been extended to accept additional flags under the `extras` key. Developers can use them, for example, to pass additional information to the UI, or define special exclusion rules. -For more information, see [VAT rates](https://doc.ibexa.co/en/master/pim/pim_configuration/#vat-rates). +For more information, see [VAT rates](https://doc.ibexa.co/en/5.0/pim/pim_configuration/#vat-rates). ##### Ability to search through products in a catalog @@ -1447,8 +1447,8 @@ When you're reviewing catalog details, on the **Products** tab, you can now see ##### New Twig functions -The `ibexa_is_pim_local` Twig helper has been introduced, which can be used in templates to [check whether product data comes from a local or remote data source](https://doc.ibexa.co/en/master/templating/twig_function_reference/storefront_twig_functions/#ibexa_is_pim_local), and adjust their behavior accordingly. -Also, several new Twig functions have been implemented that help [get product availability information](https://doc.ibexa.co/en/master/templating/twig_function_reference/product_twig_functions/#ibexa_has_product_availability). +The `ibexa_is_pim_local` Twig helper has been introduced, which can be used in templates to [check whether product data comes from a local or remote data source](https://doc.ibexa.co/en/5.0/templating/twig_function_reference/storefront_twig_functions/#ibexa_is_pim_local), and adjust their behavior accordingly. +Also, several new Twig functions have been implemented that help [get product availability information](https://doc.ibexa.co/en/5.0/templating/twig_function_reference/product_twig_functions/#ibexa_has_product_availability). ##### New and modified query types @@ -1460,7 +1460,7 @@ With `IsVirtual` criterion that searches for virtual or physical products, produ ##### Product migration -[Product variants](https://doc.ibexa.co/en/master/content_management/data_migration/importing_data/#product-variants) and [product assets](https://doc.ibexa.co/en/master/content_management/data_migration/importing_data/#product-assets) can now be created through [data migration](https://doc.ibexa.co/en/master/content_management/data_migration/data_migration/). +[Product variants](https://doc.ibexa.co/en/5.0/content_management/data_migration/importing_data/#product-variants) and [product assets](https://doc.ibexa.co/en/5.0/content_management/data_migration/importing_data/#product-assets) can now be created through [data migration](https://doc.ibexa.co/en/5.0/content_management/data_migration/data_migration/). #### New features and improvements in Commerce [[% include 'snippets/commerce_badge.md' %]] @@ -1471,7 +1471,7 @@ directly from their order history with a single click, eliminating the need for The system streamlines the process by recreating the cart, retrieving shipping information, and pre-filling payment details from past orders. This feature is exclusively accessible to logged-in users, ensuring a secure and personalized shopping experience. -For more information, see [reorder documentation](https://doc.ibexa.co/en/master/commerce/checkout/reorder/). +For more information, see [reorder documentation](https://doc.ibexa.co/en/5.0/commerce/checkout/reorder/). ##### Orders block @@ -1491,13 +1491,13 @@ Quick order form is available to both registered and guest users. ![Quick order](img/4.6_quick_order.png "Quick order") -For more information, see [Quick order documentation](https://doc.ibexa.co/en/master/commerce/cart/quick_order/). +For more information, see [Quick order documentation](https://doc.ibexa.co/en/5.0/commerce/cart/quick_order/). ##### Cancel order This version allows you to customize order cancellations by defining a specific order status and related transition. -For more information, see [Define cancel order](https://doc.ibexa.co/en/master/commerce/order_management/configure_order_management/#define-cancel-order). +For more information, see [Define cancel order](https://doc.ibexa.co/en/5.0/commerce/order_management/configure_order_management/#define-cancel-order). ##### Integrate with payment gateways @@ -1525,13 +1525,13 @@ You can create a PHP definition of the new strategy that allows for workflow man Defining strategy allows to add conditional steps for workflow if needed. When a conditional step is added, the checkout process uses the specified workflow and proceeds to the defined step. -For more information, see [Create custom strategy](https://doc.ibexa.co/en/master/commerce/checkout/customize_checkout/#create-custom-strategy). +For more information, see [Create custom strategy](https://doc.ibexa.co/en/5.0/commerce/checkout/customize_checkout/#create-custom-strategy). ##### Manage multiple checkout workflows When working with multiple checkout workflows, you can now specify the desired workflow by passing its name as an argument to the checkout initiation button or link. -For more information, see [Manage multiple workflows](https://doc.ibexa.co/en/master/commerce/checkout/customize_checkout/#manage-multiple-workflows). +For more information, see [Manage multiple workflows](https://doc.ibexa.co/en/5.0/commerce/checkout/customize_checkout/#manage-multiple-workflows). ##### Adding context data to cart @@ -1541,7 +1541,7 @@ enabling you to associate additional information with your cart and its contents By leveraging context data, such as promo codes or custom texts, you can tailor the shopping experience for your customers and enhance the capabilities of your application. -For more information, see [Adding context data](https://doc.ibexa.co/en/master/commerce/cart/cart_api/#adding-context-data). +For more information, see [Adding context data](https://doc.ibexa.co/en/5.0/commerce/cart/cart_api/#adding-context-data). #### New features and improvements in Personalization @@ -1564,7 +1564,7 @@ For more information, see [Email triggers](https://doc.ibexa.co/projects/usergui With this feature, you get an option to combine several attribute types when computing recommendations. As a result, users can be presented with recommendations from an intersection of submodel results. -For more information, see [Submodel parameters](https://doc.ibexa.co/en/master/personalization/api_reference/recommendation_api/#submodel-parameters) and [Submodels](https://doc.ibexa.co/projects/userguide/en/latest/personalization/recommendation_models/#submodels). +For more information, see [Submodel parameters](https://doc.ibexa.co/en/5.0/personalization/api_reference/recommendation_api/#submodel-parameters) and [Submodels](https://doc.ibexa.co/projects/userguide/en/latest/personalization/recommendation_models/#submodels). ##### New scenario filter @@ -1664,20 +1664,20 @@ New [[= product_name_connect =]] scenario block retrieves and displays data from Scenario block is a regular Page block and can be configured on field definition level as any other block. You also need to configure scenario block in the Page Builder. To do it, you need to provide name for the block, enter webhook link for the [[= product_name_connect =]] webhook and select the template to be used to present the webhook. -For more information, see [[[= product_name_connect =]] scenario block](https://doc.ibexa.co/en/master/content_management/pages/ibexa_connect_scenario_block/). +For more information, see [[[= product_name_connect =]] scenario block](https://doc.ibexa.co/en/5.0/content_management/pages/ibexa_connect_scenario_block/). #### DDEV [[[= product_name =]] can officially be run on DDEV](https://docs.ddev.com/en/stable/users/quickstart/#ibexa-dxp). -For more information, see the [DDEV guide](https://doc.ibexa.co/en/master/getting_started/install_with_ddev/), which offers a step-by-step walkthrough for installing [[= product_name =]]. +For more information, see the [DDEV guide](https://doc.ibexa.co/en/5.0/getting_started/install_with_ddev/), which offers a step-by-step walkthrough for installing [[= product_name =]]. #### Customer Data Platform (CDP) In this release, the CDP configuration allows you to automate the process of exporting data. Users can now export not only Content, but also Users and Products data. -For more information, see [CDP Activation](https://doc.ibexa.co/en/master/cdp/cdp_activation/cdp_activation/). +For more information, see [CDP Activation](https://doc.ibexa.co/en/5.0/cdp/cdp_activation/cdp_activation/). ### Developer experience diff --git a/tools/api_refs/.phpdoc/template/components/source.html.twig b/tools/api_refs/.phpdoc/template/components/source.html.twig index d4f5238e3e..1fa22c9048 100644 --- a/tools/api_refs/.phpdoc/template/components/source.html.twig +++ b/tools/api_refs/.phpdoc/template/components/source.html.twig @@ -2,7 +2,7 @@ {% block content %}
- {% set href = 'https://github.com/ibexa/documentation-developer/tree/master/docs/api/php_api' %} + {% set href = 'https://github.com/ibexa/documentation-developer/tree/5.0/docs/api/php_api' %} {% if node.file is not null %} {% set path = node.file.path|split('/', 4) %} {% set package = path|slice(1, 2)|join('/') %} From 71c16f3ad02c6001546b17ade9f0033f6f8bcaa7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Noco=C5=84?= Date: Tue, 5 May 2026 11:53:24 +0200 Subject: [PATCH 2/2] Changed link from main/master to 5.0 --- .../back_office/back_office_configuration.md | 2 +- .../back_office_elements/extending_thumbnails.md | 2 +- .../importing_assets_from_bundle.md | 4 ++-- .../back_office_tabs/back_office_tabs.md | 2 +- docs/administration/back_office/subitems_list.md | 2 +- .../administration/project_organization/bundles.md | 2 +- docs/api/graphql/graphql_custom_ft.md | 4 ++-- docs/api/php_api/php_api.md | 2 +- .../field_type_reference/richtextfield.md | 2 +- .../field_types/field_type_search.md | 2 +- .../field_types/field_type_storage.md | 8 ++++---- docs/content_management/field_types/field_types.md | 2 +- .../field_types/form_and_template.md | 4 ++-- .../field_types/type_and_value.md | 2 +- docs/content_management/images/images.md | 6 +++--- .../rich_text/extend_online_editor.md | 2 +- .../url_management/url_management.md | 2 +- docs/getting_started/install_ibexa_dxp.md | 2 +- docs/getting_started/install_with_ddev.md | 2 +- .../cache/http_cache/reverse_proxy.md | 4 ++-- .../cache/persistence_cache.md | 2 +- docs/infrastructure_and_maintenance/performance.md | 2 +- .../security/development_security.md | 2 +- docs/multisite/languages/languages.md | 2 +- docs/product_catalog/product_catalog_guide.md | 2 +- .../criteria_reference/contentname_criterion.md | 2 +- docs/search/search_api.md | 14 +++++++------- docs/search/search_criteria_and_sort_clauses.md | 2 +- docs/templating/components.md | 12 ++++++------ .../layout/add_forgot_password_option.md | 4 ++-- .../layout/customize_storefront_layout.md | 2 +- .../built-in_query_types.md | 2 +- 32 files changed, 53 insertions(+), 53 deletions(-) diff --git a/docs/administration/back_office/back_office_configuration.md b/docs/administration/back_office/back_office_configuration.md index b033144554..288ab7b837 100644 --- a/docs/administration/back_office/back_office_configuration.md +++ b/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/5.0/src/bundle/Resources/config/ezplatform_default_settings.yaml#L7). You can set the pagination limit for user settings under the `ibexa.system..pagination_user` [configuration key](configuration.md#configuration-files): diff --git a/docs/administration/back_office/back_office_elements/extending_thumbnails.md b/docs/administration/back_office/back_office_elements/extending_thumbnails.md index 0c3d9ae0cd..48ace7411f 100644 --- a/docs/administration/back_office/back_office_elements/extending_thumbnails.md +++ b/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/5.0/src/lib/Strategy/DefaultThumbnailStrategy.php) ## Other fields as thumbnails diff --git a/docs/administration/back_office/back_office_elements/importing_assets_from_bundle.md b/docs/administration/back_office/back_office_elements/importing_assets_from_bundle.md index fa5efb5cad..992049a038 100644 --- a/docs/administration/back_office/back_office_elements/importing_assets_from_bundle.md +++ b/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/5.0/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/5.0/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: diff --git a/docs/administration/back_office/back_office_tabs/back_office_tabs.md b/docs/administration/back_office/back_office_tabs/back_office_tabs.md index 589824d43b..8cf1488bba 100644 --- a/docs/administration/back_office/back_office_tabs/back_office_tabs.md +++ b/docs/administration/back_office/back_office_tabs/back_office_tabs.md @@ -64,7 +64,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/5.0/src/lib/Component/TabsComponent.php). To create a tab group, register it as a service: diff --git a/docs/administration/back_office/subitems_list.md b/docs/administration/back_office/subitems_list.md index 43bdfc7cbe..675a4a7015 100644 --- a/docs/administration/back_office/subitems_list.md +++ b/docs/administration/back_office/subitems_list.md @@ -145,7 +145,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/5.0/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 diff --git a/docs/administration/project_organization/bundles.md b/docs/administration/project_organization/bundles.md index 25a1e7ad06..8ff72dde96 100644 --- a/docs/administration/project_organization/bundles.md +++ b/docs/administration/project_organization/bundles.md @@ -11,7 +11,7 @@ You can also reuse the bundles you create in other projects or share them with t Many [[= product_name =]] functionalities are provided through separate bundles included in the installation. You can see the bundles that are automatically installed with [[= product_name =]] in the respective `composer.json` files. -For example, for [[= product_name_headless =]], see the [JSON file on GitHub](https://github.com/ibexa/headless/blob/master/composer.json). +For example, for [[= product_name_headless =]], see the [JSON file on GitHub](https://github.com/ibexa/headless/blob/5.0/composer.json). ## Working with bundles diff --git a/docs/api/graphql/graphql_custom_ft.md b/docs/api/graphql/graphql_custom_ft.md index 002ceb7420..3ef8a1f955 100644 --- a/docs/api/graphql/graphql_custom_ft.md +++ b/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/5.0/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. \ No newline at end of file +`RelationFieldValueBuilder` or `SelectionFieldValueBuilder` can be used as examples. diff --git a/docs/api/php_api/php_api.md b/docs/api/php_api/php_api.md index e9d3b7fd94..fe7d8b0c16 100644 --- a/docs/api/php_api/php_api.md +++ b/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/5.0/src/contracts/Repository/Values/Content/ContentInfo.php) for [`Content`](https://github.com/ibexa/core/blob/5.0/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. diff --git a/docs/content_management/field_types/field_type_reference/richtextfield.md b/docs/content_management/field_types/field_type_reference/richtextfield.md index 0f6605a0ba..1729dbffd2 100644 --- a/docs/content_management/field_types/field_type_reference/richtextfield.md +++ b/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/5.0/src/bundle/Resources/richtext/schemas/docbook/ezpublish.rng#L137) for a full list. ### Online Editor elements diff --git a/docs/content_management/field_types/field_type_search.md b/docs/content_management/field_types/field_type_search.md index 55f8559d12..807726cb40 100644 --- a/docs/content_management/field_types/field_type_search.md +++ b/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/5.0/src/lib/Resources/settings/indexable_fieldtypes.yml): ``` yaml Ibexa\Core\FieldType\Keyword\SearchField: diff --git a/docs/content_management/field_types/field_type_storage.md b/docs/content_management/field_types/field_type_storage.md index ed3ab221c3..34999a91ce 100644 --- a/docs/content_management/field_types/field_type_storage.md +++ b/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/5.0/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/5.0/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/5.0/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/5.0/src/lib/Resources/settings/storage_engines). ## Storing field type settings externally diff --git a/docs/content_management/field_types/field_types.md b/docs/content_management/field_types/field_types.md index e7d00ba817..9d689e5152 100644 --- a/docs/content_management/field_types/field_types.md +++ b/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/5.0/src/lib/FieldType) namespace. !!! note "Registration" diff --git a/docs/content_management/field_types/form_and_template.md b/docs/content_management/field_types/form_and_template.md index 471cdf36c9..fed81cc459 100644 --- a/docs/content_management/field_types/form_and_template.md +++ b/docs/content_management/field_types/form_and_template.md @@ -134,7 +134,7 @@ By convention, your block must be named `_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/5.0/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/5.0/src/bundle/Core/Resources/views/content_fields.html.twig#L486). !!! caution diff --git a/docs/content_management/field_types/type_and_value.md b/docs/content_management/field_types/type_and_value.md index 1b03733f65..fb55abd5b2 100644 --- a/docs/content_management/field_types/type_and_value.md +++ b/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/5.0/src/lib/Resources/settings/fieldtypes.yml). ### Indexing diff --git a/docs/content_management/images/images.md b/docs/content_management/images/images.md index 3926ebd0fa..fc58207a04 100644 --- a/docs/content_management/images/images.md +++ b/docs/content_management/images/images.md @@ -113,7 +113,7 @@ You can also pass two additional parameters: With a placeholder generator you can download or generate placeholder images for any missing image. It proves useful when you're working on an existing database and are unable to download uploaded images to your local development environment, due to, for example, a large size of files. -If the original image cannot be resolved, the `PlaceholderAliasGenerator::getVariation` method generates a placeholder by delegating it to the implementation of the [PlaceholderProvider](https://github.com/ibexa/core/blob/main/src/bundle/Core/Imagine/PlaceholderProvider.php) interface, and saves it under the original path. +If the original image cannot be resolved, the `PlaceholderAliasGenerator::getVariation` method generates a placeholder by delegating it to the implementation of the [PlaceholderProvider](https://github.com/ibexa/core/blob/5.0/src/bundle/Core/Imagine/PlaceholderProvider.php) interface, and saves it under the original path. In [[= product_name =]], there are two implementations of the `PlaceholderProvider` interface: @@ -122,7 +122,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/5.0/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") @@ -139,7 +139,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/5.0/src/bundle/Core/Imagine/PlaceholderProvider/RemoteProvider.php) you can download placeholders from: - remote sources, for example, (see [example 2](#configuration-examples)) - live version of a site (see [example 3](#configuration-examples)) diff --git a/docs/content_management/rich_text/extend_online_editor.md b/docs/content_management/rich_text/extend_online_editor.md index 67ae720957..a53063fc87 100644 --- a/docs/content_management/rich_text/extend_online_editor.md +++ b/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/5.0/src/bundle/Resources/config/prepend/ezpublish.yaml) ## Add CKEditor plugins diff --git a/docs/content_management/url_management/url_management.md b/docs/content_management/url_management/url_management.md index a249b83d0e..20af85356b 100644 --- a/docs/content_management/url_management/url_management.md +++ b/docs/content_management/url_management/url_management.md @@ -181,7 +181,7 @@ ibexa: | `separator` | Decides what separator is used. There are three types of separator available: dash, underscore and space. | | `transformation_groups` | Contains the available patterns for URL generation. | -A transformation group consists of an array of commands (see [all available commands](https://github.com/ibexa/core/tree/main/src/lib/Resources/slug_converter/transformations)) and a [`cleanupText`](https://github.com/ibexa/core/blob/main/src/lib/Persistence/Legacy/Content/UrlAlias/SlugConverter.php#L286). +A transformation group consists of an array of commands (see [all available commands](https://github.com/ibexa/core/tree/5.0/src/lib/Resources/slug_converter/transformations)) and a [`cleanupText`](https://github.com/ibexa/core/blob/5.0/src/lib/Persistence/Legacy/Content/UrlAlias/SlugConverter.php#L286). You can make use of pre-defined transformation groups. You can also add your own, with your own set of commands. diff --git a/docs/getting_started/install_ibexa_dxp.md b/docs/getting_started/install_ibexa_dxp.md index e8205787a7..8e6d13b984 100644 --- a/docs/getting_started/install_ibexa_dxp.md +++ b/docs/getting_started/install_ibexa_dxp.md @@ -393,7 +393,7 @@ Prepare a [virtual host configuration](https://en.wikipedia.org/wiki/Virtual_hos === "nginx" - You can use [this example vhost file](https://raw.githubusercontent.com/ibexa/post-install/main/resources/templates/nginx/vhost.template) and modify it to fit your project. You also need the `ibexa_params.d` files that should reside in a subdirectory below where the main file is, [as is shown here](https://github.com/ibexa/post-install/tree/main/resources/templates/nginx). + You can use [this example vhost file](https://raw.githubusercontent.com/ibexa/post-install/main/resources/templates/nginx/vhost.template) and modify it to fit your project. You also need the `ibexa_params.d` files that should reside in a subdirectory below where the main file is, [as is shown here](https://github.com/ibexa/post-install/tree/5.0/resources/templates/nginx). Specify `//public` as the `root`, or ensure `BASEDIR` is set in the environment. diff --git a/docs/getting_started/install_with_ddev.md b/docs/getting_started/install_with_ddev.md index 6a890c54d9..b5c05a3ddc 100644 --- a/docs/getting_started/install_with_ddev.md +++ b/docs/getting_started/install_with_ddev.md @@ -344,7 +344,7 @@ ddev restart #### Scripted procedure -Generate the virtual host with [`vhost.sh`](https://github.com/ibexa/docker/blob/main/scripts/vhost.sh): +Generate the virtual host with [`vhost.sh`](https://github.com/ibexa/docker/blob/5.0/scripts/vhost.sh): ```bash curl -O https://raw.githubusercontent.com/ibexa/docker/main/scripts/vhost.sh diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md b/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md index f309604195..8a743eb240 100644 --- a/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md +++ b/docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md @@ -158,7 +158,7 @@ If you want to use Basic Auth with Fastly on [[= product_name_cloud =]], please !!! note "Invalidating Varnish cache by using tokens" - In setups where the Varnish server IP can change (for example, on [[= product_name_cloud =]]), you can use token-based cache invalidation through [`ibexa_purge_acl`](https://github.com/ibexa/http-cache/blob/main/docs/varnish/vcl/varnish5.vcl#L174). + In setups where the Varnish server IP can change (for example, on [[= product_name_cloud =]]), you can use token-based cache invalidation through [`ibexa_purge_acl`](https://github.com/ibexa/http-cache/blob/5.0/docs/varnish/vcl/varnish5.vcl#L174). In such situation, use strong, secure hash and make sure to keep the token secret. @@ -195,7 +195,7 @@ If you created a custom Captcha block for your site by overriding the default fi data-field-id="{{ field.id }}" ``` -As a result, your file should be similar to [this example](https://github.com/ibexa/form-builder/blob/main/src/bundle/Resources/views/themes/standard/fields/captcha.html.twig). +As a result, your file should be similar to [this example](https://github.com/ibexa/form-builder/blob/5.0/src/bundle/Resources/views/themes/standard/fields/captcha.html.twig). For more information about configuring Captcha fields, see [Captcha field](work_with_forms.md#captcha-field). diff --git a/docs/infrastructure_and_maintenance/cache/persistence_cache.md b/docs/infrastructure_and_maintenance/cache/persistence_cache.md index ece1462733..4b34d52a2d 100644 --- a/docs/infrastructure_and_maintenance/cache/persistence_cache.md +++ b/docs/infrastructure_and_maintenance/cache/persistence_cache.md @@ -40,7 +40,7 @@ For further details on which calls are cached or not, see details in the [Symfon - Symfony Cache tab: for Symfony Cache itself, the tab shows cache lookups to cache backends - [[= product_name_base =]] tab: shows calls made to database back end, and if they're cached or not -To see where and how to contribute additional caches, refer to the [source code](https://github.com/ibexa/core/blob/main/src/lib/Persistence/Cache/Readme.md). +To see where and how to contribute additional caches, refer to the [source code](https://github.com/ibexa/core/blob/5.0/src/lib/Persistence/Cache/Readme.md). ## Persistence cache configuration diff --git a/docs/infrastructure_and_maintenance/performance.md b/docs/infrastructure_and_maintenance/performance.md index abe38d4ead..199064813f 100644 --- a/docs/infrastructure_and_maintenance/performance.md +++ b/docs/infrastructure_and_maintenance/performance.md @@ -138,6 +138,6 @@ The things you need to do: 2. *If not defined, it's the master process which executes the processes until nothing is left to process.* 2. Change the command so that the master process takes care of forking child processes in slices. - 1. For execution in-order, [you may look to our platform installer code](https://github.com/ibexa/core/blob/main/src/bundle/RepositoryInstaller/Command/InstallPlatformCommand.php#L220) + 1. For execution in-order, [you may look to our platform installer code](https://github.com/ibexa/core/blob/5.0/src/bundle/RepositoryInstaller/Command/InstallPlatformCommand.php#L220) used to fork out Solr indexing after installation to avoid cache issues. 2. For parallel execution of the slices, [see Symfony doc for further instruction]([[= symfony_doc =]]/components/process.html#process-signals). diff --git a/docs/infrastructure_and_maintenance/security/development_security.md b/docs/infrastructure_and_maintenance/security/development_security.md index cdc7196bcf..098edb0175 100644 --- a/docs/infrastructure_and_maintenance/security/development_security.md +++ b/docs/infrastructure_and_maintenance/security/development_security.md @@ -59,7 +59,7 @@ Native behavior of `DaoAuthenticationProvider` has been preserved, making it pos A `SecurityController` is used to manage all security-related actions and is thus used to display the login form. It follows all standards explained in [Symfony security documentation]([[= symfony_doc =]]/security.html#form-login). -The base template used is [`Security/login.html.twig`](https://github.com/ibexa/core/blob/main/src/bundle/Core/Resources/views/Security/login.html.twig). +The base template used is [`Security/login.html.twig`](https://github.com/ibexa/core/blob/5.0/src/bundle/Core/Resources/views/Security/login.html.twig). The layout used by default is `%ibexa.content_view.viewbase_layout%` (empty layout) but can be configured together with the login template: diff --git a/docs/multisite/languages/languages.md b/docs/multisite/languages/languages.md index cabac093df..e63049b173 100644 --- a/docs/multisite/languages/languages.md +++ b/docs/multisite/languages/languages.md @@ -122,7 +122,7 @@ ibexa: eng-DE: en_DE ``` -A locale *conversion map* example [can be found in `ibexa/core`, in `locale.yaml`](https://github.com/ibexa/core/blob/main/src/bundle/Core/Resources/config/locale.yml). +A locale *conversion map* example [can be found in `ibexa/core`, in `locale.yaml`](https://github.com/ibexa/core/blob/5.0/src/bundle/Core/Resources/config/locale.yml). ### More complex translation setup diff --git a/docs/product_catalog/product_catalog_guide.md b/docs/product_catalog/product_catalog_guide.md index 7c33fe0014..477723596b 100644 --- a/docs/product_catalog/product_catalog_guide.md +++ b/docs/product_catalog/product_catalog_guide.md @@ -200,7 +200,7 @@ Filtering and pagination function the same as with the product catalog, relying However, criteria and sort clauses within product catalog relying on [[= product_name =]]'s content model are not supported. Depending on your source of product information, you might need to adjust the implementation to be compatible with your data format. -For reference, you could review the [`CriterionVisitor` class](https://github.com/ibexa/example-in-memory-product-catalog/blob/main/src/lib/PIM/InMemory/CriterionVisitor.php) that is part of [Remote PIM example package](add_remote_pim_support.md#install-remote-pim-example-package). +For reference, you could review the [`CriterionVisitor` class](https://github.com/ibexa/example-in-memory-product-catalog/blob/5.0/src/lib/PIM/InMemory/CriterionVisitor.php) that is part of [Remote PIM example package](add_remote_pim_support.md#install-remote-pim-example-package). For more information about product search, see [Product Search Criteria reference](product_search_criteria.md) and [Product Sort Clauses](product_sort_clauses.md). diff --git a/docs/search/criteria_reference/contentname_criterion.md b/docs/search/criteria_reference/contentname_criterion.md index 4f16fd57b2..0c57bf7023 100644 --- a/docs/search/criteria_reference/contentname_criterion.md +++ b/docs/search/criteria_reference/contentname_criterion.md @@ -4,7 +4,7 @@ description: ContentName Search Criterion # ContentName Criterion -The [`ContentName` Search Criterion](https://github.com/ibexa/core/blob/main/src/contracts/Repository/Values/Content/Query/Criterion/ContentName.php) searches for content by its name. +The [`ContentName` Search Criterion](https://github.com/ibexa/core/blob/5.0/src/contracts/Repository/Values/Content/Query/Criterion/ContentName.php) searches for content by its name. ## Arguments diff --git a/docs/search/search_api.md b/docs/search/search_api.md index dd0f39a8aa..83723385ce 100644 --- a/docs/search/search_api.md +++ b/docs/search/search_api.md @@ -199,7 +199,7 @@ When using Repository filtering, provide the results of `ContentService::find()` ### Paginate search results -To paginate search or filtering results, it's recommended to use the [Pagerfanta library](https://github.com/BabDev/Pagerfanta) and [[[= product_name =]]'s adapters for it.](https://github.com/ibexa/core/blob/main/src/lib/Pagination/Pagerfanta/Pagerfanta.php) +To paginate search or filtering results, it's recommended to use the [Pagerfanta library](https://github.com/BabDev/Pagerfanta) and [[[= product_name =]]'s adapters for it.](https://github.com/ibexa/core/blob/5.0/src/lib/Pagination/Pagerfanta/Pagerfanta.php) ``` php // ... @@ -219,12 +219,12 @@ For more information and examples, see [PagerFanta documentation](https://www.ba | Adapter class name | Description | |----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [`ContentSearchAdapter`](https://github.com/ibexa/core/blob/main/src/lib/Pagination/Pagerfanta/ContentSearchAdapter.php) | Makes a search against passed Query and returns [`Content`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Content.html) objects. | -| [`ContentSearchHitAdapter`](https://github.com/ibexa/core/blob/main/src/lib/Pagination/Pagerfanta/ContentSearchHitAdapter.php) | Makes a search against passed Query and returns [`SearchHit`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Search-SearchHit.html) objects instead. | -| [`LocationSearchAdapter`](https://github.com/ibexa/core/blob/main/src/lib/Pagination/Pagerfanta/LocationSearchAdapter.php) | Makes a location search against passed Query and returns [`Location`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Location.html) objects. | -| [`LocationSearchHitAdapter`](https://github.com/ibexa/core/blob/main/src/lib/Pagination/Pagerfanta/LocationSearchHitAdapter.php) | Makes a location search against passed Query and returns [`SearchHit`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Search-SearchHit.html) objects instead. | -| [`ContentFilteringAdapter`](https://github.com/ibexa/core/blob/main/src/lib/Pagination/Pagerfanta/ContentFilteringAdapter.php) | Applies a Content filter and returns a [`ContentList`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-ContentList.html) object. | -| [`LocationFilteringAdapter`](https://github.com/ibexa/core/blob/main/src/lib/Pagination/Pagerfanta/LocationFilteringAdapter.php) | Applies a location filter and returns a [`LocationList`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-LocationList.html) object. | +| [`ContentSearchAdapter`](https://github.com/ibexa/core/blob/5.0/src/lib/Pagination/Pagerfanta/ContentSearchAdapter.php) | Makes a search against passed Query and returns [`Content`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Content.html) objects. | +| [`ContentSearchHitAdapter`](https://github.com/ibexa/core/blob/5.0/src/lib/Pagination/Pagerfanta/ContentSearchHitAdapter.php) | Makes a search against passed Query and returns [`SearchHit`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Search-SearchHit.html) objects instead. | +| [`LocationSearchAdapter`](https://github.com/ibexa/core/blob/5.0/src/lib/Pagination/Pagerfanta/LocationSearchAdapter.php) | Makes a location search against passed Query and returns [`Location`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Location.html) objects. | +| [`LocationSearchHitAdapter`](https://github.com/ibexa/core/blob/5.0/src/lib/Pagination/Pagerfanta/LocationSearchHitAdapter.php) | Makes a location search against passed Query and returns [`SearchHit`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Search-SearchHit.html) objects instead. | +| [`ContentFilteringAdapter`](https://github.com/ibexa/core/blob/5.0/src/lib/Pagination/Pagerfanta/ContentFilteringAdapter.php) | Applies a Content filter and returns a [`ContentList`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-ContentList.html) object. | +| [`LocationFilteringAdapter`](https://github.com/ibexa/core/blob/5.0/src/lib/Pagination/Pagerfanta/LocationFilteringAdapter.php) | Applies a location filter and returns a [`LocationList`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-LocationList.html) object. | | `AttributeDefinitionListAdapter` | Makes a search for product attributes and returns an [`AttributeDefinitionListInterface`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-ProductCatalog-Values-AttributeDefinition-AttributeDefinitionListInterface.html) object. | | `AttributeGroupListAdapter` | Makes a search for product attribute groups and returns an [`AttributeGroupListInterface`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-ProductCatalog-Values-AttributeGroup-AttributeGroupListInterface.html) object. | | `CurrencyListAdapter` | Makes a search for currencies and returns a [`CurrencyListInterface`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-ProductCatalog-Values-Currency-CurrencyListInterface.html) object. | diff --git a/docs/search/search_criteria_and_sort_clauses.md b/docs/search/search_criteria_and_sort_clauses.md index b772074ab1..107b3fa2d3 100644 --- a/docs/search/search_criteria_and_sort_clauses.md +++ b/docs/search/search_criteria_and_sort_clauses.md @@ -14,7 +14,7 @@ For an example of how to use and combine Criteria and Sort Clauses, refer to [Se As Search Criteria and Sort Clauses are value objects which are used to define the query from API perspective, they're common for all storage engines. Each storage engine needs to implement its own handlers for the corresponding Criterion and Sort Clause value object, which are used to translate the value object into a storage-specific search query. -As an example take a look at the [`ContentId` Criterion handler](https://github.com/ibexa/core/blob/main/src/lib/Search/Legacy/Content/Common/Gateway/CriterionHandler/ContentId.php) in Legacy search engine or [`ContentId` Criterion handler](https://github.com/ibexa/solr/blob/main/src/lib/Query/Common/CriterionVisitor/ContentIdIn.php) in Solr search engine. +As an example take a look at the [`ContentId` Criterion handler](https://github.com/ibexa/core/blob/5.0/src/lib/Search/Legacy/Content/Common/Gateway/CriterionHandler/ContentId.php) in Legacy search engine or [`ContentId` Criterion handler](https://github.com/ibexa/solr/blob/5.0/src/lib/Query/Common/CriterionVisitor/ContentIdIn.php) in Solr search engine. ## Custom Criteria and Sort Clauses diff --git a/docs/templating/components.md b/docs/templating/components.md index 8f5bf962ae..a318cb17a7 100644 --- a/docs/templating/components.md +++ b/docs/templating/components.md @@ -69,12 +69,12 @@ You can use an unique group name when creating a Twig Component to create your o | Name | Description | YAML type | |---|---|---| -| [Controller](https://github.com/ibexa/twig-components/blob/main/src/lib/Component/ControllerComponent.php) | Renders a Symfony controller |`controller` | -| [HTML](https://github.com/ibexa/twig-components/blob/main/src/lib/Component/HtmlComponent.php) | Renders static HTML |`html` | -| [Menu](https://github.com/ibexa/twig-components/blob/main/src/lib/Component/MenuComponent.php) | Renders a [menu](https://symfony.com/bundles/KnpMenuBundle/current/index.html) |`menu` | -| [Script](https://github.com/ibexa/twig-components/blob/main/src/lib/Component/ScriptComponent.php) | Renders a [`