Bug #86727
closed
Numeric in slugs on multidomain instances.
0%
Description
I have an instance with 30+ domains.On running upgrade wizard for slug generation ,it produces slugs with numeric like '/9/exampleproduct'.This kind of slug generation is not fair and affects the site ranking and thus clients wont allow this type of slugs.
Please check the logic for slug generation on multi domain instances.
Updated by Georg Ringer over 5 years ago
- Status changed from New to Needs Feedback
- Assignee deleted (
Benni Mack)
Please provide a bit more information about the structure of the sites. Do you have a page called "9"?
Updated by Ricky Mathew over 5 years ago
Georg Ringer wrote:
Please provide a bit more information about the structure of the sites. Do you have a page called "9"?
I dont have page called 9 but i assume it is the 9th domain got termed as /9/.For that domain all slugs starts with /9/something.Likewise for pages in some 30th domain the slug will be like /30/something.
Updated by Stefanos Karasavvidis over 5 years ago
I tried to reproduce this by going from a 8 multisite installation to 9, with no success.
With and without realurl, with and without nested sites, and with various other variations. Every time I got urls with no numeric prefix.
It would help if you could provide more specific information about your setup.
Updated by Stig Nørgaard Færch over 5 years ago
I have multisite installation where the root page of one of the sites refuses to have an empty (or /) slug. It always inserts /1. If insert somthing in the field, it is accepted.
Slug/URL segment - /1 is wrongly saved, when trying to set / on rootpage: https://forge.typo3.org/issues/87454
Updated by Benni Mack about 5 years ago
- Target version changed from next-patchlevel to Candidate for patchlevel
Updated by Riccardo De Contardi almost 5 years ago
- Related to Bug #87454: Slug/URL segment - /1 is wrongly saved, when trying to set / on rootpage. added
Updated by Riccardo De Contardi almost 5 years ago
- Related to Bug #87884: Root page of page tree suddenly gets slug "/1" added
Updated by Riccardo De Contardi over 4 years ago
Has this one been solved with #87884 ?
Updated by Jan Kornblum about 4 years ago
- Related to Bug #90736: Wrong slug fields for siteroots (level > 1) in multidomain environment and no possibility to modify them added
Updated by Jan Kornblum about 4 years ago
Riccardo De Contardi wrote:
Has this one been solved with #87884 ?
Not in 9.5.14. I've created another ticket with some more explanations. https://forge.typo3.org/issues/90736
Updated by Sybille Peters over 2 years ago
Issue https://forge.typo3.org/issues/90736 has been resolved. Can you check if the issue still persists?
Updated by Christian Kuhn about 2 years ago
- Status changed from Needs Feedback to Closed
Hey. I hope it's ok to close here since the issue has likely been solved with #90736. In case this still persists in recent core versions, let's restart with a fresh issue together with more information on how to reproduce.