#96599Slugs with and without trailing slash are considered different but will confuse URL handling in frontend
Description
If pages exist with the slugs “/foobar” and “/foobar/” the checks for duplicate slugs will not change one to a slug with a trailing number.
When you request the URL domain.ext/foobar one of the pages will be accessed. If that page is disabled the frontend will produce a 404 error.
- Foobar ( slug: /foobar ) - Achive - Foobar ( slug: /foobar/ , page hidden)
In this situation domain.ext/foobar produced a 404 error. Changing the slug of the page Foobar in the root to “/foobar-test” made that page accessible. The backend allowed the slug to be renamed back to “/foobar” (the automatic slug generator created that from the page title!).
The workaround was to change the slugs of the page in the archive. This made the active page accessible again.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[BUGFIX] Slugs with and without trailing slash are considered different but will confuse URL handling in frontend Resolves: #96599 Releases: main