Added more mentions about clearing persistence cache (#3174)

* Added more mentions about clearing persistence cache

* Self review

* Apply suggestions from code review

Co-authored-by: Tomasz Dąbrowski <64841871+dabrt@users.noreply.github.com>

* Vale remarks

* Should -> consider comitting

* Apply suggestion from @mnocon

---------

Co-authored-by: Tomasz Dąbrowski <64841871+dabrt@users.noreply.github.com>

Author: mnocon

docs/snippets/page_block_cache_clear.md

@@ -2,9 +2,9 @@
 
     Persistence cache must be cleared after any modifications have been made to the block config in Page Builder, such as adding, removing or altering the page blocks, block attributes, validators or views configuration.
 
-    To clear the persistence cache run `./bin/console cache:pool:clear [cache-pool]` command.
-    The default cache-pool is named `cache.tagaware.filesystem`.
-    The default cache-pool when running Redis or Valkey is named `cache.redis`.
+    To clear the persistence cache, run `php bin/console cache:pool:clear <cache-pool>` command.
+    The default cache pool is named `cache.tagaware.filesystem`.
+    The default cache pool when running Redis or Valkey is named `cache.redis`.
     If you have customized the [persistence cache configuration](https://doc.ibexa.co/en/latest/infrastructure_and_maintenance/cache/persistence_cache/#what-is-cached), the name of your cache pool might be different.
 
     In prod mode, you also need to clear the symfony cache by running `./bin/console c:c`.

docs/update_and_migration/from_5.0/update_from_5.0.md

@@ -331,6 +331,120 @@ Additionally, you must remove the following line from your `.platform.app.yaml`
 curl -fs https://get.symfony.com/cloud/configurator | bash
 ```
 
+## v5.0.7
+
+### Update Symfony from 7.3 to 7.4
+
+This version of [[= product_name =]] requires [Symfony 7.4](https://symfony.com/releases/7.4).
+Update Symfony constraints in `composer.json` before updating the packages.
+
+1. In `composer.json`, update `extra.symfony.require` to allow installing a higher Symfony version:
+
+    ```json
+    "extra": {
+        "symfony": {
+            "require": "7.4.*"
+        }
+    }
+    ```
+
+2. To allow installing Symfony 7.4, update the requirements for **all** `symfony` packages in `composer.json` as in the example below:
+
+    ``` diff
+    -        "symfony/<package>"": "7.3.*",
+    +        "symfony/<package>"": "7.4.*",
+    ```
+
+3. Review your code, configuration, and third-party bundles for Symfony 7.4 compatibility.
+
+    For more details about the new version, see the official Symfony [upgrade instructions](https://github.com/symfony/symfony/blob/7.4/UPGRADE-7.4.md) and [blog posts introducing this release](https://symfony.com/blog/category/living-on-the-edge/8.0-7.4).
+    Key changes include:
+
+
+    - Independent application cache directory
+
+        Symfony 7.4 introduces a new [share directory](https://symfony.com/blog/new-in-symfony-7-4-share-directory), dedicated for storing application cache on the file system.
+        If you decide to configure it (for example, by setting the `APP_SHARE_DIR` environment variable), review your existing scripts for explicit `var/cache` usage (for example, `rm -rf var/cache`) and decide whether to include `var/share` in the script.
+
+        !!! caution "Always clear the persistence cache with `cache:pool:clear` command"
+
+            Starting with Symfony 7.4, running `php bin/console cache:clear` doesn't clear the [[= product_name =]] persistence cache, even when using a filesystem-based cache pool.
+
+            To clear the persistence cache, for example after adding a [custom Page Builder block](create_custom_page_block.md), you must always run:
+
+            ```bash
+            php bin/console cache:pool:clear <cache-pool>
+            ```
+
+            The default cache pool is named `cache.tagaware.filesystem`.
+            The default cache pool when running Redis or Valkey is named `cache.redis`.
+            If you have customized the persistence cache configuration, the name of your cache pool might be different.
+
+            For more information about persistence cache, see [Persistence cache](persistence_cache.md).
+
+    - Array-based PHP configuration format
+
+        As part of the new [array-based PHP configuration format](https://symfony.com/blog/new-in-symfony-7-4-better-php-configuration), Symfony creates the `config/reference.php` file.
+        Consider committing this file to the repository.
+
+4. Update Ibexa packages by running:
+
+    === "[[= product_name_headless =]]"
+
+        ``` bash
+        yarn upgrade @ibexa/frontend-config @ibexa/ts-config
+        composer require ibexa/headless:v5.0.7 --with-all-dependencies --no-scripts
+        composer recipes:install ibexa/headless --force -v
+        ```
+    === "[[= product_name_exp =]]"
+
+        ``` bash
+        yarn upgrade @ibexa/frontend-config @ibexa/ts-config
+        composer require ibexa/experience:v5.0.7 --with-all-dependencies --no-scripts
+        composer recipes:install ibexa/experience --force -v
+        ```
+    === "[[= product_name_com =]]"
+
+        ``` bash
+        yarn upgrade @ibexa/frontend-config @ibexa/ts-config
+        composer require ibexa/commerce:v5.0.7 --with-all-dependencies --no-scripts
+        composer recipes:install ibexa/commerce --force -v
+        ```
+
+5. Manually restore the entry for `JMSTranslationBundle` in `config/bundles.php` to [its previous position](https://github.com/ibexa/commerce-skeleton/blob/v5.0.6/config/bundles.php#L14):
+
+    ``` hl_lines="2"
+        FOS\HttpCacheBundle\FOSHttpCacheBundle::class => ['all' => true],
+        JMS\TranslationBundle\JMSTranslationBundle::class => ['all' => true],
+        Liip\ImagineBundle\LiipImagineBundle::class => ['all' => true],
+    ```
+
+You're now running [Symfony 7.4, the current long-term support version](https://symfony.com/releases/7.4).
+
+### [[= product_name_cloud =]] `ibexa:setup` command deprecation
+
+Following the changes introduced in v5.0.6, the `ibexa:setup` command is deprecated as of v5.0.7 and will be removed in v6.0.0.
+Additionally, the `ibexa/cloud` package must be installed for the [[= product_name_cloud =]] build to succeed.
+The command `ibexa:cloud:setup` from this package replaces the deprecated `ibexa:setup`.
+
+To learn how to adjust your configuration, see [update instructions for v5.0.6](#ibexa-cloud-configuration-update).
+
+### Database update [[% include 'snippets/experience_badge.md' %]] [[% include 'snippets/commerce_badge.md' %]]
+
+Run the provided SQL upgrade script to update your database:
+
+=== "MySQL"
+
+    ``` bash
+    mysql -u <username> -p <password> <database_name> < vendor/ibexa/installer/upgrade/db/mysql/ibexa-5.0.6-to-5.0.7.sql
+    ```
+
+=== "PostgreSQL"
+
+    ``` bash
+    psql <database_name> < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-5.0.6-to-5.0.7.sql
+    ```
+
 ## LTS Updates and additional packages
 
 [LTS Updates](editions.md#lts-updates) are standalone packages with their own update procedures.