Problem/Motivation
#2509300: Path alias UI allows node/1 and /node/1 as system path then fatals converted most remaining instances to have a starting slash,
but there are a couple left, see https://www.drupal.org/node/2509300#comment-10068572
#2509300: Path alias UI allows node/1 and /node/1 as system path then fatals converted most remaining instances to have a starting slash,
but there are a couple left, see https://www.drupal.org/node/2509300#comment-10068572
Comments
Comment #1
dawehner.
Comment #2
Crell commenteddawehner, this sounds Novice-y. Can you provide instructions and tag accordingly?
Comment #3
catchAlso a task.
Comment #17
smustgrave commentedThank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
Comment #18
smustgrave commentedwanted to bump 1 more time.
Comment #19
nexaguard commentedTested on Drupal 10.3.x and 11.x-dev, patch applies cleanly and the behavior works as expected.
No regressions found in AliasWhitelist or PathValidator behavior.
Confirming that using a leading slash improves route resolution consistency.