We have a content.tree_root.location_id configured to ID 54 (name "start"). I want to create an URLAlias that can be called with http://localhost/test.

When creating a global URLAlias in Backend to /test it does not match, as the start is missing. When unchecking the last checkbox (use global alias) the alias ist being created as /start/noname2/test, which does not match either. The only way to get it working is to manually set it to /start/test or creating it as a test (without a leading slash) and leaving the last checkbox unchecked. This is very unhandy.

a) Why is it possible at all, to create a URLAlias that does not match?
b) Where does the "noname2" come from

Steps to reproduce (scenario a):

1. Create a page named "start" and set content.tree_root.location_id to it's location id
2. Create another page "test" under "start"
3. Add an URL Alias to "test" with the URL "/test-redirect"
4. Open http://localhost/test-redirect
5. Get a 404 instead of being redirected to /test

Steps to reproduce (scenario b):

1. Create a page named "start" and set content.tree_root.location_id to it's location id
2. Create another page "test" under "start"
3. Add an URL Alias to "test" with the URL "/test-redirect" unchecking the option "use global alias"
4. See that URL alias was created as /start/noname2/test-redirect
5. Open http://localhost/test-redirect
6. Get a 404 instead of being redirected to /test