Issue Bug New Stale

#88890URL segments (slugs) of translated pages should be autogenerated

S P 08/02/19, 15:04 updated 06/11/26, 08:11

Description

When creating a new page and not set a slug it gets autogenerated.

But when translating a page the slug gets pre-filled with “translate-to-target-language-original-title” and thus is not auto-generated with the real title on saving.

The slug field should initially be empty on a newly translated page record. Since v14 this is ven more serious, because this overlay translation wizard does not even allow to change the title…

This is
  1. big nuisance for non-technical editors in large envorinments. The UX can be improved here by emptying the slug initially to trigger the auto-filling when no slug is entered manually.
  2. more an just an annoyance when doing automatic translations (see comments)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] URL segments (slugs) of translated pages should be autogenerated Resolves: #88890 Releases: main

History 7

  1. Jo Hasenau commented <span data-processor="relativetime" data-value="2020-11-11T15:13:20+00:00" > 11/11/20, 15:13 </span>

    Actually this is a bit more than just nuisance as soon as you are going to automatically translate pages and/or other tables containing slug fields.

    The problem is the same, but it does not get noticed.

    So after the import of properly translated L10nmgr XML files containing properly translated titles, the slug fields of those translated records still contain “translate-to-language-original-language-title” as a value.
    Since there is nobody actively editing those records, those slug values will be taken as is and provide wrong paths for each language other than default.

  2. Jo Hasenau changed subject URL segments (slugs) of translated pages must be updated manually (UX flaw) URL segments (slugs) of translated pages must be updated manually <span data-processor="relativetime" data-value="2020-11-11T15:13:47+00:00" > 11/11/20, 15:13 </span>

  3. Jo Hasenau changed subject URL segments (slugs) of translated pages must be updated manually URL segments (slugs) of translated pages should be autogenerated <span data-processor="relativetime" data-value="2023-08-03T21:44:30+00:00" > 08/03/23, 21:44 </span>

  4. S P commented and changed TYPO3 Version 9 12 <span data-processor="relativetime" data-value="2024-12-16T11:01:36+00:00" > 12/16/24, 11:01 </span>

    Still valid in v12 and AFAIK no configuration for this.

  5. S P commented and changed TYPO3 Version 12 13 <span data-processor="relativetime" data-value="2024-12-19T08:49:51+00:00" > 12/19/24, 08:49 </span>

    This behaviour is still in v13.

  6. S P commented and changed description TYPO3 Version 13 14 <span data-processor="relativetime" data-value="2026-06-11T08:11:24+00:00" > 06/11/26, 08:11 </span>

    Still valid on v14. And I think it got even worse, because now you have this wizard that let’s you not even change the title first. You just get a dummy-“localized” record and have to think of so many details to get the localisation right (click through wizard, open the “localized” record, change title, recreate slug, all in correct order).