Entity paths override paths from routing.yml

I was able to reproduce this from the standard installation profile by creating a new basic page with the alias /node/1/edit. Once saved, it is impossible to edit the node again. The only workaround is to visit /node/1/delete, which would cause any other field data to be lost.

I think there's a case that this could be labelled a bug because it can:

• Cause a significant admin- or developer-facing bug with no workaround.
• Cause user input to be lost, but do not delete or corrupt existing data.

However, this has clearly been possible for a very long time, so feels fair.

Create a constraint with the message: "This URL is used in routing.yml. Please try another one."

or

Automatically add a suffix, such as /admin/modules-0, to the alias.

In my opinion, it's better to reject the path alias rather than silently change it. However, I'm not sure we should explain that the problem is that the URL is in a routing.yml file. That's not always going to be true. For example, /node/1/edit the ContentEntityType annotation in Node.php.

What do you think of a more generic message like ?

Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .

This is a duplicate of 📌 Do not allow existing or reserved paths as aliases Needs work .