Feature #87085

Slug generator option fields should respect list of field definitions as fallback (nav_title // title)

Added by Joerg Boesche about 2 months ago. Updated 7 days ago.

Status:
Under Review
Priority:
Must have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
Start date:
2018-12-05
Due date:
% Done:

0%

PHP Version:
7.2
Tags:
routing, pages
Complexity:
Sprint Focus:

Description

The slug generator option still uses the field "title" to generate the slug. It is not possible to define a list of fields "nav_title // title", as we know from TypoScript.

In case of SEO optimizations and the daily work of an editor, it should be possible to define a list of fields in the slug configuration.
An editor creates a new page and fills up the title and nav title. Actually the title is used to generate the slug. The behavior should be configurable with the "TCA columnsOverrides" mechanism.

TCA Example

'columns' => [
                'slug' => [
                    'config' => [
                        'generatorOptions' => [
                            'fields' => ['nav_title // title']
                        ]
                    ]
                ],

Example with defined nav_title:
Page-Title: Best summer deals
Navigation Title: Summer deals
Slug: /summer-deals (nav_title)
Slug-behavior: nav_title (is not empty) // title

Example with undefined nav_title, but title:
Page-Title: Best summer deals
Navigation Title: Summer deals
Slug: /best-summer-deals (title)
Slug-behavior: nav_title (is empty, fallback to title) // title

History

#1 Updated by Joerg Boesche about 2 months ago

Additional information:
Handling in old realurl extension for pathsegment generation:

'segTitleFieldList' => 'alias,tx_realurl_pathsegment,nav_title,title'

#2 Updated by Gerrit Code Review about 1 month ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59167

#3 Updated by Gerrit Code Review about 1 month ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59167

#4 Updated by Guido Schmechel about 1 month ago

Using of // is a good direction. Integrators know this convention. Already now you can specify a comma separated list, see RST file. But this simply combines the fields.

#5 Updated by Gerrit Code Review about 1 month ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59167

#6 Updated by Gerrit Code Review about 1 month ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59167

#7 Updated by Gerrit Code Review about 1 month ago

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59167

#8 Updated by Gerrit Code Review about 1 month ago

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59167

#9 Updated by Gerrit Code Review 12 days ago

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59167

#10 Updated by Gerrit Code Review 9 days ago

Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59167

#11 Updated by Gerrit Code Review 7 days ago

Patch set 9 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59167

Also available in: Atom PDF