Bug #86727

Numeric in slugs on multidomain instances.

Added by Ricky Mathew about 1 year ago. Updated 3 days ago.

Status:
Needs Feedback
Priority:
Must have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Start date:
2018-10-24
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
medium
Is Regression:
Sprint Focus:

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.


Related issues

Related to TYPO3 Core - Bug #87454: Slug/URL segment - /1 is wrongly saved, when trying to set / on rootpage. New 2019-01-16
Related to TYPO3 Core - Bug #87884: Root page of page tree suddenly gets slug "/1" Closed 2019-03-11

History

#1 Updated by Georg Ringer about 1 year 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"?

#2 Updated by Ricky Mathew about 1 year 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.

#3 Updated by Stefanos Karasavvidis 10 months 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.

#4 Updated by Stig Nørgaard Færch 10 months 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

#5 Updated by Benni Mack 7 months ago

  • Target version changed from next-patchlevel to Candidate for patchlevel

#6 Updated by Riccardo De Contardi 7 months ago

  • Related to Bug #87454: Slug/URL segment - /1 is wrongly saved, when trying to set / on rootpage. added

#7 Updated by Riccardo De Contardi 7 months ago

  • Related to Bug #87884: Root page of page tree suddenly gets slug "/1" added

#8 Updated by Riccardo De Contardi 3 days ago

Has this one been solved with #87884 ?

Also available in: Atom PDF