Release notes for v5.0.7 and v4.6.29 #3133
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -10,6 +10,156 @@ | |||||
|
|
||||||
| <div class="release-notes" markdown="1"> | ||||||
|
|
||||||
| [[% set version = 'v5.0.7' %]] | ||||||
|
|
||||||
| [[= release_note_entry_begin( | ||||||
| "Google Gemini connector " + version, | ||||||
| '2026-04-14', | ||||||
| ['Headless', 'Experience', 'Commerce', 'LTS Update', 'New feature', 'First release'] | ||||||
| ) =]] | ||||||
|
|
||||||
| This release introduces a new AI connector that allows you to integrate [AI Actions](https://doc.ibexa.co/en/5.0/ai_actions/ai_actions/) with [Google Gemini](https://gemini.google/overview/#what-gemini-is). | ||||||
| Among other things, you can use it as an alternative embeddings provider for the taxonomy suggestions feature. | ||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
|
|
||||||
| For more information, see how to [install and configure the Google Gemini connector](https://doc.ibexa.co/en/5.0/ai_actions/configure_ai_actions/#install-google-gemini-connector). | ||||||
|
|
||||||
| [[= release_note_entry_end() =]] | ||||||
|
|
||||||
| [[= release_note_entry_begin( | ||||||
| "Integrated help " + version, | ||||||
| '2026-04-14', | ||||||
| ['Headless', 'Experience', 'Commerce', 'LTS Update', 'New feature'] | ||||||
| ) =]] | ||||||
|
|
||||||
| ### Product tour | ||||||
|
|
||||||
| The product tour is a new Integrated help feature that helps back office contributors to discover [[= product_name =]]. | ||||||
|
|
||||||
| For more information, see [Product tour](https://doc.ibexa.co/en/5.0/administration/back_office/product_tour/). | ||||||
|
|
||||||
| [[= release_note_entry_end() =]] | ||||||
|
|
||||||
| [[= release_note_entry_begin( | ||||||
| "Ibexa DXP " + version, | ||||||
|
Check failure on line 43 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
| '2026-04-14', | ||||||
| ['Headless', 'Experience', 'Commerce', 'New feature'] | ||||||
| ) =]] | ||||||
|
|
||||||
| ### Raptor connector | ||||||
|
|
||||||
| The SiteAccess-aware Raptor connector provides a seamless integration between [[= product_name =]] and [Raptor Recommendation Engine](https://www.raptorservices.com/website-recommendations/). | ||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
|
|
||||||
| For more information, see [SiteAccess-aware Raptor connector](https://doc.ibexa.co/en/5.0/cdp/raptor_integration/raptor_connector/). | ||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
|
|
||||||
| #### Tracking | ||||||
|
|
||||||
| This add-on includes two Twig functions to ease tracking setting: | ||||||
|
|
||||||
| - `ibexa_tracking_script` to load the JavaScript tracking code, for more information, see [Tracking script](https://doc.ibexa.co/en/5.0/cdp/raptor_integration/tracking_script/) | ||||||
| - `ibexa_tracking_track_event` to send tracking events from your pages, for more information, see [Tracking event function](https://doc.ibexa.co/en/5.0/cdp/raptor_integration/tracking_event_function/) | ||||||
|
|
||||||
| #### Recommendations blocks [[% include 'snippets/experience_badge.md' %]] [[% include 'snippets/commerce_badge.md' %]] | ||||||
|
|
||||||
| This add-on introduces a set of recommendation blocks available in the [Page Builder](https://doc.ibexa.co/en/5.0/content_management/pages/page_builder_guide/), | ||||||
| designed to suggest relevant content or products to users, such as the most popular items or viewed by others. | ||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
|
|
||||||
| For more information, see [Recommendation blocks in Page Builder](https://doc.ibexa.co/en/5.0/cdp/raptor_integration/pb_blocks/). | ||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
|
|
||||||
| ### Quable PIM | ||||||
|
Check notice on line 68 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
Vale is right 😄 |
||||||
|
|
||||||
| Add-on to integrate [[[= pim_product_name =]]](https://www.quable.com/en) with [[= product_name =]]. | ||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
|
|
||||||
| For more information, see [Quable PIM Integration](https://doc.ibexa.co/en/5.0/product_catalog/quable/). | ||||||
|
|
||||||
| ### Developer experience | ||||||
|
|
||||||
| #### Symfony 7.4 | ||||||
|
|
||||||
| Symfony is upgraded from 7.3 to 7.4. | ||||||
|
Check notice on line 78 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
|
adriendupuis marked this conversation as resolved.
|
||||||
| See [what's new in Symfony 7.4](https://symfony.com/blog/category/living-on-the-edge/8.0-7.4) | ||||||
| and [how to update Symfony within [[= product_name =]]](https://doc.ibexa.co/en/5.0/update_and_migration/from_5.0/update_from_5.0/#update-symfony-from-73-to-74). | ||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
|
|
||||||
| #### Taxonomy search | ||||||
|
|
||||||
| Two [taxonomy search](https://doc.ibexa.co/en/5.0/content_management/taxonomy/taxonomy_api/search) criteria are added: | ||||||
|
Check notice on line 84 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
|
Contributor
There was a problem hiding this comment. To be completely honest, TaxonomySubtree was added 3 years ago and missed 🙈 But I think it's ok to mention it here (#3082 (review))
Contributor
Author
There was a problem hiding this comment. I could mention one here and keep the other for new_in_doc.md |
||||||
|
|
||||||
| - [`TaxonomyNoEntries`](https://doc.ibexa.co/en/5.0/search/criteria_reference/taxonomy_no_entries/) to find content items to which no taxonomy entries have been assigned. | ||||||
|
Check notice on line 86 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
| - [`TaxonomySubtree`](https://doc.ibexa.co/en/5.0/search/criteria_reference/taxonomy_subtree/) for content items assigned to a taxonomy entry or any of its descendants. | ||||||
|
|
||||||
| #### Custom parameters in `ibexa_render()` | ||||||
|
|
||||||
| You can now pass custom parameters to templates when using the `ibexa_render()` Twig function with the new `params` option, similar to how you can with `render(controller())`.Collapse annotationCheck notice on line R18[vale] docs/release_notes/ibexa_dxp_v5.0.md#L18Check notice: [vale] docs/release_notes/ibexa_dxp_v5.0.md#L18[Ibexa.ByUsing] Prefer 'by using' or 'with' to plain 'using'.Build & test documentation / valeView details | ||||||
|
Check notice on line 91 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
|
|
||||||
| This allows you to provide additional context or data to your view templates: | ||||||
|
|
||||||
| ``` html+twig | ||||||
| {{ ibexa_render(content, { | ||||||
| 'viewType': 'line', | ||||||
| 'method': 'inline', | ||||||
| 'params': { | ||||||
| 'custom_param': 'custom_value', | ||||||
| 'another_param': 'another_value' | ||||||
| } | ||||||
| }) }} | ||||||
| ``` | ||||||
|
|
||||||
| The parameters are available in your template as regular variables. | ||||||
|
|
||||||
| For more information, see [`ibexa_render()` Twig function](https://doc.ibexa.co/en/5.0/templating/twig_function_reference/content_twig_functions/#ibexa_render). | ||||||
|
|
||||||
| #### Try-catch support in data migrations | ||||||
|
|
||||||
| Data migrations now support try-catch error handling, allowing you to wrap migration steps with exception handling logic. | ||||||
| You can use it for migrations that might fail under certain conditions but should not break the entire migration process. | ||||||
|
|
||||||
| For example, you can create languages without checking if they already exist: | ||||||
|
|
||||||
| ``` yaml | ||||||
| [[= include_file('code_samples/data_migration/examples/try_catch_step.yaml') =]] | ||||||
| ``` | ||||||
|
|
||||||
| The `try_catch` step allows you to specify which exceptions to catch and whether to continue executing remaining steps after an exception occurs. | ||||||
|
|
||||||
| For more information, see [Error handling with try-catch](https://doc.ibexa.co/en/5.0/content_management/data_migration/importing_data/#error-handling-with-try-catch). | ||||||
|
|
||||||
| #### Translation-related Twig Component groups | ||||||
|
Check notice on line 125 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
|
|
||||||
| Four groups of [Twig components](https://doc.ibexa.co/en/5.0/templating/components/) related to Admin UI translation are added. | ||||||
|
Check notice on line 127 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
|
|
||||||
| For more information, see [Customizing the back office with Twig Components > Admin UI](https://doc.ibexa.co/en/5.0/administration/back_office/back_office_elements/custom_components/#admin-ui). | ||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
|
|
||||||
| #### REST API | ||||||
|
|
||||||
| You can now find examples for some REST request bodies in the [OpenAPI REST API](rest_api_usage.md#openapi-support): | ||||||
|
|
||||||
| - in the right column of the [online reference](https://doc.ibexa.co/en/5.0/api/rest_api/rest_api_reference/rest_api_reference.html) where the example is used as a sample instead of a duplicate of middle column schema, | ||||||
|
Check notice on line 135 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
| and in the downloadable OpenAPI specification files | ||||||
| - on your dev instance at `/api/ibexa/v2/doc` in an “Example Value” tab of the "Request Body" section, alongside the "Schema" tab | ||||||
| - in the generated JSON or YAML OpenAPI specifications when running `ibexa:openapi` command | ||||||
|
|
||||||
| #### PHP API | ||||||
|
Check notice on line 140 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
|
|
||||||
| The following additions were made to the PHP API: | ||||||
|
|
||||||
| - [`Ibexa\Contracts\Core\FieldType\ReferenceAwareExternalStorage`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-FieldType-ReferenceAwareExternalStorage.html) | ||||||
| - [`Ibexa\Contracts\Core\Options\Context`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Options-Context.html) | ||||||
| - [`Ibexa\Contracts\CorporateAccount\Order\OrderStatusLabelProviderInterface`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/classes/Ibexa-Contracts-CorporateAccount-Order-OrderStatusLabelProviderInterface.html) | ||||||
| - [`Ibexa\Contracts\ProductCatalog\Events\ProductAttributeRenderEvent`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/classes/Ibexa-Contracts-ProductCatalog-Events-ProductAttributeRenderEvent.html) | ||||||
| - [`Ibexa\Contracts\Taxonomy\Search\Query\Criterion\TaxonomyNoEntries`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/classes/Ibexa-Contracts-Taxonomy-Search-Query-Criterion-TaxonomyNoEntries.html) | ||||||
| (for more information, see [its search criteria reference entry](https://doc.ibexa.co/en/5.0/search/criteria_reference/taxonomy_no_entries/)) | ||||||
| - optionally, from the [Raptor connector add-on](https://doc.ibexa.co/en/5.0/cdp/raptor_integration/raptor_connector/), classes of the [`Ibexa\Contracts\ConnectorRaptor` namespace](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/namespaces/ibexa-contracts-connectorraptor.html) | ||||||
|
Check notice on line 150 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
| - optionally, from the [Integrated help LTS-Update](https://doc.ibexa.co/en/5.0/administration/back_office/integrated_help/), classes of the [`Ibexa\Contracts\IntegratedHelp` namespace](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/namespaces/ibexa-contracts-integratedhelp.html) | ||||||
|
Check notice on line 151 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
|
|
||||||
| ### AI Actions in Page Builder blocks [[% include 'snippets/experience_badge.md' %]] [[% include 'snippets/commerce_badge.md' %]] | ||||||
|
Check notice on line 153 in docs/release_notes/ibexa_dxp_v5.0.md
|
||||||
|
adriendupuis marked this conversation as resolved.
Outdated
|
||||||
|
|
||||||
| You can now use the [refining text AI Actions](https://doc.ibexa.co/en/5.0/ai_actions/ai_actions_guide/#refining-text) in Page Builder blocks string and text inputs. | ||||||
|
|
||||||
| ### Full changelog | ||||||
|
|
||||||
| [[% include 'snippets/release_50.md' %]] | ||||||
|
|
||||||
| [[= release_note_entry_end() =]] | ||||||
|
|
||||||
| [[% set version = 'v5.0.6' %]] | ||||||
|
|
||||||
| [[= release_note_entry_begin( | ||||||
|
|
||||||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.