Add option to exclude pages from speaking url
Add a option to exclude pages from speaking url (slug), if the page is not the current page.
This feature is necessary for every installation that used realurl in the past.
Links to e.q. landingpages may don't work anymore, if a installation upgrades from 8.7 with realurl to 9.5 with native url handling.
If this feature would be developed, the upgrade wizard "PopulatePageSlugs" should be extended to set the exclude flag on upgrade.
#1 Updated by Chris Müller 2 months ago
I think this feature isn't needed, because you can set the slug of the page individually. Take for example the structure:
page-1 -> subpage-1-1
page-1 -> subpage-1-2 -> subsubpage-1-2-1
You can change your slug e.g. to
/subpage-1-2 instead of /page-1/subpage-1-2
so that page-1 isn't shown in slug for subpage-1-2
Any subsequent pages of subpage-1-2 will also omit page-1, because the slug of the parent page is taken into account when generating a new page under subpage-1-2.
This behaviour is more flexibel than with RealURL, because you can change the complete slug of the page, not only the segment of the page (where you need a possibility to omit a segment).
To make it short, just set the slug of your landing page to the slug you want. That's it.
#4 Updated by Sebastian Krikke 2 months ago
I think even for new projects this is a nice to have feature.
When editiors create new pages and in-between Page segment schould not be shown then the editor has to edit the slug every Time they create a page.
In that regard it would be much easier to simply tell the parent page to not show in a slug, so that editors don't have to bother with the slug.
Another Point is, when you use sluggenerator (for example: 3rd-Party extensions) so rearrange the whole page tree after an upgrade. Here you need to go into every Page to press the refresh button and modify the Slug after. it would be much more comfortable to exclude some specific pages and let the rest autogenerate.
#6 Updated by Benni Mack 16 days ago
- Status changed from New to Needs Feedback
it's not possible for us to build such a solution in TYPO3 v9 as it would require to modify the database, which I agreed to not do again after 9.5.5 (due to some hundreds of installations with auto-updates breaking as there was a missing DB field).
So, what I've built was a hook within the Slug Generation which can take care of this:
So, it should be fairly easy to create an extension to handle all custom specifications needed for an extension author. Hope this helps. If there are well-proven extensions we can look into that for adding this to TYPO3 v10. If there are any extensions available, let me know.
Sorry for the inconvenience on handling it for TYPO3 v9.