diff --git a/docs/customer_management/cp_page_builder.md b/docs/customer_management/cp_page_builder.md index f2152934f4..69e3bdd6b6 100644 --- a/docs/customer_management/cp_page_builder.md +++ b/docs/customer_management/cp_page_builder.md @@ -52,7 +52,7 @@ ibexa: content: tree_root: location_id: location_id_of_customer_portal - excluded_uri_prefixes: [ /media, /images ] + excluded_uri_prefixes: [ /media/, /images/ ] ``` Next, under the `ibexa.system.admin.page_builder` [configuration key](configuration.md#configuration-files), add `custom_portal` to [the SiteAccess list available to Page Builder](multisite_configuration.md#siteaccesses-and-page-builder): @@ -136,7 +136,7 @@ ibexa: content: tree_root: location_id: location_id_of_customer_portals_root_folder - excluded_uri_prefixes: [ /media, /images ] + excluded_uri_prefixes: [ /media/, /images/ ] ``` Next, under the `ibexa.system.admin.page_builder` [configuration key](configuration.md#configuration-files), add `custom_portal` to [the SiteAccess list available to Page Builder](multisite_configuration.md#siteaccesses-and-page-builder): @@ -234,7 +234,7 @@ ibexa: content: tree_root: location_id: location_id_of_customer_portals_root_folder - excluded_uri_prefixes: [ /media, /images ] + excluded_uri_prefixes: [ /media/, /images/ ] ``` To generate the Customer Portal menu you should use `customer_portal.menu.main` key: diff --git a/docs/multisite/multisite_configuration.md b/docs/multisite/multisite_configuration.md index 8a35200057..7954c0486c 100644 --- a/docs/multisite/multisite_configuration.md +++ b/docs/multisite/multisite_configuration.md @@ -184,13 +184,14 @@ ibexa: content: tree_root: location_id: 42 - excluded_uri_prefixes: [/media, /images] + excluded_uri_prefixes: [/media/, /images/] index_page: /EventFrontPage ``` - `location_id` defines the location ID of the content root for the SiteAccess. - `excluded_uri_prefixes` defines which URIs ignore the root limit set by using `location_id`. -In the example above, to access the Media and Images folders, you can use their own URI, even though they're outside the location provided in `content.tree_root.location_id`. + In the example above, to access the Media and Images folders, you can use their own URI, even though they're outside the location provided in `content.tree_root.location_id`. + It's an array of prefixes. So, for example, `[/media]` would also exclude `/mediation` from root limit. - `index_page` is the page shown when you access the root index `/`. !!! note diff --git a/docs/multisite/set_up_campaign_siteaccess.md b/docs/multisite/set_up_campaign_siteaccess.md index 83030c9056..506e188a68 100644 --- a/docs/multisite/set_up_campaign_siteaccess.md +++ b/docs/multisite/set_up_campaign_siteaccess.md @@ -51,7 +51,7 @@ Thanks to this configuration, you can access `/campaign/Articles/Arti ## Reuse content Finally, reuse some content between sites, for example "Logos" from "Images/Media". -You can allow the `campaign` site to access them, even though they're in a different part of the tree, via `excluded_uri_prefixes`: +You can allow the `campaign` site to access them, even though they're in a different part of the tree, via [`excluded_uri_prefixes`](multisite_configuration.md#location-tree): ``` yaml ibexa: @@ -60,7 +60,7 @@ ibexa: content: tree_root: location_id: 57 - excluded_uri_prefixes: [ /media/images/logos ] + excluded_uri_prefixes: [ /media/images/logos/ ] ``` Now, when you use the `campaign` SiteAccess, you can reach `/campaign/Media/Images/Logos`, despite the fact that it's not a sub-item of the "Campaign" location.