Bug #71618
closedExtension manager does not work properly due to JS error
100%
Description
Due to noconflict-mode enabled for jQuery, the jquery plugins (validate, expander, loadmask) fail to find the jQuery object.
This subsequently causes the initialization code in EM's Main.js file to fail ultimately killing any functionality initialized after those plugin usages, for instance, "update now" button for TER extlist refresh.
In general we face a shortcomming of our API, which offers no way to add jquery plugins before the call to noConflict.
A possible solution would be to load jquery without the noconflict-mode in EM. This would currently only be possible if the call in ModuleTemplate.php is changed to
$this->pageRenderer->loadJquery(null, null, PageRenderer::JQUERY_NAMESPACE_NONE);
AND the additional loadJQuery="true" attribute of the <f:be.pageRenderer> VH in the main layout of EM is rmeoved (otherwise jquery would be loaded twice).
Another solution would be to extend the API to allow to register jQuery-Plugins, which are then added right after the jQuery script tag, but before the call to noConflict(true).