Bug #87369

Slug generation does not work for readonly fields

Added by Michael Grundkötter 2 months ago. Updated 2 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2019-01-08
Due date:
% Done:

0%

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

Description

When configuring a TCA type "slug", using a "field" in "generatorOptipons" with readOnly=true set in TCA, this field is not used/skipped in the slug generation process.
E.g. this TCA

'title' => [
     'exclude' => true,
     'label' => 'LLL:EXT:xyz/Resources/Private/Language/locallang_db.xlf:tx_xyz_domain_model_offer.title',
     'config' => [
         'type' => 'input',
         'size' => 30,
         'eval' => 'trim,required'
     ],
],
'webcode' => [
   'exclude' => true,
   'label' => 'LLL:EXT:xyz/Resources/Private/Language/locallang_db.xlf:tx_xyz_domain_model_offer.webcode',
   'config' => [
       'type' => 'input',
       'readOnly' => true,
       'size' => 4,
       'eval' => 'unique,int',
       'range' => [
           'lower' => 1000,
           'upper' => 9999
       ]
   ],
],
'slug' => [
   'exclude' => true,
   'label' => 'LLL:EXT:xyz/Resources/Private/Language/locallang_db.xlf:tx_xyz_domain_model_offer.slug',
   'config' => [
       'type' => 'slug',
       'fallbackCharacter' => '-',
       'size' => 50,
       'eval' => 'uniqueInSite',
       'generatorOptions' => [
           'fields' => ['title', 'webcode'],
           'fieldSeparator' => '-',
           'prependSlash' => true,
           'prefixParentPageSlug' => true,
           'replacements' => [
               '/' => '',
           ],
       ]
   ],
],

The title field is used correctly, the webcode field is skipped. When I remove the readonly flag on webcode, the slug is generated correctly.

History

#1 Updated by Benjamin Gries Gries 2 months ago

I can confirm this. The value of the input field can't be read in SlugElement.js, because the readOnly option adds a disabled attribute instead of a readonly attribute to the input field. This has potentially an influence to all input fields where the readOnly option is used.

#2 Updated by Benjamin Gries Gries 2 months ago

  • Category set to Link Handling, Site Handling & Routing

Also available in: Atom PDF