?
avatar smz
smz
26 Dec 2014

This is a re-opening of #475

This has recently been re-discovered in the joomla-dev-general Google Group/Mailing list where a developer reported having issues with a BS-based slideshow module he developed, and thus is still a current and valid issue.

avatar smz smz - open - 26 Dec 2014
avatar smz
smz - comment - 27 Dec 2014

You can use the following code (taken from Twitter Bootstrap 2.3.2 reference code at http://getbootstrap.com/2.3.2/javascript.html#carousel): copy-paste it into an article (be sure to use editor:none and of course substitute the path to your images):

<div id="myCarousel" class="carousel slide" data-interval="2000">
    <ol class="carousel-indicators">
        <li data-target="#myCarousel" data-slide-to="0" class="active"></li>
        <li data-target="#myCarousel" data-slide-to="1"></li>
        <li data-target="#myCarousel" data-slide-to="2"></li>
        <li data-target="#myCarousel" data-slide-to="3"></li>
    </ol>
    <!-- Carousel items -->
    <div class="carousel-inner">
        <div class="active item"><img src="/images/slideshow-1/01.jpg"</img></div>
        <div class="item"><img src="/images/slideshow-1/02.jpg"</img></div>
        <div class="item"><img src="/images/slideshow-1/03.jpg"</img></div>
        <div class="item"><img src="/images/slideshow-1/04.jpg"</img></div>
    </div>
    <!-- Carousel nav -->
    <a class="carousel-control left" href="#myCarousel" data-slide="prev">&lsaquo;</a>
    <a class="carousel-control right" href="#myCarousel" data-slide="next">&rsaquo;</a>
</div>

When you'll display your article you'll have your slideshow and can start it by clicking on one of the nav buttons.

Now try the same when having mootool-more loaded. You can force it by editing your index.php and put the following inside the <head> ... </head> section:

<script src="/media/system/js/mootools-core.js" type="text/javascript"></script>
<script src="/media/system/js/mootools-more.js" type="text/javascript"></script>

There will be no JS errors in console, but... you will see! ?

avatar dgt41
dgt41 - comment - 27 Dec 2014

Please let mootools rest in peace!

avatar smz
smz - comment - 27 Dec 2014

Rest in peace? It should burn in hell! ?
Unhappily in this case (see the dev mailing list) someone designed a BS based slideshow module, but he was also using a componenent using Mootools for modal (BTW, don't we still use it for ToolTips?), and... crash!!

avatar brianteeman brianteeman - change - 3 Jan 2015
Labels Added: ?
avatar nternetinspired
nternetinspired - comment - 16 Jan 2015

Mootools-more and Boostrap are incompatible. End of story.

Neither libraries have attempted any sort of fix (in fact both refused to do so) so neither should we.

avatar SergioCrisostomo
SergioCrisostomo - comment - 16 Jan 2015

Just in case it can be usefull there is a UI library using MooTools based on Bootstrap: https://github.com/Behavior-UI/behavior-ui

avatar smz smz - change - 13 Jul 2015
Status New Closed
Closed_Date 0000-00-00 00:00:00 2015-07-13 08:17:24
Closed_By smz
avatar smz smz - close - 13 Jul 2015
avatar pinta83
pinta83 - comment - 12 Aug 2016

...This has recently been re-discovered in the joomla-dev-general Google Group/Mailing ...

Rediscovered????? Are you kidding me ?

It's never been fixed, altough u have a fix in https://github.com/joomla/joomla-cms/issues/475
Poor and sad......

avatar brianteeman
brianteeman - comment - 12 Aug 2016

@pinta83 you are commenting on a closed issue that no one will see

avatar pinta83
pinta83 - comment - 12 Aug 2016

@brianteeman No one obviously cares about it anyway......

avatar nternetinspired
nternetinspired - comment - 12 Aug 2016

No one should be using Mootools + Bootstrap(jQuery) at the same time.

Why would Joomla want support that when both Mootools or Bootstrap projects have said it shouldn't be done??

avatar mbabker
mbabker - comment - 13 Aug 2016

Why would Joomla want support that when both Mootools or Bootstrap projects have said it shouldn't be done??

Because when 3.0 released Joomla was still heavily dependent on MooTools for its JavaScript API. It's less of an issue today but there are still extensions and a few core systems requiring MooTools.

Considering Joomla's already forked and hacked away at Bootstrap (without documentation, ever tried implementing event handlers on some of Bootstrap's hide events and wonder WTF it doesn't work?), at this point Joomla has accepted full responsibility for maintaining the Bootstrap JavaScript APIs because it wanted to create a MooTools and jQuery/Bootstrap friendly environment so since the project has taken it upon itself to create said fork it should resolve whatever incompatibility issues exist or whatever bugs have been introduced by creating said fork.

Add a Comment

Login with GitHub to post a comment