Bug #87842
closedSlugs of subpages of a root page inside a sys_folder contain the name of the root page
0%
Description
Slugs of root pages inside sys folders cannot be edited. Because of this, the slug of subpages will contain an unwanted url part of the root page.
How to reproduce (TYPO3 9.5.5):
- Create a sys folder
- Create a normal page inside this sys folder
- Edit the page, make a root page out of it and save
- Add the site configuration for this specific root page
- Create a page inside the root page and edit this page
- Now have a look at the slug. It contains the slug of the root page
- The slug can be edited manually for the child pages, but this gets complicated if there are many pages
What we expect:
The slug of a root page should be editable so that we can make a slash out of it.
Updated by Marcel Macasso over 5 years ago
- Category set to Site Handling, Site Sets & Routing
Updated by Marcel Macasso almost 5 years ago
- Subject changed from Slugs of root pages inside sys folders cannot be edited to Slugs of subpages of a root page inside a sys_folder contain the name of the root page
Updated by Dmitry Dulepov over 3 years ago
It sounds like you are trying to create nested sites. This never was a good idea...
Updated by Marcel Macasso over 2 years ago
Dmitry Dulepov wrote in #note-3:
It sounds like you are trying to create nested sites. This never was a good idea...
No, we didn't try to nest root pages inside root pages. We tried to add root pages inside folders though, as we have more than 40 root pages and this was our way to keep the pagetree clean and ordered. It could be that this was never meant to work and because of that not a good idea, but our intentions were good ;)
As the behavior described in the ticket seems to not happen in TYPO3 10, this ticket can be closed.
Updated by Riccardo De Contardi over 2 years ago
- Status changed from New to Closed
@Marcel Macasso Thank you for you feedback!
I close this issue as requested. If you think that this is the wrong decision or I have misunderstood or experience the issue again, please reopen it or open a new issue with a reference to this one.
Thank you.