Merge branch '5.0' into notifications

Author: adriendupuis

code_samples/api/public_php_api/src/perform_count.php

@@ -0,0 +1,18 @@
+<?php declare(strict_types=1);
+
+use Ibexa\Contracts\Core\Repository\Values\Content\LocationQuery;
+use Ibexa\Contracts\Core\Repository\Values\Content\Query;
+
+/** @var \Ibexa\Contracts\Core\Repository\SearchService $searchService */
+
+// For location searches
+$locationQuery = new LocationQuery();
+$locationQuery->performCount = false;
+
+$locationResult = $searchService->findLocations($locationQuery);
+
+// For content searches
+$contentQuery = new Query();
+$contentQuery->performCount = false;
+
+$contentResult = $searchService->findContent($contentQuery);

code_samples/cache/http_cache/src/response_tagging.php

@@ -0,0 +1,11 @@
+<?php declare(strict_types=1);
+
+/** @var \Ibexa\Contracts\HttpCache\ResponseTagger\ResponseTagger $responseTagger */
+/** @var \Ibexa\Core\MVC\Symfony\View\ContentValueView|\Ibexa\Core\MVC\Symfony\View\LocationValueView $view */
+$responseTagger->tag($view); // When working with a view
+
+/** @var \Ibexa\Contracts\Core\Repository\Values\Content\Content $content */
+$responseTagger->tag($content->getContentInfo()); // When working with a content item
+
+/** @var \Ibexa\Contracts\Core\Repository\Values\Content\Location $location */
+$responseTagger->tag($location); // When working with a location

code_samples/recent_activity/src/recent_activity_disable.php

@@ -0,0 +1,9 @@
+<?php declare(strict_types=1);
+
+/** @var \Ibexa\Contracts\ActivityLog\ActivityLogServiceInterface $activityLogService */
+$activityLogService->disable();
+
+// Perform operations that should not be logged to the activity log
+// ...
+
+$activityLogService->enable();

code_samples/recommendations/events/product_visit_event.html.twig

