[#5249] - Force loading MooTools in backend for B/C
- Closed
- 29 Nov 2014
- Medium
- Build: staging
- # 5249
- Diff
- smz:ForceLoadingMooTools
- Success The Travis CI build passed Details
User tests: Successful: Unsuccessful:
As we often do not load MooTools for our own needs, here we force the loading of it for B/C with 3rd party extensions back-end
jissues-bot
- | Labels |
Added:
?
|
||
Why should we load Mootools everywhere??
In fact this would cause serious B/C issues for extensions nos using Mootools.
@phproberto Actually I'm of the "this is not a B/C issue" school, but in case, how can we know if a 3rd party extension is relying on MooTools? Why do you think this will break other extensions?
There are only a handful of places in core that would need to load Mootools to support extensions. com_installer is one of them. IMO, there's no need to load it as part of both templates.
Agree with loading in com_installer indeed
@mbabker Agreed.... this was only to keep "on the safe side of things" and I think it would cause big performance isssues, once MooTools is cached locally, unless @phproberto is right and this is causing other B/C issues...
We can load mootools in layout/toolbar/base which covers most cases and is also overridable. Sorry NO to this one!
OK, got it! closing this! 
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-11-29 16:57:21 |
This fixes (amongst other possible situations) the issue raised in #5239