From 7d5325bfb54e36374a537e76a74ad259b9263fce Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Wed, 19 Jun 2024 14:45:44 +0200 Subject: [PATCH] NOP URL aliases caution added --- docs/content_management/url_management/url_management.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/content_management/url_management/url_management.md b/docs/content_management/url_management/url_management.md index 5105291f39..853ef1969b 100644 --- a/docs/content_management/url_management/url_management.md +++ b/docs/content_management/url_management/url_management.md @@ -156,6 +156,10 @@ URL aliases are not SiteAccess-aware. When creating an alias, you can select a S If the SiteAccess root path (configured in `content.tree_root.location_id`) is different than the default, the prefix path that results from the configured content root is prepended to the final alias path. +!!! caution "Creating custom URL aliases on the same level with a virtual (NOP) entry" + + From v5.0 of [[= product_name =]]: If there is already a custom URL alias with path `/a/b` where `a` is a virtual entry (NOP: not pointing to any content), renaming or creating another content on the same level using a colliding name, `a` in this case, would result in the creation of a `a2` entry, as `a` is already taken by path `/a/b`. + ### URL alias pattern configuration You can configure how [[= product_name =]] generates URL aliases.