[!!!][TASK] Allow New Content Element override with custom module
[Packages/TYPO3.CMS.git] / typo3 / sysext / core / Documentation / Changelog / master / Breaking-70055-OverrideNewContentElementWizardViaPageTSconfig.rst
1 ========================================================================
2 Breaking: #70055 - Override New Content Element Wizard via page TSconfig
3 ========================================================================
4
5 Description
6 ===========
7
8 In the past it was possible to override the "New Content Element Wizard" via custom scripts
9 when using page TSconfig via ``mod.web_list.newContentWiz.overrideWithExtension = myextension`` to define an extension,
10 which then needed a file placed under ``mod1/db_new_content_el.php``. The script was then called with certain parameters instead
11 of the wizard.
12
13 The new way of handling entry-points and custom scripts is now built via modules and routes. The former option
14 ``mod.web_list.newContentWiz.overrideWithExtension`` has been removed and a new option
15 ``mod.newContentElementWizard.override`` was introduced instead. Instead of setting the option to a certain extension key,
16 a custom module or route has to be specified.
17
18 Example:
19
20 .. code-block:: typoscript
21
22 mod.newContentElementWizard.override = my_custom_module
23
24
25 Impact
26 ======
27
28 Using the old TSconfig option ``mod.web_list.newContentWiz.overrideWithExtension`` has no effect anymore and
29 will fallback to the regular new content element wizard provided by the TYPO3 Core.
30
31
32 Affected Installations
33 ======================
34
35 Any installation using this option with extensions providing custom New Content Element Wizards, e.g. templavoila.
36
37
38 Migration
39 =========
40
41 The extension providing the script must be changed to register a route or module and set the TSconfig option to the route identifier,
42 instead of a raw PHP script. Any usages in TSconfig need to be adapted to use the new TSconfig option.