# Update from v4.6.x to v4.6.latest

## Update the application

Note which version you actually have before starting.

First, run:

**Ibexa Headless**

```
composer require ibexa/headless:4.6.29 --with-all-dependencies --no-scripts
composer recipes:install ibexa/headless --force -v
```

**Ibexa Experience**

```
composer require ibexa/experience:4.6.29 --with-all-dependencies --no-scripts
composer recipes:install ibexa/experience --force -v
```

**Ibexa Commerce**

```
composer require ibexa/commerce:4.6.29 --with-all-dependencies --no-scripts
composer recipes:install ibexa/commerce --force -v
```

Then execute the instructions below starting from the version you're upgrading from.

Caution

To avoid deprecations when using PHP 8.2, 8.3, or 8.4, run the following commands:

```
composer config extra.runtime.error_handler "\\Ibexa\\Contracts\\Core\\MVC\\Symfony\\ErrorHandler\\Php82HideDeprecationsErrorHandler"
composer dump-autoload
```

## v4.6.1

No additional steps needed.

## v4.6.2

#### Database update

Run the following scripts:

**MySQL**

```
mysql -u <username> -p <password> <database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.1-to-4.6.2.sql
```

**PostgreSQL**

```
psql <database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-4.6.1-to-4.6.2.sql
```

## v4.6.3

### Notification config update

