Merge branch 'master' into test-links

Author: adriendupuis

code_samples/catalog/custom_attribute_type/src/Attribute/Percent/Form/PercentValueFormMapper.php

@@ -34,9 +34,7 @@ public function createValueForm(
         ];
 
         if ($assignment->isRequired()) {
-            $options['constraints'] = [
-                new Assert\NotBlank(),
-            ];
+            $options['constraints'][] = new Assert\NotBlank();
         }
 
         $builder->add($name, PercentType::class, $options);

docs/content_management/content_management_guide.md

@@ -32,7 +32,7 @@ Content management capabilities are available in all [[= product_name =]] editio
 You can set up content structure, define the templates to be filled with content, and assign different areas of the structure to your editors. 
 Next steps would be to create the actual content, and then classify content items, and organize them as necessary.
 
-You can then publish the content directly, by building a website or a web store, or by using external systems together with a [headless CMS](https://developers.ibexa.co/developer-portal/headless-cms) that relies on the [[= product_name =]] technology.
+You can then publish the content directly, by building a website or a web store, or by using external systems together with a [headless CMS](https://developers.ibexa.co/headless-cms) that relies on the [[= product_name =]] technology.
 
 ## Content structure
 
@@ -284,4 +284,4 @@ Extensive content management capabilities would prove themselves in a setting,
 where multiple buyers from different partner companies connect to an industry leader’s trading website, 
 and they expect to find well organized SKU catalogs that contain basic product information. 
 From there they would like to access detailed specifications, white papers and application notes. 
-The same products could come with different brands and at different price points, depending on the customer segment or origin.
+The same products could come with different brands and at different price points, depending on the customer segment or origin.

docs/content_management/data_migration/exporting_data.md

@@ -14,7 +14,7 @@ or in [a custom folder that you configure](managing_migrations.md#migration-fold
 You can later use this file to import the data.
 
 ``` bash
-php bin/console ibexa:migrations:generate --type=content --mode=create
+php bin/console ibexa:migrations:generate --type=content --mode=create --siteaccess=admin
 ```
 
 This generates a file containing all Content items.
@@ -134,6 +134,12 @@ Note that you should test your migrations. See [Importing data](importing_data.m
 
     Migration command can be executed with database rollback at the end with the `--dry-run` option.
 
+!!! caution
+
+    The `--siteaccess` option usage can be relevant for a multi-language repository.
+    You must export with a SiteAccess that supports all languages, or the migration skips translations in non-supported languages.
+    It is recommended to use the SiteAccess from the Back Office of the targeted repository.
+
 ## type
 
 The mandatory `--type` option defines the type of Repository data to export.

docs/content_management/data_migration/importing_data.md

@@ -15,13 +15,17 @@ and specify the file name within this folder as parameter.
 If you don't specify the file, all files within this directory are used.
 
 ``` bash
-php bin/console ibexa:migrations:migrate --file=my_data_export.yaml
+php bin/console ibexa:migrations:migrate --file=my_data_export.yaml --siteaccess=admin
 ```
 
 Migrations store execution metadata in the `ibexa_migrations` database table.
 This allows incremental upgrades:
 the `ibexa:migrations:migrate` command ignores files that it had previously executed.
 
+Notice that `--siteaccess` option usage is important when several languages are used.
+You must import with a SiteAccess that supports all languages, or the migration skips translations in non-supported languages.
+It's recommended to use the SiteAccess from the Back Office of the targeted repository.
+
 ## Migration step
 
 A data migration step is a single operation in data migration process

docs/content_management/taxonomy/taxonomy.md

@@ -57,7 +57,7 @@ To use this new taxonomy, add an `ibexa_taxonomy_entry_assignement` Field to a C
 
 ### Hide Content tab
 
-The **Content** tab in taxonomy objects, for example, tags and categories, lists all Content assigned to the current taxonomy. 
+The **Content** tab in taxonomy objects, for example, tags and categories, lists all Content assigned to the current taxonomy.
 You can hide the **Content** tab in the **Categories** view.
 
 In configuration add `assigned_content_tab` with the flag `false` (for other taxonomies this flag is by default set to `true`):
@@ -68,3 +68,36 @@ In configuration add `assigned_content_tab` with the flag `false` (for other tax
 ```
 
 For more information about available functionalities of tags, see [User Documentation]([[= user_doc =]]/taxonomy).
+
+## Hide delete button on large subtree
+
+The **Delete** button can be hidden when a taxonomy entry has many children.
+By default, the button is hidden when there are 100 children or more.
+
+The `delete_subtree_size_limit` configuration is [SiteAccess-aware](siteaccess_aware_configuration.md), and can be set per SiteAccess, per SiteAccess group, or globally per default.
+For example:
+
+```yaml
+ibexa:
+    system:
+        default: # or a SiteAccess, or a SiteAccess group
+            taxonomy:
+                admin_ui:
+                    delete_subtree_size_limit: 20
+```
+
+## Remove orphaned Content items
+
+In some rare case, especially in I[[= product_name =]] v4.2 and older, when deleting parent of huge subtrees, some Taxonomy entries are not properly deleted, leaving Content items that point to a non-existing parent.
+The command `ibexa:taxonomy:remove-orphaned-content` deletes those orphaned Content item.
+It works on a taxonomy passed as an argument, and has two options that act as a protective measure against deleting data by mistake:
+
+- `--dry-run` to list deletable Content items, without performing the deletion.
+- `--force` to effectively delete the orphaned Content items.
+
+The following example first lists the orphaned Content items for taxonomy `tags`, and then deletes them:
+
+```bash
+php bin/console ibexa:taxonomy:remove-orphaned-content tags --dry-run
+php bin/console ibexa:taxonomy:remove-orphaned-content tags --force
+```

docs/getting_started/requirements.md

@@ -455,7 +455,7 @@ Recommendation for production setups is to use Varnish/Fastly, Redis/Memcached,
 
     ### Cloud hosting with eZ Platform Cloud and Platform.sh
 
-    In general, eZ Platform Cloud supports all features and services of [Platform.sh](https://platform.sh/hosting/php/ez) that are compatible and supported by the eZ Platform version you use.
+    In general, eZ Platform Cloud supports all features and services of [Platform.sh](https://platform.sh/marketplace/ibexa/) that are compatible and supported by the eZ Platform version you use.
 
     For example:
 

docs/infrastructure_and_maintenance/clustering/clustering_with_aws_s3.md

@@ -14,13 +14,13 @@ meaning AWS S3 will be used to store binary files.
 ## Set up AWS S3 account
 
 1.  Go to <https://aws.amazon.com/> and create an account.
-An [existing Amazon account can be used](http://docs.aws.amazon.com/AmazonS3/latest/gsg/SigningUpforS3.html).
-1.  [Choose a region](http://docs.aws.amazon.com/storagegateway/latest/userguide/available-regions-intro.html).
+An [existing Amazon account can be used](https://docs.aws.amazon.com/AmazonS3/latest/userguide/setting-up-s3.html#sign-up-for-aws).
+1.  [Choose a region](https://docs.aws.amazon.com/storagegateway/latest/vgw/available-regions-intro.html).
 The example below uses EU (Ireland): `eu-west-1`
 1.  Create a bucket in your chosen region and make note of the bucket name:
-<http://docs.aws.amazon.com/AmazonS3/latest/gsg/CreatingABucket.html>.
+<https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-bucket.html>.
 1.  Go to the [IAM Management Console](https://console.aws.amazon.com/iam/home#/users) and create a user.
-See <http://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html>.
+See <https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html>.
 1.  Then create a group and assign the user to the group.
 1.  Assign policies to the group. The `AmazonS3FullAccess` policy gives read/write access to your bucket.
 1.  Still in the IAM console, view the user you created. Click the "Security credentials" tab.
@@ -30,7 +30,7 @@ The secret key cannot be retrieved again after the key has been created, so don'
 
 !!! note
 
-    Make sure that your bucket is [configured as Public](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/block-public-access-bucket.html) to avoid facing 403 errors, as the current S3 handler is meant to store files publicly so they can be served directly from S3.
+    Make sure that your bucket is [configured as Public](https://docs.aws.amazon.com/AmazonS3/latest/userguide/configuring-block-public-access-bucket.html) to avoid facing 403 errors, as the current S3 handler is meant to store files publicly so they can be served directly from S3.
 
 ## Set up [[= product_name =]] for AWS S3
 
@@ -76,8 +76,8 @@ ibexa_io:
     `aws_s3` is an arbitrary handler identifier that is used in the config block below.
     You can configure multiple handlers.
 
-    For example, you could configure one called `gcloud_storage` for a third-party (community-supported)
-    [Google Cloud Storage adapter](https://github.com/thephpleague/flysystem#community-supported).
+    For example, you could configure one called `gcloud_storage` for a
+    [Google Cloud Storage adapter](https://github.com/thephpleague/flysystem#officially-supported-adapters).
 
 Under the `ibexa.system.<scope>.io` [configuration key](configuration.md#configuration-files), enable the binary data handler:
 

docs/personalization/api_reference/content_api.md

@@ -61,7 +61,7 @@ The following call attributes are available:
 
 | Parameter name | Description | Value |
 |---|---|---|
-| `customerid` |A customer ID (for example "00000"), as defined when [enabling Personalization](#multiple-website-hosting).| alphanumeric |
+| `customerid` | A customer ID (for example "00000"), as defined when [enabling Personalization](enable_personalization.md#get-authentication-parameters). Can be used to identify a website in installations that [hosts multiple SiteAccesses]([[= user_doc =]]/personalization/use_cases/#multiple-website-hosting). | alphanumeric |
 | `itemid` | A unique ID of the Content item/product. Used to identify the item in the database. | integer |
 | `itemtypeid` | An ID of the type of Content item/product. In most cases, the value is 1 but you might have items/products of more than one type. | integer |
 | `lang` | A [language code](languages.md) of the Content item/product (for example, "ger-DE"). This parameter is optional. | string |
@@ -75,7 +75,7 @@ An XML representation of the data object used for item import can look like this
     <!-- Version is mandatory and must always be set to 1 -->
     <item id="102" type="1">
         <description>the item's description</description>
-        <price currency="EUR">122</price>
+        <price currency="EUR">1234</price>
         <validfrom>2011-01-01T00:00:00</validfrom>
         <validto>2021-01-01T00:00:00</validto>
         <categorypaths>
@@ -115,7 +115,7 @@ The following keys and attributes used in the XML object are available:
 | `type` | An ID of the type of item/product. This parameter is required. | integer |
 | `description`| Additional information about the item. | alphanumeric |
 | `currency` | Currency used for the price. By default, prices are expressed in EUR. | ISO 4217 |
-| `price` | The item's price in the currency's fractional units (for example, cents).<br/>See below for more information. | integer |
+| `price` | The item's price in the currency's fractional units (for example, cents).<br/>[See below for more information.](#price-and-currency) | integer |
 | `validfrom` | Together with `validto`, defines the lifespan of an item.<br/>If NULL or not available, the item is considered valid immediately.<br/>See below for more information. | ISO 8601 |
 | `validto` | Together with `validfrom`, defines the lifespan of an item.<br/>If NULL or not available, the item is considered valid indefinitely.<br/>See below for more information. | ISO 8601 |
 | `categorypath` | A logical (website) navigation path through which the end user can reach the item/product in your website.<br/>You can define multiple paths for the product.| alphanumeric, separated with "/" ("%2F") characters |
@@ -125,11 +125,16 @@ The following keys and attributes used in the XML object are available:
     Keys and their values can only contain letters, digits and underscore characters.
     Attribute keys are case-sensitive.
 
-##### Currency
+##### Price and currency
 
-If the currency does not have a fractional unit, the main unit is used, 
-for example 12 for 12 Japanese Yen.
-To check whether the currency has fractional units, see the [ISO 4217 standard](https://en.wikipedia.org/wiki/ISO_4217#cite_note-ReferenceA-6).
+The price is given as an integer in the fractional unit of the currency, which ends as removing the decimal separators.
+For example:
+
+- 1234 for 12.34 Euro: `<price currency="EUR">1234</price>`
+- 12 for 12 Japanese Yen: `<price currency="JPY">12</price>`
+- 12345 for 12.345 Tunisian Dinar: `<price currency="TND">12345</price>`
+
+To check how many digits the fractional unit of a currency has, see the [ISO 4217 standard](https://en.wikipedia.org/wiki/ISO_4217#List_of_ISO_4217_currency_codes).
 
 ##### Validity
 

docs/personalization/api_reference/recommendation_api.md

@@ -87,6 +87,17 @@ For more information, see [Submodels]([[= user_doc =]]/personalization/recommend
 
     `GET https://reco.perso.ibexa.co/api/v2/00000/john.doe/landing_page.json?numrecs=50&outputtypeid=1&width-range=10:30&color=green`
 
+##### Segment parameters
+
+If you have configured segments, you can use them in the recommendation model. Pass the following parameter
+to request recommendations for a specific segment or segment group.
+
+Parameter|Example|Description|Value|
+|---|---|---|---|
+|`segments`|`&segments=7,8,10,11`|ID from segment group management|string|
+
+For more information, see [Segments]([[= user_doc =]]/personalization/segment_management).
+
 ## Responses
 
 The recommendation request returns information about the currently used context 

docs/personalization/api_reference/tracking_api.md

@@ -199,7 +199,7 @@ By using the shopping cart products as input for getting recommendations, proble
 with an empty profile or no buy history for the user can be solved.
 The more valuable Basket events instead of recent user clicks can be used to provide
 personalized recommendations.
-It also happens quite often that users "store" products on their shopping [wishlist](#wishlist)
+It also happens quite often that users "store" products on their shopping [wishlist](#wishlist-event)
 and plan to buy them later.
 With the help of this information, personalized shopping cart-based recommendations
 can be provided in the whole shop.
@@ -472,12 +472,12 @@ Example of a trigger message:
    "userExternalId":"[email protected]",
    "triggerType":"REACTIVATION|ABANDAONED_SHOPPING_CART",
    "triggerName":"trigger_ref_code",
-   "triggerOpenedLink":"//tracker.ibexa.co/api/17751/triggeropened/johndoe?triggername=action_trigger_ref_code",
+   "triggerOpenedLink":"//event.perso.ibexa.co/api/17751/triggeropened/johndoe?triggername=action_trigger_ref_code",
    "recommendations":[
       {
          "itemId":959,
          "itemType":46,
-         "clickRecommended":"//tracker.ibexa.co/api/17751/clicktriggered/johndoe/46/959?triggername=action_trigger_ref_code",
+         "clickRecommended":"//event.perso.ibexa.co/api/17751/clicktriggered/johndoe/46/959?triggername=action_trigger_ref_code",
          "attributes":{
             "ses_name":"Minimalista Coffee Table",
 			"ses_image":["img_1", "img_2"]
@@ -536,7 +536,7 @@ The Triggeropened event is sent when the end user opens a trigger message, for e
 
 The URL has the following format:
 
-`GET https://tracker.ibexa.co/api/[customerid]/triggeropened/[userid]?triggername=<action_trigger_reference_code>`
+`GET https://event.perso.ibexa.co/api/[customerid]/triggeropened/[userid]?triggername=<action_trigger_reference_code>`
 
 For a detailed description of embedded parameters, see [event parameters](#event-parameters).
 The request parameter is:
@@ -553,7 +553,7 @@ The Clicktriggered event is sent when the end user clicks the link delivered in
 
 The URL has the following format:
 
-`GET https://tracker.ibexa.co/api/[customerid]/clicktriggered/[userid]/[itemtypeid]/[itemid]?triggername=<action_trigger_reference_code>`
+`GET https://event.perso.ibexa.co/api/[customerid]/clicktriggered/[userid]/[itemtypeid]/[itemid]?triggername=<action_trigger_reference_code>`
 
 For a detailed description of embedded parameters, see [event parameters](#event-parameters).
 The request parameter is: