Since i’ve fixed some bugs and issues on the files to switch core MooTools v1.11 to v1.2.x and following the release of version 1.2.2 1.2.3 of MooTools Core and More, i’m posting here an updated version of this workaround to which you could refer for details on how this code works.
Changes in this new version are:
- Updated MooTools Core to 1.2.2 1.2.3 and MooTools More to 1.2.2.2 1.2.3.1
- Added
.getValue()to the compatibility file - Added
.getSelected()to the compatibility file to fix some issues under IE - Added
Jsonsupport to the compatibility file - Added
window.onDomReadyshortcut for DOM ready event - Changed
MY_Behavior::mootoolsFix();to handle new MooTools files - Changed
MY_Behavior::mootoolsFix();to correctly render old tooltips formattitle::textfor items withhasTipclass (anyway, remember that classes to style the tooltip have changed!) - Added a validate.js replacement to fix an issue with changed namespaces. ( this replacement is no more needed)
The source code is released in the form of patch: unzip it and upload files in your Joomla root, eventually overwriting files. MooTools library is uncompressed to allow for a quicker debug. Anyway you may minify it with your tool of choice.
Here is the code: Mootools 1.11 to 1.2.2 (71.68 KB)
Update (again): Sometimes i can’t get if MooTools team is too vital or library milestones are not well defined… anyway here is an update to use latest MooTools 1.2.3. No major changes have been made to the fix library, anyway keep reporting compatibility issues. Here is the zipped file: Mootools 1.11 to 1.2.3 for Joomla 1.5 (72.06 KB)
Update (09/20/09): New version available. Corrected some bugs in the compatibility file and added a loop check to replace MooTools 1.11 when called from a component as custom script. Now the validation core script doesn’t need to be replaced. Get source here (carries the original validate.js as in Joomla 1.5.14: MooTools 1.11 to 1.2.x (72.88 KB)
Tags: joomla, Joomla 1.5, Mootools
58 Responses to this post:
-
great fix! i have set to false for now since lord knows when you’ll ((if you’ll check 8-))
it prevents the error in IE 7.
BUT, will not load subsequent MODS ((on interior site pages)
they pretend they are loading 8-)!
any suggestion appreciated.
thanks for the excellent workaround
-
The hack works great with my Highslide and AllVideos Reloaded plgs but I’m having a problem with my mod_jaslideshow on the frontpage. IE throws me an error on the page:
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Timestamp: Thu, 2 Jul 2009 16:37:38 UTCObject doesn’t support this property or method, Line: 187, Char: 3, media/system/js/mootools-compat-111-121.js
-
I only use the mod_jaslideshow on the frontpage. Can I exclude mod_jaslideshow from the hack? how do i do that?
OR
Can I switch library right on my template’s index.php module call:
PLEASE HELP!!!
-
Sure! It’s currently under developemnt: http://www.kiinga.com
-
Can I put some code under:
isContentEdit() && $this->countModules(‘ja-slideshow’)){ ?>
-
You are a genius! I added the hack as a separate argument right before calling the module and it worked!
Thanks a lot for your extremely quick response and thank you for your compliments on the site. Here’s the code I implemented:
// countModules(‘ja-slideshow’)) {
// JLoader::import( ‘my_libs.behavior’ );
// MY_Behavior::mootoolsFix();
// } ?>-
Dan,
I am using jaslideshow as well. I kinda understand that these hacks you are having are on index.php but I am confused how does it work?
doesn’t this mootools hacks by dwight jack upgrade our Joomla 1.5 mootool?
seems like just inserting
//Jloader:: import(‘my_libs.behavior’);
//MY_Behavior:mootoolsFix();from the looks of it.
Please advise and thanks!
-
*seems like just inserting the codes would work from the looks of it.
-
-
-
Sorry, tags don’t work with your posting system. Your should try to implement some bbCode for people to paste code [code][/code]
-
Thanx, that’s exactly what I need. I also did changes in /libraries/joomla/html/html/behavior.php to prevent default mootools1.1 loading. Don’t know why but it’s doesn’t want load mootools1.2 without it.
-
Sorry forgot to ask my question… How I can change it to Moo 1.2.3?
-
Thanks for this patch. I`m going to test it and i post again. But still thank you.
-
I just did the fix on my site, but now I get an error on the frontpage syaing:
JHTMLBehavior::caption not found in file.
JHTMLBehavior::mootools not found in file.and on the backend I get:
JHTMLBehavior::mootools not found in file.
JHTMLBehavior::mootools not found in file.
JHTMLBehavior::tooltip not found in file.Did I miss something? Please help and thanks in advance.
Barry
-
I’m using this method as defined for moo 1.2.1 as this is the version I’ve been working with for my menu script.
I’m checking the page in firebug, and apparently, all the js is loading. Moo 1.11 and moo 1.2.1 – is this right? Needless to say, my menu doesn’t work, but the joomla backend does.
Any advice much appreciated
-
Ok – I’ve figured it out. If anyone else can’t get it to work, try this:
Remove this bit of code from your template’s index.php filethen manually add the mootools.js and any css for your page.
The back end will still work because it doesn’t use your template, so it will load moo 1.11. Easy! -
meh
the code to remove is
< jdoc::include type=”head” /> -
hi all,
my site works fine with existing js except for this specific component SIMgallery:
so inside index.php above
make it half workings and there is still some errors which I couldn't solve by my own.
the dev claims the typical issue raised bcoz of SIMgallery is using Mootools 1.2. Using this hack I managed to get it works on some parts, while others part remain problematic.
thanks for the concern and please advise.
http://forum.joomla.org/viewtopic.php?f=471&t=427770&p=1805759#p1805759
-
I meant above
-
-
This is just what I needed. I will detail any issues I come across if any.
Thanks.
-
I get..
Window.onDomReady(function(){
126 document.formvalidator.setHandler(‘passverify’, function (value) { return ($(‘password’).value == value); } );
127 });This occurs when I load my home page while not logged in. It seems to be getting thrown from com_user registration which is currently my default front page. The site is not live. Registration seems to be working fine though.
-
-
I have applied this to my joomla 1.5.14 and RT template affinity 1.5.5
the purpose was to get SimGallery to work..and although SimGallery does now work ..anything form the template that used mootools does not.
and shadwobox is not loading either
and also in IE I now get a error overflow stack at line 77
and these errors
Message: ‘getSize().size.x’ is null or not an object
Line: 150
Char: 48
Code: 0
URI: http://www.stripperhq.com/media/system/js/mootools-1.2.3-core.jsMessage: Object doesn’t support this property or method
Line: 2908
Char: 3
Code: 0
URI: http://www.stripperhq.com/media/system/js/mootools-1.2.3-core.jsIdeally I just need the SimGallery to load the newest version or at least 1.2 version of mootools, I need the rest of the site to rely on 1.11 or 1.14 or what it was orgianly using…..is this possible?
the developer at SimGallery doesnt really seem to have any answers for me, and neither does RT
suggestions?
-
Not working for me at all… getting the error:
this.setOptions is not a function
in modal.js -
It lunacy developers JOOMLA —
make forced users to download large mootools!!
There is a much better script Jquery – easier and more convenient -
There are some new features in Mootools 1.2.4 that I would like to use. I am going to load the latest version and report any issues with Joomla 1.5.14.
-
Hi all! There are errors in the Chronoforms.
-
error in com_contact in ie 5.5 =) this.ownerDocument.window is null (core)
-
This is what I needed.Thanks.
-
I tried this but the top menus in the back end no longer work. Am I missing something?
-
Is there a reason you need it on the backend? I just use it on the front end. All of my components that would use Mootools 1.2 are on the front end.
-
-
I didn’t use it for the backend on purpose. I must be doing something wrong. Anyway, I decided to use Dojo until Joomla 1.6 comes out. Dojo seems to do everything with no conflicts and works well in all IE browsers. I tried some other frameworks and had problems with some things not working in IE 7, or conflicts with the resident MooTools.
-
There’s a problem with loading TinyMCE configuration script in the frontend (it’s being stripped). To add an exclusion, change behaviur.php @Line 18 to
if ((preg_match('/src="([^"]*)"/',$script,$matches)) && (preg_match('tinyMCE.init',$script,$matches))) {
thanks Dwight Jack for your work!
btw Joomla 1.5.16 is supposed to have an option in admin to load MooTools 1.1.x or 1.2.x
-
well, the code works but actuall it’s supposed to be:
if ((preg_match('/src="([^"]*)"/',$script,$matches)) && !(strpos($script,'tinyMCE.init' ))) {
-
-
Nice Work. Helped me a lot with MooScroll
-
I had to change the line 29 in the beheaviour.php to the following:
if ((strpos($script,'mootools.js') !== false ) || (strpos($script,'mootools-uncompressed.js') !== false )) {
-
hi
Is there a upgrade with mootools 1.2.4 planed?
-
Hi! First of all thank you very much for this nice hack. It helped me much with allvideos reloaded.
By the way I would like to ask you if I have to load all these three javascript files (if not, which one will do the best work and which can I remove?)
-
- media/system/js/mootools-1.2.3-core.js
- media/system/js/mootools-1.2.3.1-more.js
- media/system/js/mootools-compat-111-12.js

[...] Update: A new version of files presented in this post is available here! [...]