Bug #85997
closed
Inconsistent page slugs
100%
Description
Consider the following:
- create a page called "First page" at the site root => its slug is "/first-page"
- rename the page to "First nice page", but don't change the slug
- create a sub-page called "First sub-page" => its slug is "/first-nice-page/first-sub-page"
Now if you access something like www.foo.com/first-nice-page/first-sub-page in a browser, you might be tempted to remove the last segment in the address bar to access the parent page. However www.foo.com/first-nice-page does not exist and will result in a page not found error.
Updated by Francois Suter about 6 years ago
I'm sure the topic has been given a lot of thought, but is it really a good idea that the slug of a given page contains a whole path to the page, including the slugs of all parent pages? That makes really hard to keep consistency when pages are renamed.
Updated by Mathias Schreiber about 6 years ago
So here's what will happen:
Once you rename the page, TYPO3 will ask the user what to do with subsequent changes.
In your case this is either:
- keep slug as is (take the behavior you described)
- change this slug (and child slugs, take SEO penalty)
- change slug, create redirects
To address your last question in the comment:
Having only parts of the slug in a page is exactly what realURL does and that's guessing.
Guessing results in problems.
I completely agree that the slug generator should create slugs based on parent slugs (in your case the subpage would've gotten foo.com/first-page/first-sub-page as a slug).
I strongly disagree on only storing parts of the path on page level :)
Updated by Gerrit Code Review about 6 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58100
Updated by Gerrit Code Review about 6 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58100
Updated by Benni Mack about 6 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset bdff18fb9ccbe80be70a393436988ca4261f99df.