Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Try Vanilla Forums Cloud product

Ready to contribute?

Amazing! Sign our contributors' agreement and then join us on GitHub.

Update for critical security issue in PHPMailer included in release Vanilla 2.3.1
Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.


This discussion is related to the Mootools addon.


  • Uploaded version 1.1 of Mootools.
  • Uploaded version 1.2 of Mootools.
  • Uploaded version 1.2 of Mootools.
  • Uploaded version 1.3 of Mootools.
  • As of 1.3 is compatible with SmoothPageJump and fixes problems on the Settings > Roles/Categories.
  • Uploaded version 1.4 of Mootools.
  • Question: you say "The script will handle any and all dependencies so you only have to list the bare minimum components." Exactly how? Do I need to specify which ones I need in reverse order (from the mootools download list)? I've got an addon that uses Fx.Slide, Window.DomReady, and Element.Selectors. Those are the minimums. Everything else is added (to the download list) thats required after selecting those. I tried that and couldn't get it to work, tried adding a couple extras too just in case, still didn't work. The only thing I didn't add was core, class, and native.

  • It takes a page refresh for Mootools to force itself to the top of the extension list. Other than that I can't see what would be the problem. If you only need Fx.Slide, Window.DomReady and Element.Selectors then all you need to do is call:
    MT_AddComponent('Fx.Slide', 'Window.DomReady', 'Element.Selectors');
    All the dependencies will be added automatically. Also, it shouldn't matter which order you list them in.
  • Uploaded version 1.5 of Mootools.
  • Uploaded version 1.6 of Mootools.
  • Uploaded version 1.7 of Mootools.
  • It's much smaller as of 1.7 because I cut out all the cache files that were left over from testing. I've modified my build script so that it shouldn't happen again.
  • mootools.class.php still refers to the cache files.
  • It still uses them, yes. What I meant was that it was generating files and putting them in the cache while I was testing. When I built the extension, it copied those files into the extension archive so it had a bunch of unnecessary files that were using up space.
  • then why am I getting this:

    Warning: fopen(/path/to/vanilla/extensions/Mootools/cache/ca036f01dda60efb1edcb6f8cf8400e7): failed to open stream: No such file or directory in /path/to/vanilla/extensions/Mootools/mootools.class.php on line 82

    Warning: fwrite(): supplied argument is not a valid stream resource in /path/to/vanilla/extensions/Mootools/mootools.class.php on line 83

    Warning: fclose(): supplied argument is not a valid stream resource in /path/to/vanilla/extensions/Mootools/mootools.class.php on line 84

    last minute thought:
    does the cache folder need to be writable? I don't think the download came with an empty cache folder


    yea that fixes it .. I don't know that I did that for any of the previous versions ... oops

    now the collapsible panel works, except that there isn't a (+) / (-) icon, but when you click on the title of a panel, it collapses or re-expands.
  • Yup, I ran into your above error when I did a local install. I've added a section to the readme about making the cache folder writeable now.

    I don't think Collapsible Panel ever had [+] or [-] icons. Might add it to the to-do list though although it might inhibit support for other themes.
  • Oh, i saw when it uploaded add.png, and I thought it was for the (+) / (-) button, but now I see that it's for settings -> configure collapsible panel -> exceptions. my bad. it's good without (+) / (-) icons, I just thought it was something going wrong on my install.

    overall excellent extension --- now that I got it working; lol. (it was probably the cache issue all along)
  • Heh, I'm really glad to finally be rid of that bug. Ø had had it for ages and I spent so long trying to fix it. The worst part is that, in order to fix the bug, I had to type one extra character... an '&' to be specific. The problem is that I think you're using PHP 4 and I was testing on a PHP 5 server which meant that objects behaved slightly differently. I was passing the $Head object by reference (as opposed to by value) throughout the Mootools class but I forgot to pass it by reference in the delegate function. That's ok for PHP 5 which passes objects by reference by default but for PHP 4 you have to explicitely tell PHP to do that.

    And as a bonus, I also found out why the extension was so huge (after going over the 198k limit). I cleared out the cache folder which unluckily caused your cache issue.

    I might get a rest now...
  • I'm just glad you aren't one of those programmers that throws some code out with infinity plus one errors and abandons it. Actually the lussumo community in general isn't that way.
  • Uploaded version 1.8 of Mootools.
  • Just to let you know... With this latest version everything seems to work: Live Discussions, Collapsible Panel, Yellow Fade... and even Smooth Page Jump!

    Thanks a lot for your hard work, you rock :)
  • After you updated it the issue I was having with my extension (Hidden Text 2) is now gone as well.
  • Hey, I have a tiny problem with something apparently related to Mootools. I've tweaked a bit Smooth Page Jump in order to enable it on the blog page created with BlogThis (I've just added 'extension.php' in the array) and it works.

    Thus Firebug gives me a strange error which seems to have something to do with a Mootools cached file. It looks like this:

    this.getStyle is not a functione("marginTop") each(function())prototype.lite.js (line 124) e("margin")ea7d055e4a28c35ad... (line 1) e("margin")ea7d055e4a28c35ad... (line 1) $each(["margin"], function(), undefined)ea7d055e4a28c35ad... (line 1) e(ul, "getStyle", ["margin"])ea7d055e4a28c35ad... (line 1) e()ea7d055e4a28c35ad... (line 1) e(ul, Object duration=500)ea7d055e4a28c35ad... (line 1) e()ea7d055e4a28c35ad... (line 1) e()ea7d055e4a28c35ad... (line 1) Start(h2)slidepanel.js (line 28) bind()prototype.lite.js (line 25) each(function())prototype.lite.js (line 124) Start()slidepanel.js (line 44) (no name)()slidepanel.js (line 59) e()ea7d055e4a28c35ad... (line 1) e(undefined)ea7d055e4a28c35ad... (line 1) e(function())ea7d055e4a28c35ad... (line 1) each(function())prototype.lite.js (line 124) e("domready", undefined, undefined)ea7d055e4a28c35ad... (line 1) e()ea7d055e4a28c35ad... (line 1) e()ea7d055e4a28c35ad... (line 1) e(DOMContentLoaded )ea7d055e4a28c35ad... (line 1) [Break on this error] eval(function(p,a,c,k,e,d){e=function(c){return(c<a?'':e(parseInt(c/a)))+((c=c%a... ea7d055e4a28c35ad... (line 1)

    Not really a problem since it works anyway, but this error keeps appearing. Maybe is it more related to Smooth Page Jump?
  • Could be. It did mention prototype.lite.js which is included by the Smooth Page Jump extension. Mootools is supposed to remove this and replace it with a Mootools version. I think Mootools is setup to remove those scripts if it's on the search or comments page. I think perhaps with BlogThis, Smooth Page Jump is being loaded on a different page. It should just be a matter of adding the new page to the if statement.

    @Krak: Yeah, I'm guessing Hidden Text 2 used a bit of javascript. If there are any errors with any of the javascript scripts then usually none of the rest will work either.
  • Any ideas why i would be getting a "there was a problem authenticating your post information" message when activating the extension?
  • Uhm nope, it's never been reported before. Are you only getting this error with this extension or are there others?
  • CommentLinks seems to crash when having mootools & UserInfo extensions enabled

    also getting this when I've disabled both:

    Notice: Undefined index: Head in /opt/lampp/htdocs/xampp/Vanilla-1.1.4/extensions/Mootools/appendix.php on line 2
  • umm, Fyorl seems to be missing... :(

  • i get this error today. it was working fine for at least 2days.


    i disabled Mootools, but right now i cannot enable ANYof my extensions. anyone got an idea?
  • nevermind. i found the problem. in the conf/extensions.php folder there was only one line=

    deleted that and it was fine, but i lost all my extensions settings, so now i have to reinstall them and make sure extensions.php is working properly.

    anybody knows why this happens?
This discussion has been closed.