Breaking: #70055 - Override New Content Element Wizard via page TSConfig¶
See Issue #70055
In the past it was possible to override the “New Content Element Wizard” via custom scripts
when using page TSConfig via
mod.web_list.newContentWiz.overrideWithExtension = myextension to define an extension,
which then needed a file placed under
mod1/db_new_content_el.php. The script was then called with certain parameters instead
of the wizard.
The new way of handling entry-points and custom scripts is now built via modules and routes. The former option
mod.web_list.newContentWiz.overrideWithExtension has been removed and a new option
mod.newContentElementWizard.override has been introduced instead. Instead of setting the option to a certain extension key,
a custom module or route has to be specified.
mod.newContentElementWizard.override = my_custom_module
Using the old TSConfig option
mod.web_list.newContentWiz.overrideWithExtension has no effect anymore and
will fallback to the regular new content element wizard provided by the TYPO3 Core.
Any installation using this option with extensions providing custom New Content Element Wizards, e.g. templavoila.
The extension providing the script must be changed to register a route or module and set the TSConfig option to the route identifier, instead of a raw PHP script. Any usages in TSConfig need to be adapted to use the new TSConfig option.