Update: Use MooTools v1.2.x in Joomla! 1.5

Homepage > Home > Coding > Update: Use MooTools v1.2.x in Joomla! 1.5

Sun 06/07/2009

in Coding, Internet, JavaScript, PHP

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:

  1. Updated MooTools Core to 1.2.2 1.2.3 and MooTools More to 1.2.2.2 1.2.3.1
  2. Added .getValue() to the compatibility file
  3. Added .getSelected() to the compatibility file to fix some issues under IE
  4. Added Json support to the compatibility file
  5. Added window.onDomReady shortcut for DOM ready event
  6. Changed MY_Behavior::mootoolsFix(); to handle new MooTools files 
  7. Changed MY_Behavior::mootoolsFix(); to correctly render old tooltips format title::text for items with hasTip class (anyway, remember that classes to style the tooltip have changed!)
  8. 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)

No Related Posts

Tags: , ,

Leave a response, or trackback from your own site.

63 Responses to this post:

  • Upgrade Mootools to v1.2.x in Joomla! 1.5 :: Dwight Jack Diary says:
    Sun 06/07/2009 at 3:42 pm

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

    Reply
  • andersen says:
    Sat 06/20/2009 at 12:49 am

    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

    Reply
  • Dan says:
    Thu 07/02/2009 at 5:38 pm

    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 UTC

    Object doesn’t support this property or method, Line: 187, Char: 3, media/system/js/mootools-compat-111-121.js

    Reply
  • Dan says:
    Thu 07/02/2009 at 6:30 pm

    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!!! :) :)

    Reply
    • Dwight Jack says:
      Thu 07/02/2009 at 8:50 pm

      Hi,
      you may exclude the hack from the fronpage by placing the hack code inside this if code:

      $menu = &JSite::getMenu();
      if ($menu->getActive() != $menu->getDefault()) {
      JLoader::import( 'my_libs.behavior' );
      MY_Behavior::mootoolsFix();
      }

      This way when the active menu will be the default one (so you are in the homepage) the hack won’t be loaded.

      Anyway it’ll be nice if you can provide me with a link to the page so that i can try to fix the error :)

      Reply
  • Dan says:
    Thu 07/02/2009 at 9:14 pm

    Sure! It’s currently under developemnt: http://www.kiinga.com

    Reply
  • Dan says:
    Thu 07/02/2009 at 9:29 pm

    Can I put some code under:

    isContentEdit() && $this->countModules(‘ja-slideshow’)){ ?>

    Reply
    • Dwight Jack says:
      Thu 07/02/2009 at 10:07 pm

      Well, i think that if you wanna prevent it to load with ja-slideshow you’ll have to put it in this code:

      if (! $this->countModules('ja-slideshow')) {
      // here the hack
      }

      Anyway, i’ve looked at the problem, but im unsure where the issue is. I’ll try to analyze it deeper in the next days.
      Bye

      PS: nice project ;)

      Reply
  • Dan says:
    Thu 07/02/2009 at 10:25 pm

    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();
    // } ?>

    Reply
    • pcrew says:
      Sun 08/09/2009 at 5:14 am

      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!

      Reply
      • pcrew says:
        Sun 08/09/2009 at 5:15 am

        *seems like just inserting the codes would work from the looks of it.

        Reply
      • Dwight Jack says:
        Mon 08/10/2009 at 12:01 pm

        Hi,
        actually the hack works like this: Joomla stores all components and core JS needed in an array and plans to output it in the head template tag (< jdoc::include type=”head” />) . The hack just cycles the array before is rendered as HTML tags and substitutes every occurrence of the mootools files with the new version one.
        Of the two lines of code you quoted, the 1st loads a library which contains the substitution routines, the other just launches them.

        Reply
        • pcrew says:
          Mon 08/10/2009 at 4:08 pm

          ah i see.

          thanks dwight jack! i have applied your hack but have not make any changes regarding this ja-slideshow but it still works!

          weird maybe i am missing something but good thing is, it works now :)

          ps: see the result of it on my site :)

          Reply
  • Dan says:
    Thu 07/02/2009 at 10:30 pm

    Sorry, tags don’t work with your posting system. Your should try to implement some bbCode for people to paste code [code][/code]

    Reply
  • jamland says:
    Mon 07/20/2009 at 10:46 am

    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.

    Reply
  • jamland says:
    Mon 07/20/2009 at 10:51 am

    Sorry forgot to ask my question… How I can change it to Moo 1.2.3?

    Reply
    • Dwight Jack says:
      Thu 07/23/2009 at 10:19 pm

      Thanx for the feedback.
      To answer (with another question) to your previous comment: is your installation in a subfolder?

      To answer to your Mootools version question: if you take a look to the mootoolsFix class method, you’ll see that it points to Mootools JS files. Just download new Mootools library files and change the PHP code to point to the right file names.
      If no major changes are made to the framework, i wouldn’t have any problem.
      Anyway im planning to release an updated version of the class.

      bye!

      Reply
      • jamland says:
        Mon 07/27/2009 at 2:24 pm

        Sorry I was not correct.
        I find my problem with trying stop loading Mootools1.1. I am very-very new with PHP so your code for me is hard. I will try with it more but for now I did some changes with mootools function in /Joomla/libraries/joomla/html/html/behavior.php:
        global $mainframe;
        if ($debug || $konkcheck) {

        JHTML::script(‘mootools-uncompressed.js’, ‘media/system/js/’, false);

        }
        elseif ($mainframe->isSite()) {

        JHTML::script(‘mootools-1.2.2-core.js’, ‘media/system/js/’, false);
        JHTML::script(‘mootools-1.2.2.2-more.js’, ‘media/system/js/’, false);
        JHTML::script(‘mootools-compat-111-121.js’, ‘media/system/js/’, false);
        JHTML::script(‘switcher.js’, ‘media/system/js/’, false);
        JHTML::script(‘validate.js’, ‘media/system/js/’, false);

        //Otherwise, use the stable 1.11
        }else{
        JHTML::script(‘mootools.js’, ‘media/system/js/’, false);

        }
        $loaded = true;
        return;

        That’s what I found by googling. I know it’s not best manner but…
        Thanks for your feedback I’ll try with mootools1.2.3.

        Reply
  • James says:
    Mon 07/20/2009 at 6:20 pm

    Thanks for this patch. I`m going to test it and i post again. But still thank you.

    Reply
  • Barry Roggeveen says:
    Sun 07/26/2009 at 2:27 pm

    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

    Reply
    • Dwight Jack says:
      Mon 08/10/2009 at 12:06 pm

      Hi,
      seems like your are having some problems with a missing Joomla core library. It’s located in /libraries/joomla/html/html/behavior.php
      check if the file exists and it’s not empty

      Reply
  • notbanksy says:
    Mon 08/10/2009 at 9:49 am

    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 :)

    Reply
  • notbanksy says:
    Mon 08/10/2009 at 11:20 am

    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 file

    then 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!

    Reply
  • notbanksy says:
    Mon 08/10/2009 at 11:21 am

    meh
    the code to remove is
    < jdoc::include type=”head” />

    Reply
    • Dwight Jack says:
      Mon 08/10/2009 at 12:17 pm

      Well no,
      if you’are removing the head tag from Joomla, you’re loosing also all the meta tags and external CSS. You’d better investigate why you script is not working (you can send me a link, if u want, so i can help you).
      bye!

      Reply
  • pcrew says:
    Tue 08/11/2009 at 5:46 am

    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

    Reply
  • Bill says:
    Wed 08/19/2009 at 2:20 pm

    This is just what I needed. I will detail any issues I come across if any.

    Thanks.

    Reply
    • Bill says:
      Wed 09/09/2009 at 1:22 pm

      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.

      Reply
  • jakobe says:
    Wed 09/09/2009 at 12:10 am

    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.js

    Message: 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.js

    Ideally 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?

    Reply
    • Dwight Jack says:
      Sun 09/20/2009 at 3:07 pm

      Hi. Many methods with same name have changed a lot from 1.11 to 1.2x .getSize() now returns an object with ‘x’ and ‘y’ keys only while in 1.11 was different. I should see a live example to digg the problem though.

      Reply
  • Clone says:
    Tue 09/15/2009 at 7:33 pm

    Not working for me at all… getting the error:

    this.setOptions is not a function
    in modal.js

    Reply
    • Dwight Jack says:
      Sun 09/20/2009 at 3:09 pm

      That’s because the script should load an updated version of modal.js which is included in my package. Try downloading the latest version and see if it works.

      Reply
  • oppo GOP says:
    Tue 09/15/2009 at 10:33 pm

    It lunacy developers JOOMLA —
    make forced users to download large mootools!!
    There is a much better script Jquery – easier and more convenient

    Reply
    • Dwight Jack says:
      Sat 09/19/2009 at 12:14 pm

      Honestly im a jQuery fan 2, but since Joomla’s core JS Framework is MooTools and right now u need it ’cause is largely used from templates, modules and components. I think that loading jQuery 2 would result in a performance issue :)

      Reply
  • Bill says:
    Fri 10/23/2009 at 1:26 pm

    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.

    Reply
  • EDark says:
    Fri 10/30/2009 at 1:14 pm

    Hi all! There are errors in the Chronoforms.

    Reply
  • EDark says:
    Sun 11/01/2009 at 2:22 pm

    error in com_contact in ie 5.5 =) this.ownerDocument.window is null (core)

    Reply
  • mootools says:
    Fri 11/06/2009 at 9:19 pm

    This is what I needed.Thanks.

    Reply
  • Jim Mooney says:
    Thu 12/31/2009 at 3:38 am

    I tried this but the top menus in the back end no longer work. Am I missing something?

    Reply
  • Jim Mooney says:
    Wed 01/06/2010 at 8:28 pm

    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.

    Reply
  • Piotr_cz says:
    Thu 01/07/2010 at 12:34 pm

    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

    Reply
  • Slashmaster says:
    Sun 01/24/2010 at 10:46 pm

    Nice Work. Helped me a lot with MooScroll :)

    Reply
  • koyan says:
    Mon 01/25/2010 at 10:06 am

    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 )) {

    Reply
  • Suli3 says:
    Wed 02/17/2010 at 8:18 pm

    hi

    Is there a upgrade with mootools 1.2.4 planed?

    Reply
  • Danila says:
    Sat 02/20/2010 at 10:50 pm

    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?)

    Reply
  • Danila says:
    Sat 02/20/2010 at 10:51 pm

    - 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

    Reply
    • Dwight Jack says:
      Sat 03/27/2010 at 2:50 pm

      Well usually you can leave the more.js file, since it’s a collection of plugins.

      Reply
      • Danila says:
        Sat 03/27/2010 at 9:21 pm

        What about the others?
        - media/system/js/mootools-1.2.3-core.js
        - media/system/js/mootools-compat-111-12.js

        Is the usage of mootools-1.2.3-core.js mandatory? Or can I use mootools-compat-111-12.js instead of mootools-1.2.3-core.js?

        Reply
  • mihazu says:
    Fri 05/21/2010 at 2:11 pm

    yes! great – good job! thanx a lot. i spent 2 nights by fixing joomla mootools with my 1.2 core script for my site, this works great, done in 5 minutes….

    Reply
  • Alex says:
    Thu 07/22/2010 at 8:10 pm

    “Mootools 1.2.4 Upgrage Plugin” is available in Joomla 1.5.19+
    If you do clean installation only thing to do is to enabled the plugin. However if you update Joomla to the latest version plugin will not be installed in database. You can find information on how to add the “Mootools 1.2.4 Upgrade Plug-in” to Joomla after update in this article

    Reply
  • Mootools upgrade in Joomla 1.5 | |Van der Sluijs .NLVan der Sluijs .NL says:
    Fri 02/25/2011 at 10:53 am

    [...] Jack Gebruik Mootools 1.2 in Joomla 1.5 Upgrade Mootools naar 1.2 in Joomla 1.5 VN:F [1.9.7_1111]please wait…Rating: 7.0/10 (1 [...]

    Reply
Leave a Reply ()

You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

* required.