Breaking: #39721 - Prototype.js and Scriptaculous removed ¶
See Issue #39721
Any TYPO3 Extension that uses prototype.js or scriptaculous for usage in the Backend or Frontend will not work anymore.
The TypoScript properties
have been removed
and have no effect anymore, leading to not including prototype in websites where this TypoScript option is set.
This might lead to broken websites when updating.
The shipped Fluid ViewHelper for backend modules does no longer have the according properties anymore and will throw a fatal error:
<f:be.container loadPrototype="false" loadScriptaculous="false" scriptaculousModule="someModule,someOtherModule">
Using the PageRenderer directly in any module, and calling one of the related methods will result in a fatal error.
PageRenderer->setPrototypePath() PageRenderer->setScriptaculousPath() PageRenderer->getPrototypePath() PageRenderer->getScriptaculousPath() PageRenderer->loadPrototype() PageRenderer->loadScriptaculous()
Affected Installations ¶
Instances that use prototype.js or scriptaculous in the Frontend.
Instances with third-party extensions that
require these libraries or set one of the options in the mentioned ViewHelper.
Instances that use the PageRenderer API directly and use on of the methods above.
The preferred substitution is jQuery and RequireJS that are loaded by default in any TYPO3 Backend module, if any third-party code is needed based on prototype and/or scriptaculous. Alternatively, it is possible to ship a separate prototype.js and scriptaculous library in a third-party extension if no migration is possible with jQuery.