#104673TCA type slug field not generated correctly for new record with generatorOptions in columnsOverrides
Description
The scenario is we have a slug field defined, but the generatorOptions are to be found in types/columnsOverrides section.
This is already handled in FormSlugAjaxController, however for NEW records, this does not work because it relies on the existence of the db row.
A fix would be to provide the record type already in the ajax request, which should be known by FormEngine at this point.
Reviews 3
Related issues 1
History 812
-
Garvin Hicking changed category <span data-processor="relativetime" data-value="2024-08-20T17:12:45+00:00" > 08/20/24, 17:12 </span>
-
Benjamin Franzke changed status
NewAccepted <span data-processor="relativetime" data-value="2024-10-07T13:40:29+00:00" > 10/07/24, 13:40 </span> -
Benni Mack changed Related to #101435 <span data-processor="relativetime" data-value="2025-04-22T10:04:00+00:00" > 04/22/25, 10:04 </span>
-
Benni Mack changed Sprint Focus On Location Sprint <span data-processor="relativetime" data-value="2026-08-06T16:02:24+00:00" > 08/06/26, 16:02 </span>
-
Oliver Bartsch commented <span data-processor="relativetime" data-value="2026-11-05T08:07:14+00:00" > 11/05/26, 08:07 </span>
Hey,
thanks. I now pushed a patch for this.
FormSlugAjaxController::suggestAction()worked out the record type only from the database row to apply the “columnsOverrides” of the slug field. For a new record the uid is “NEW…”, so there is no row, the type cannot be determined and the proposal was generated with the base “generatorOptions”. FormEngine, however, renders the slug element with the overridden configuration, e.g. listening on different fields.InputSlugElementnow passes the record type FormEngine already resolved (recordTypeValue) through the slug JavaScript module to the AJAX request.Cheers, Oli
-
Gerrit Code Review pushed patch set 1 for main to change 97355 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2026-11-05T08:07:29+00:00" > 11/05/26, 08:07 </span> -
Gerrit Code Review pushed patch set 2 for main to change 97355 <span data-processor="relativetime" data-value="2026-11-05T10:00:07+00:00" > 11/05/26, 10:00 </span>
-
Oliver Bartsch commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-11-05T10:20:10+00:00" > 11/05/26, 10:20 </span>Applied in changeset commit:a9724bf5e79e2aa9ed2348c64630c2273c9d9820.
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 97370 status
ResolvedUnder Review <span data-processor="relativetime" data-value="2026-11-05T11:02:14+00:00" > 11/05/26, 11:02 </span> -
Gerrit Code Review pushed patch set 2 for 14.3 to change 97370 <span data-processor="relativetime" data-value="2026-11-05T13:10:53+00:00" > 11/05/26, 13:10 </span>
-
Oliver Bartsch commented and changed status
Under ReviewResolved <span data-processor="relativetime" data-value="2026-11-06T08:05:10+00:00" > 11/06/26, 08:05 </span>Applied in changeset commit:84c826be8d3d174dab34092ad43c57619c9c869d.
Slughandling DataHandler / FormEngine has more caveats related to slug generation/sanitzation.
Stumpeled over that (DH / functional tests) while refactoring https://review.typo3.org/c/Packages/TYPO3.CMS/+/85574
and testing / debugging through the DataHandler->processDataMap() step to test/verify the
change (and changes for the change).