@@ -1,4 +1,4 @@
-# templates/product/view.html.twig #}
+{# templates/product/view.html.twig #}
 {% extends 'base.html.twig' %}
 
 {% block content %}

docs/administration/recent_activity/recent_activity.md

@@ -10,35 +10,62 @@ Recent activity log displays last actions in the repository (whatever their orig
 
 To learn more about its back office usage and the actions logged by default, see [Recent activity in User Documentation]([[= user_doc =]]/recent_activity/recent_activity/).
 
-## Configuration and cronjob
+## Configuration
 
-With some configuration, you can customize the log length in the database or on screen.
+With some configuration, you can customize the log length in the database or on screen, or disable the logging completely.
 A command maintains the log size in database, it should be scheduled through CRON.
 
-- The configuration `ibexa.system.<scope>.activity_log.pagination.activity_logs_limit` sets the number of log items shown per page in the back office (default value: 25).
-A log item is a group of entries, or an entry without group.
-- The configuration `ibexa.repositories.<repository>.activity_log.truncate_after_days` sets the number of days a log entry is kept before it's deleted by the `ibexa:activity-log:truncate` command (default value: 30 days).
+### Log retention
+
+The `ibexa.repositories.<repository>.activity_log.truncate_after_days` setting sets the number of days a log entry is kept before it's deleted by the `ibexa:activity-log:truncate` command (default value: 30 days).
 
-For example, the following configuration sets 15 days of life to the log entries on the `default` repository, and 20 context groups per page for the `admin_group` SiteAccess group:
+For example, the following configuration sets 15 days of life to the log entries on the `default` repository:
 
 ```yaml
 ibexa:
     repositories:
         default:
             activity_log:
                 truncate_after_days: 15
+```
+
+To automate a regular truncation, the command `ibexa:activity-log:truncate` must be added to a crontab.
+To minimize the number of entries to delete, it's recommended to execute the command more than one time a day.
+
+For every exact hour, the cronjob line is:
+`0 * * * * cd [path-to-ibexa]; php bin/console ibexa:activity-log:truncate --quiet --env=prod`
+
+### Display limit
+
+The `ibexa.system.<scope>.activity_log.pagination.activity_logs_limit` setting sets the number of log items shown per page in the back office (default value: 25).
+
+For example, the following configuration sets 20 context groups per page for the `admin_group` SiteAccess group:
+
+```yaml
+ibexa:
     system:
         admin_group:
             activity_log:
                 pagination:
                     activity_logs_limit: 20
 ```
+A log item is a group of entries, or an entry without group.
 
-To automate a regular truncation, the command `ibexa:activity-log:truncate` must be added to a crontab.
-To minimize the number of entries to delete, it's recommended to execute the command more than one time a day.
+### Disable activity log
 
-For every exact hour, the cronjob line is:
-`0 * * * * cd [path-to-ibexa]; php bin/console ibexa:activity-log:truncate --quiet --env=prod`
+The `ibexa.repositories.<repository>.activity_log.enabled` setting can disable activity log entirely for a given [repository](repository_configuration.md).
+
+For example, to disable the activity log for the `default` repository:
+
+```yaml
+ibexa:
+    repositories:
+        default:
+            activity_log:
+                enabled: false
+```
+
+You can also disable activity log for a single action by using the [PHP API](#disable-logging-activities).
 
 ## Permission and security
 
@@ -132,6 +159,7 @@ migration
     Keep activity logging as light as possible.
     Don't make database requests or heavy computation at logging time.
     Keep them for activity log list display time.
+    If needed, you can [disable logging for specific operations](#disable-logging-activities) using the PHP API.
 
 #### Create an entry
 
@@ -259,6 +287,21 @@ Thanks to the previous subscriber, the related object is available at display ti
 [[= include_code('code_samples/recent_activity/templates/themes/admin/activity_log/ui/my_feature/simulate.html.twig') =]]
 ```
 
+### Disable logging activities
+
+You can disable logging the activities with PHP API, for example, when loading large amounts of data in cases where you don't want logging to slow down the process or the actions to be included in the log.
+
+Call [`ActivityLogService::disable()`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-ActivityLog-ActivityLogServiceInterface.html#method_disable)
+ before running the relevant code, then [`ActivityLogService::enable()`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-ActivityLog-ActivityLogServiceInterface.html#method_enable) to restore the logging process:
+
+``` php
+[[= include_code('code_samples/recent_activity/src/recent_activity_disable.php') =]]
+```
+
+When disabled, any call to [`ActivityLogService::save()`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-ActivityLog-ActivityLogServiceInterface.html#method_save) has no effect and no entries are written to the database.
+
+You can check the current state with [`ActivityLogService::isEnabled()`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-ActivityLog-ActivityLogServiceInterface.html#method_isEnabled) and [`ActivityLogService::isDisabled()`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-ActivityLog-ActivityLogServiceInterface.html#method_isDisabled).
+
 ## REST API
 
 You can browse activity logs with REST API.

docs/api/event_reference/shopping_list_events.md

@@ -2,7 +2,7 @@
 description: Events that are triggered while managing shopping lists.
 page_type: reference
 editions: lts-update commerce
-month_change: true
+month_change: false
 ---
 
 # Shopping list events

docs/commerce/shopping_list/install_shopping_list.md

@@ -1,7 +1,7 @@
 ---
 description: Install the Shopping list LTS update.
 editions: lts-update commerce
-month_change: true
+month_change: false
 ---
 
 # Install shopping list

docs/commerce/shopping_list/shopping_list_api.md

@@ -1,7 +1,7 @@
 ---
 description: Manage shopping lists from PHP API or REST API.
 editions: lts-update commerce
-month_change: true
+month_change: false
 ---
 
 # Shopping list APIs

docs/commerce/shopping_list/shopping_list_design.md

@@ -1,7 +1,7 @@
 ---
 description: Learn how to integrate the shopping list features to your own online store design.
 editions: lts-update commerce
-month_change: true
+month_change: false
 ---
 
 # Shopping list design

docs/commerce/shopping_list/shopping_list_guide.md

@@ -1,7 +1,7 @@
 ---
 description: A shopping list allows users to save potential purchases, recurring product sets, and other items for future use in the cart.
 editions: lts-update commerce
-month_change: true
+month_change: false
 ---
 
 # Shopping list feature guide