The configuration of the package `ibexa/notifications` has changed. This package is required by other packages, such as `ibexa/connector-actito` for [Transactional emails](https://doc.ibexa.co/en/latest/commerce/transactional_emails/transactional_emails/), `ibexa/payment`, or `ibexa/user`.

If you are customizing the configuration of the `ibexa/notifications` package, and using SiteAccess aware configuration to change the `Notification` subscriptions, you have to manually change your configuration by using the new node name `notifier` instead of the old `notifications`.

For example, the following v4.6.2 config:

```
ibexa:
    system:
        my_siteacces_name:
            notifications: # old
                subscriptions:
                    Ibexa\Contracts\Shipping\Notification\ShipmentStatusChange:
                        channels:
                            - sms
```

becomes the following from v4.6.3:

```
ibexa:
    system:
        my_siteacces_name:
            notifier: # new
                subscriptions:
                    Ibexa\Contracts\Shipping\Notification\ShipmentStatusChange:
                        channels:
                            - sms
```

## v4.6.4

#### Database update

Run the following scripts:

**MySQL**

```
mysql -u <username> -p <password> <database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.3-to-4.6.4.sql
```

**PostgreSQL**

```
psql <database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-4.6.3-to-4.6.4.sql
```

## v4.6.5

No additional steps needed.

## v4.6.6

No additional steps needed.

## v4.6.7

No additional steps needed.

## v4.6.8

No additional steps needed.

## v4.6.9

No additional steps needed.

## v4.6.10

No additional steps needed.

## v4.6.11

### Ibexa Cloud

Update Platform.sh configuration for PHP and Varnish.

Generate new configuration with the following command:

```
composer ibexa:setup --platformsh
```

Review the changes applied to `.platform.app.yaml` and `.platform/`, merge with your custom settings if needed, and commit them to Git.

## v4.6.12

If the new bundle `ibexa/core-search` has not been added by the recipes, enable it by adding the following line in `config/bundles.php`:

```
    Ibexa\Bundle\CoreSearch\IbexaCoreSearchBundle::class => ['all' => true],
```

## v4.6.13

This release comes with a command to clean up duplicated entries in the `ezcontentobject_attribute` table, which were created due to an issue related to previewing content in different languages.

If you're affected, remove the duplicated entries by running the following command:

```
php bin/console ibexa:content:remove-duplicate-fields
```

Caution

Remember about [**proper database backup**](https://doc.ibexa.co/en/latest/infrastructure_and_maintenance/backup/index.md) before running the command in the production environment.

You can customize the behavior of the command with the following options:

- `--batch-size` or `-b` - number of attributes affected per iteration. Default value = 10000.
- `--max-iterations` or `-i` - maximum iterations count. Default value = -1 (unlimited).
- `--sleep` or `-s` - wait time between iterations, in milliseconds. Default value = 0.

## v4.6.14

### Security

This release contains security fixes. For more information, see [the published security advisory](https://developers.ibexa.co/security-advisories/ibexa-sa-2024-006-vulnerabilities-in-content-name-pattern-commerce-shop-and-varnish-vhost-templates). For each of the following fixes, evaluate the vulnerability to determine whether you might have been affected. If so, take appropriate action, for example by [revoking passwords](https://doc.ibexa.co/en/latest/users/passwords/#revoking-passwords) for all affected users.

#### BREACH vulnerability

The [BREACH](https://www.breachattack.com/) attack is a security vulnerability against HTTPS when using HTTP compression.

If you're using Varnish, update the VCL configuration to stop compressing both the Ibexa DXP's REST API and JSON responses from your backend. Fastly users are not affected.

**Varnish on Ibexa Cloud**

Update Platform.sh configuration and scripts.

Generate new configuration with the following command:

```
composer ibexa:setup --platformsh
```

Review the changes, merge with your custom settings if needed, and commit them to Git before deployment.

**Varnish 6**

Update your Varnish VCL file to align it with the [`vendor/ibexa/http-cache/docs/varnish/vcl/varnish6.vcl`](https://github.com/ibexa/http-cache/blob/4.6/docs/varnish/vcl/varnish6.vcl) file.

**Varnish 7**

Update your Varnish VCL file to align it with the [`vendor/ibexa/http-cache/docs/varnish/vcl/varnish7.vcl`](https://github.com/ibexa/http-cache//blob/4.6/docs/varnish/vcl/varnish7.vcl) file.

```

If you're not using a reverse proxy like Varnish or Fastly, adjust the compressed `Content-Type` in the web server configuration.
For more information, see the [updated Apache and nginx template configuration](https://github.com/ibexa/post-install/pull/86/files).

#### XSS in Content name pattern

There are no additional update steps to execute.

#### Outdated version of jQuery in ibexa/commerce-shop package

Only users of the [old Commerce solution](https://doc.ibexa.co/en/latest/update_and_migration/from_4.3/update_from_4.3_old_commerce/index.md) are affected.
There are no additional update steps to execute.

### Other changes

#### Disable translations of identifiers in Product Catalog's categories

The possibility of translating identifiers and parent information for the Categories in Product Catalog might lead to data consistency issues.

Disable it by running the following migration:

```

php bin/console ibexa:migrations:import vendor/ibexa/product-catalog/src/bundle/Resources/migrations/2024_07_25_07_00_non_translatable_product_categories.yaml --name=2024_07_25_07_00_non_translatable_product_categories.yaml php bin/console ibexa:migrations:migrate --file=2024_07_25_07_00_non_translatable_product_categories.yaml

```

#### Update web server configuration

Adjust the web server configuration to prevent direct access to the `index.php` file when using URLs consisting of multiple path segments.

See [the updated Apache and nginx template files](https://github.com/ibexa/post-install/pull/70/files) for more information.

## v4.6.15

### Removed `symfony/orm-pack` and `symfony/serializer-pack` dependencies

This release no longer directly requires the `symfony/orm-pack` and `symfony/serializer-pack` Composer dependencies, which can remove some dependencies from your project during the update process.

If you rely on them in your project, for example by using Symfony's `ObjectNormalizer` to create your own REST endpoints, run the following command before updating Ibexa packages:

```

composer require symfony/serializer-pack symfony/orm-pack

```

Then, verify that Symfony Flex installed the versions you were using before.

## v4.6.16

No additional steps needed.

## v4.6.17

### Security

This release contains security fixes.
For more information, see [the published security advisory](https://developers.ibexa.co/security-advisories/ibexa-sa-2025-001-vulnerabilities-in-shopping-cart-and-publish-unscheduling).
For each of the following fixes, evaluate the vulnerability to determine whether you might have been affected.
If so, take appropriate action.

#### CartOwner permission limitation exposes carts

This release fixes a critical vulnerability in the REST API regarding shopping carts.
There are no additional update steps to execute.

#### Unauthorized user can cancel scheduled publish events

This release fixes vulnerability in publish scheduling, ensures that `edit/create` policies are correctly checked.
There are no additional update steps to execute.

#### Dependency upgrades

This release upgrades the requirements for [Twig to v3.19](https://github.com/twigphp/Twig/security/advisories/GHSA-3xg3-cgvq-2xwr) and [PHPSpreadsheet to v1.29.9](https://github.com/PHPOffice/PhpSpreadsheet/security), resolving several vulnerabilities of varying severity in those dependencies.
There are no additional update steps to execute.

## v4.6.18

No additional steps needed.

## v4.6.19

### Security

This release fixes a critical vulnerability in the [RichText field type](https://doc.ibexa.co/en/latest/content_management/field_types/field_type_reference/richtextfield/index.md).
By entering a maliciously crafted input into the RichText field type's XML, the attacker could perform an attack using [XML external entity (XXE) injection](https://portswigger.net/web-security/xxe).
To exploit this vulnerability, an attacker would need to have edit permission to content with RichText fields.

For more information, see the [published security advisory IBEXA-SA-2025-002](https://developers.ibexa.co/security-advisories/ibexa-sa-2025-002-xxe-vulnerability-in-richtext).

Evaluate the vulnerability to determine whether you might have been affected.
If so, take appropriate action.
There are no additional update steps to execute.

### Ibexa Rector

The new [Ibexa Rector](https://github.com/ibexa/rector/) package is now available.
It's an optional package based on [Rector](https://getrector.com/) and comes with additional rules for working with Ibexa code.

You can use it to get rid of PHP code deprecations and start preparing your project for the next major release.

Note

Ibexa Rector requires PHP 8.3 and you must upgrade your codebase first.
To do it, you can use Rector and the [existing PHP upgrade sets](https://getrector.com/documentation/integration-to-new-project#content-2-upgrade-php-first).

To get started with Ibexa Rector, execute the following steps:

1. Add the Composer dependency:

```

composer require --dev ibexa/rector:^4.6

```
2. Adjust the created `rector.php` configuration file to match your project structure
3. Run Rector in the dry-run mode to preview the changes:

```

vendor/bin/rector --dry-run

```
4. Run Rector:

```

vendor/bin/rector

```

## v4.6.20

No additional steps needed.

## v4.6.21

### Security

This security advisory resolves XSS vulnerabilities in several parts of the back office of the DXP.
Back office access and varying levels of editing and management permissions are required to exploit these vulnerabilities.

For more information, see the [security advisory IBEXA-SA-2025-003](https://developers.ibexa.co/security-advisories/ibexa-sa-2025-003-xss-vulnerabilities-in-back-office).

Evaluate the vulnerability to determine whether you might have been affected.
If so, take appropriate action.
There are no additional update steps to execute.

### Database update

Run the following scripts:

**MySQL**

```

mysql -u <username> -p <password> \<database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.20-to-4.6.21.sql

```

**PostgreSQL**

```

psql \<database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-4.6.20-to-4.6.21.sql

```

## v4.6.22

### Added support for Solr 9

This release adds support for [Solr 9](https://doc.ibexa.co/en/latest/getting_started/requirements/#search).

To update Solr within an existing Ibexa DXP project, first refer to the [Solr 9 upgrade planning](https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html) instructions.

Then, follow the [instructions for setting up Solr 9 with Ibexa DXP](https://doc.ibexa.co/en/latest/search/search_engines/solr_search_engine/install_solr/#configure-and-start-solr) and merge them with your custom configuration.

Changes include:

1. Configuration files

   - the `schema.xml` configuration file became [`managed-schema.xml`](https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-6.html#managed-schema-is-now-the-default)
   - the [removed `LatLonType` field is replaced by the `LatLonPointSpatialField` field](https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-7.html#deprecations-and-removed-features)
2. New [Solr version parameter](https://doc.ibexa.co/en/latest/search/search_engines/solr_search_engine/install_solr/#configure-solr-version)

Once Solr 9 is fully configured, [refresh the search index](https://doc.ibexa.co/en/latest/search/reindex_search/index.md).

### Set character set for activity log tables (Experience) (Commerce)

When using MySQL or MariaDB, run the following script to ensure correct character set for activity log tables:

**MySQL**

```

mysql -u <username> -p <password> \<database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.21-to-4.6.22.sql

```

## v4.6.23

No additional steps needed.

## v4.6.24

### Database update

**MySQL**

```

mysql -u <username> -p <password> \<database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.23-to-4.6.24.sql

```

**PostgreSQL**

```

psql \<database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-4.6.23-to-4.6.24.sql

```

## v4.6.25

### Form Builder performance fix: missing indexes on form submission data (Experience) (Commerce)

In large production databases, the `ezform_form_submissions` and `ezform_form_submission_data` tables may contain a lot of rows.
Missing indexes can cause high CPU load and slow queries.

Run the provided SQL upgrade script to add the missing indexes to your database:

**MySQL**

```

mysql -u <username> -p <password> \<database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.24-to-4.6.25.sql

```

**PostgreSQL**

```

psql \<database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-4.6.24-to-4.6.25.sql

```

## v4.6.26

No additional steps needed.

## v4.6.27

### Elasticsearch 8 support

As of v4.6.27, Ibexa DXP adds optional support for Elasticsearch 8.19 or higher through the new `ibexa/elasticsearch8` package.

By default, Ibexa DXP continues to support Elasticsearch 7.16.2+ with the `ibexa/elasticsearch` package.
To use Elasticsearch 8, follow these steps:

#### Install Elasticsearch 8 package

Replace the existing Elasticsearch package and install Elasticsearch 8:

```

composer require ibexa/elasticsearch8:4.6.29

```

#### Update Elasticsearch server

Upgrade your Elasticsearch server to version 8.19 or higher.
For detailed instructions, follow the [Elasticsearch upgrade guide](https://www.elastic.co/guide/en/elastic-stack/8.19/upgrading-elastic-stack.html#prepare-to-upgrade).

When you use Ibexa Cloud, see [Elasticsearch service](https://docs.upsun.com/add-services/elasticsearch.html) for a list of supported versions.

#### Update configuration

Update your configuration in `config/packages/ibexa_elasticsearch.yaml` as decribed below:

##### Replace connection pool settings

The `connection_pool` and `connection_selector` settings are ignored when using Elasticsearch 8.
Replace them with appropriate `node_pool_selector` and `node_pool_resurrect` settings:

```

# Elasticsearch 7 configuration

ibexa_elasticsearch: connections: default: connection_pool: 'Elasticsearch\\ConnectionPool\\StaticNoPingConnectionPool' connection_selector: 'Elasticsearch\\ConnectionPool\\Selectors\\RoundRobinSelector'

```

```

# Elasticsearch 8 configuration

ibexa_elasticsearch: connections: default: node_pool_selector: 'Elastic\\Transport\\NodePool\\Selector\\RoundRobin' node_pool_resurrect: 'Elastic\\Transport\\NodePool\\Resurrect\\NoResurrect'

```

For more information, see [Connection pool and node pool settings](https://doc.ibexa.co/en/4.6/search/search_engines/elasticsearch/configure_elasticsearch/#connection-pool-and-node-pool-settings).

##### Remove trace option

The `trace` debugging option is no longer available in Elasticsearch 8:

```

# Elasticsearch 7 configuration

ibexa_elasticsearch: connections: default: debug: true trace: true

```

```

# Elasticsearch 8 configuration

ibexa_elasticsearch: connections: default: debug: true # Trace option is no longer available

```

#### Reindex content

After upgrading to Elasticsearch 8 and updating your configuration, reindex the search engine:

1. Push the index templates:

```

php bin/console ibexa:elasticsearch:put-index-template --overwrite

```
2. Reindex your content:

```

php bin/console ibexa:reindex

```

### Removed Composer dependencies

The following unused Composer dependencies have been removed from `ibexa/core`:

- `guzzlehttp/guzzle`
- `php-http/guzzle6-adapter`

If your project uses Guzzle directly, you should add these dependencies to your project's `composer.json` file.

To check if you need to add these dependencies, run:

```

composer why guzzlehttp/guzzle composer why php-http/guzzle6-adapter

```

If only the `ibexa/core` entry appears in the output, check your codebase to determine if you use Guzzle directly.
If you do, add the required dependencies to your project:

```

composer require guzzlehttp/guzzle:^6.5 php-http/guzzle6-adapter:^2.0

```

### Messenger support in CDP

If you're using [CDP](https://doc.ibexa.co/en/latest/cdp/cdp/index.md) and haven't configured Ibexa Messenger yet, do so now.
Follow the [Messenger setup instructions](https://doc.ibexa.co/en/4.6/infrastructure_and_maintenance/background_tasks/#install-package) to continue.

## Notify support

Inform the support team that you have updated your installation.
They update your Service portal to match the new version.
This ensures that you receive notifications about new maintenance releases and security advisories for the correct version.
You can contact the support team at [support@ibexa.co](mailto:support@ibexa.co) or through your [Service portal](https://support.ibexa.co).

With the product updated to the latest version, you can now finish the update process or proceed to updating the LTS Updates packages.

## v4.6.28

### Database update (Experience) (Commerce)

Run the provided SQL upgrade script to adapt your database to latest change in [form builder](https://doc.ibexa.co/en/latest/content_management/forms/form_builder_guide/index.md)'s `max_length` validator behavior:

**MySQL**

```

mysql -u <username> -p <password> \<database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.27-to-4.6.28.sql

```

**PostgreSQL**

```

psql \<database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-4.6.27-to-4.6.28.sql

```

Prior, `0` was interpreted as "no length limit".
Now, `0` is interpreted as "length limited to zero characters" and `NULL` as "no length limit".

## v4.6.29

### GraphQL package update

Due to the [GHSA-68jq-c3rv-pcrr security issue](https://github.com/advisories/GHSA-68jq-c3rv-pcrr), the GraphQL package requirements have been updated to allow installing higher versions in which this issue is resolved.

When doing the update, you have two options:

#### Update GraphQL packages and custom code (recommended)

Make sure the `webonyx/graphql-php` package is installed in a version higher or equal to v15.31.5.

If you [extended GraphQL to support custom field types](https://doc.ibexa.co/en/latest/api/graphql/graphql_custom_ft/index.md), update the returned expression from `@=resolver(...)` to `@=query(...)` and change the argument syntax from an array to variadic arguments as in the following example:

```

-return sprintf('@=resolver("MyFieldValue", [field, %s])', $myArg); +return sprintf('@=query("MyFieldValue", field, %s)', $myArg);

```

Then, regenerate the GraphQL schema by running:

```

rm -rf config/graphql/types/ibexa/ php bin/console ibexa:graphql:generate-schema

```

#### Implement other countermeasures

If updating the GraphQL packages isn't possible right now, for example because the project is using PHP 7.4 where the fix is not available, review the security issue carefully and assess the danger.

If you choose to implement countermeasures without updating the GraphQL packages, for example by restricting access to the GrapQL endpoint with rate limiting, authentication, or [WAF](https://en.wikipedia.org/wiki/Web_application_firewall), then you can silence the advisory in `composer.json`:

```

"config": { "audit": { "ignore": { "GHSA-68jq-c3rv-pcrr": "Description of the countermeasures you've implemented causing this one to be safe to ignore." } } }

```

In addition, consider upgrading your project to one of [the actively supported PHP versions](https://doc.ibexa.co/en/latest/getting_started/requirements/#php).

### Database update (Experience) (Commerce)

Run the provided SQL upgrade script to update your database:

**MySQL**

```

mysql -u <username> -p <password> \<database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-4.6.28-to-4.6.29.sql

```

**PostgreSQL**

```

psql \<database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-4.6.28-to-4.6.29.sql

```

## LTS Updates

[LTS Updates](https://doc.ibexa.co/en/4.6/ibexa_products/editions/#lts-updates) are standalone packages with their own update procedures.
To use the [latest features](https://doc.ibexa.co/en/latest/release_notes/ibexa_dxp_v4.6/index.md) added to them, update them separately with the following commands:

**Discounts**

### Discounts (LTS Update) (Commerce)

To install the [Discounts feature](https://doc.ibexa.co/en/latest/discounts/discounts_guide/index.md), see the [installation instructions](https://doc.ibexa.co/en/4.6/discounts/install_discounts/).

If you're already using it, run the following command to get the latest version of this feature:

```

composer require ibexa/discounts:4.6.29 ibexa/discounts-codes:4.6.29

```

Then apply manually the changes described below.

### Discounts v4.6.20

#### Policy changes

The `discount/view` policy is no longer required for the store customers to use a discount and must be removed from all users who are not managing discounts.
The policy allows to access all the discount details, including the coupon codes to activate them, which could lead to system abuse.

To learn more, see the [discounts policies overview](https://doc.ibexa.co/en/4.6/permissions/policies/).

#### Database update

Run the following scripts:

**MySQL**

```

CREATE TABLE ibexa_discount_code_usage ( id INT AUTO_INCREMENT NOT NULL, discount_code_id INT NOT NULL, order_id INT NOT NULL, discriminator VARCHAR(10) NOT NULL, used_at DATETIME NOT NULL COMMENT '(DC2Type:datetime_immutable)', INDEX ibexa_discount_code_usage_discount_code_idx (discount_code_id), INDEX ibexa_discount_code_usage_order_idx (order_id), PRIMARY KEY(id) ) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_520_ci` ENGINE = InnoDB;

CREATE TABLE ibexa_discount_code_usage_email ( id INT NOT NULL, user_email VARCHAR(190) DEFAULT NULL, INDEX ibexa_discount_code_usage_email_idx (user_email), UNIQUE INDEX ibexa_discount_codes_usage_email_uidx (id, user_email), PRIMARY KEY(id) ) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_520_ci` ENGINE = InnoDB;

CREATE TABLE ibexa_discount_code_usage_user ( id INT NOT NULL, user_id INT DEFAULT NULL, INDEX ibexa_discount_code_usage_user_idx (user_id), UNIQUE INDEX ibexa_discount_codes_usage_user_uidx (id, user_id), PRIMARY KEY(id) ) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_520_ci` ENGINE = InnoDB;

ALTER TABLE ibexa_discount_code_usage ADD CONSTRAINT ibexa_discount_code_usage_code_fk FOREIGN KEY (discount_code_id) REFERENCES ibexa_discount_code (id) ON UPDATE CASCADE ON DELETE CASCADE;

ALTER TABLE ibexa_discount_code_usage ADD CONSTRAINT ibexa_discount_code_usage_order_fk FOREIGN KEY (order_id) REFERENCES ibexa_order (id) ON UPDATE CASCADE ON DELETE CASCADE;

ALTER TABLE ibexa_discount_code_usage_email ADD CONSTRAINT ibexa_discount_code_usage_email_fk FOREIGN KEY (id) REFERENCES ibexa_discount_code_usage (id) ON UPDATE CASCADE ON DELETE CASCADE;

ALTER TABLE ibexa_discount_code_usage_user ADD CONSTRAINT ibexa_discount_code_usage_user_fk FOREIGN KEY (id) REFERENCES ibexa_discount_code_usage (id) ON UPDATE CASCADE ON DELETE CASCADE;

ALTER TABLE ibexa_discount_code_usage_user ADD CONSTRAINT ibexa_discount_code_usage_user_content_fk FOREIGN KEY (user_id) REFERENCES ezuser (contentobject_id) ON UPDATE CASCADE ON DELETE CASCADE;

```

**PostgreSQL**

```

CREATE TABLE ibexa_discount_code_usage ( id SERIAL NOT NULL, discount_code_id INT NOT NULL, order_id INT NOT NULL, discriminator VARCHAR(10) NOT NULL, used_at TIMESTAMP(0) WITHOUT TIME ZONE NOT NULL, PRIMARY KEY(id) );

CREATE INDEX ibexa_discount_code_usage_discount_code_idx ON ibexa_discount_code_usage (discount_code_id);

CREATE INDEX ibexa_discount_code_usage_order_idx ON ibexa_discount_code_usage (order_id);

COMMENT ON COLUMN ibexa_discount_code_usage.used_at IS '(DC2Type:datetime_immutable)';

CREATE TABLE ibexa_discount_code_usage_email ( id INT NOT NULL, user_email VARCHAR(190) DEFAULT NULL, PRIMARY KEY(id) );

CREATE INDEX ibexa_discount_code_usage_email_idx ON ibexa_discount_code_usage_email (user_email);

CREATE UNIQUE INDEX ibexa_discount_codes_usage_email_uidx ON ibexa_discount_code_usage_email (id, user_email);

CREATE TABLE ibexa_discount_code_usage_user ( id INT NOT NULL, user_id INT DEFAULT NULL, PRIMARY KEY(id) );

CREATE INDEX ibexa_discount_code_usage_user_idx ON ibexa_discount_code_usage_user (user_id);

CREATE UNIQUE INDEX ibexa_discount_codes_usage_user_uidx ON ibexa_discount_code_usage_user (id, user_id);

ALTER TABLE ibexa_discount_code_usage ADD CONSTRAINT ibexa_discount_code_usage_code_fk FOREIGN KEY (discount_code_id) REFERENCES ibexa_discount_code (id) ON UPDATE CASCADE ON DELETE CASCADE NOT DEFERRABLE INITIALLY IMMEDIATE;

ALTER TABLE ibexa_discount_code_usage ADD CONSTRAINT ibexa_discount_code_usage_order_fk FOREIGN KEY (order_id) REFERENCES ibexa_order (id) ON UPDATE CASCADE ON DELETE CASCADE NOT DEFERRABLE INITIALLY IMMEDIATE;

ALTER TABLE ibexa_discount_code_usage_email ADD CONSTRAINT ibexa_discount_code_usage_email_fk FOREIGN KEY (id) REFERENCES ibexa_discount_code_usage (id) ON UPDATE CASCADE ON DELETE CASCADE NOT DEFERRABLE INITIALLY IMMEDIATE;

ALTER TABLE ibexa_discount_code_usage_user ADD CONSTRAINT ibexa_discount_code_usage_user_fk FOREIGN KEY (id) REFERENCES ibexa_discount_code_usage (id) ON UPDATE CASCADE ON DELETE CASCADE NOT DEFERRABLE INITIALLY IMMEDIATE;

ALTER TABLE ibexa_discount_code_usage_user ADD CONSTRAINT ibexa_discount_code_usage_user_content_fk FOREIGN KEY (user_id) REFERENCES ezuser (contentobject_id) ON UPDATE CASCADE ON DELETE CASCADE NOT DEFERRABLE INITIALLY IMMEDIATE;

```

### Discounts v4.6.22

#### Database update

Run the following scripts:

**MySQL**

```

ALTER TABLE ibexa_discount ADD override_prioritization tinyint(1) NOT NULL DEFAULT 0; CREATE INDEX ibexa_discount_prioritization_idx ON ibexa_discount (override_prioritization, type, priority); ALTER TABLE ibexa_discount_code ADD global_limit INT DEFAULT NULL;

```

**PostgreSQL**

```

ALTER TABLE ibexa_discount ADD override_prioritization tinyint(1) NOT NULL DEFAULT 0; CREATE INDEX ibexa_discount_prioritization_idx ON ibexa_discount (override_prioritization, type, priority); ALTER TABLE ibexa_discount_code ADD global_limit INT DEFAULT NULL;

```

### Discounts v4.6.24

#### Database update

Run the following scripts:

**MySQL**

```

ALTER TABLE ibexa_discount ADD indexed_at DATETIME DEFAULT NULL COMMENT '(DC2Type:datetime_immutable)';

CREATE INDEX ibexa_discount_indexed_at_idx ON ibexa_discount (indexed_at);

```

**PostgreSQL**

```

ALTER TABLE ibexa_discount ADD indexed_at TIMESTAMP(0) WITHOUT TIME ZONE DEFAULT NULL;

COMMENT ON COLUMN ibexa_discount.indexed_at IS '(DC2Type:datetime_immutable)';

CREATE INDEX ibexa_discount_indexed_at_idx ON ibexa_discount (indexed_at);

```

**AI Actions**

### AI Actions (LTS Update)

To install the [AI actions feature](https://doc.ibexa.co/en/latest/ai_actions/ai_actions_guide/index.md), see the [installation instructions](https://doc.ibexa.co/en/4.6/ai_actions/install_ai_actions/).

If you're already using it, run the following command to get the latest version of this feature:

```

composer require ibexa/connector-ai:4.6.29 ibexa/connector-openai:4.6.29

```

**Date and time attribute**

### Date and time attribute (LTS Update)

To install the [Date and time attribute](https://doc.ibexa.co/en/latest/product_catalog/attributes/date_and_time/index.md), see the [installation instructions](https://doc.ibexa.co/en/4.6/pim/attributes/date_and_time/#installation).

If you're already using it, run the following command to get the latest version of this feature:

```

composer require ibexa/product-catalog-date-time-attribute:4.6.29

```

**Symbol attribute**

### Symbol attribute (LTS Update)

To install the [Symbol attribute](https://doc.ibexa.co/en/latest/product_catalog/attributes/symbol_attribute_type/index.md), see the [installation instructions](https://doc.ibexa.co/en/4.6/pim/attributes/symbol_attribute_type/#installation).

If you're already using it, run the following command to get the latest version of this feature:

```

composer require ibexa/product-catalog-symbol-attribute:4.6.29

```

**Integrated help**

### Integrated help (LTS Update)

See [Integrated help](https://doc.ibexa.co/en/latest/administration/back_office/integrated_help/index.md) for more information.

If you're already using it, run the following command to get the latest version of this feature:

```

composer require ibexa/integrated-help:4.6.29

```

**Collaborative editing**

### Collaborative editing (LTS Update)

To learn more about the [Collaborative editing](https://doc.ibexa.co/en/latest/content_management/collaborative_editing/collaborative_editing_guide/), see the [installation instructions](https://doc.ibexa.co/en/4.6/content_management/collaborative_editing/install_collaborative_editing).

If you're already using it, run the following command to get the latest version of this feature:

```

composer require ibexa/share:4.6.29 ibexa/collaboration:4.6.29

```

If you're using the Real-time collaborative editing, in addition run:

```

composer require ibexa/fieldtype-richtext-rte:4.6.29 ibexa/ckeditor-premium:4.6.29

```
```