Skip to main content
Participant
March 10, 2017
Question

DW Boostrap issues with jQuery

  • March 10, 2017
  • 1 reply
  • 1266 views

Hey Guys,

I am pulling my hair out with this one.. I built a website with Boostrap in Dreamweaver CC 2017,and all is good, but when you build a page using bootstrap it puts a jQuery call at the bottom or the page example below... The problem arises when I try to add a random image rotator that also uses jQuery but a different version, and so if I get rid of the jQuery call at the bottom of the page (1.11.3min.js) the navbar dropdown menus stop working, but the random image rotator works. And if I get rid of the call for the random rotator the navbar starts working again..

I have tried several different image rotators that are jQuery and they will not work while the Boostrap jQuery call is at the bottom of the page.

How can I get all to work on the page? Is this a common problem with Dreamweaver CC 2017??

<!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->

  <script src="js/jquery-1.11.3.min.js"></script>

  <!-- Include all compiled plugins (below), or include individual files as needed -->

  <script src="js/bootstrap.js"></script>

Here is the call/jQuery code:

<script src="Scripts/jquery.min.js"></script>

    <script src="Scripts/jquery.banner-rotator.js"></script>

    <script>

        $(window).load(function() {

            $('#myRotator').bannerRotator({

                width:963,

                height:456,

  delay:8000,

                cpanelPosition:'center bottom',

                navButtons:'large',

                navThumbs:false,

                tooltip:'image',

                depth:'auto',

  shuffle: true,

  effect: 'fade',

  pauseOnHover: true,

  thumbnails:'none',

  playButton:false

            });

        });

    </script>

  <script>

  $(window).load(function() {

  $('#myRotator2').bannerRotator({

  width:286,

  height:456,

  effect:'fade',

  shuffle:true,

  timer:'none',

  navButtons:'none',

  hideControl:true,

  pauseOnHover: true,

  playButton:false,

  thumbnails:'none'

  });

  });

  </script>

Thanks

Ken

    This topic has been closed for replies.

    1 reply

    Nancy OShea
    Community Expert
    Community Expert
    March 10, 2017

    Which jQuery library do you need for your image rotator script?  If it's 1.11 or 1.12, it should work fine with Bootstrap.  You do not want 2 jQuery scripts.   Only one.

    Now if your rotator script is using jQuery 1.10 or earlier, you need to find  or write a newer script.

    Nancy

    Nancy O'Shea— Product User & Community Expert
    ALsp
    Legend
    March 10, 2017

    https://forums.adobe.com/people/Nancy+OShea  wrote

    Which jQuery library do you need for your image rotator script?  If it's 1.11 or 1.12, it should work fine with Bootstrap.  You do not want 2 jQuery scripts.   Only one.

    Now if your rotator script is using jQuery 1.10 or earlier, you need to find  or write a newer script.

    Nancy

    And therein lies just one the reasons Adobe should not be in the business of pulling off the shelf free libraries written by other people into Dreamweaver. I feel bad for the original poster, but it's kind of funny, in a sad way. You really expect people to accept this, huh?

    pziecina
    Legend
    March 11, 2017

    ALsp  wrote

    And therein lies just one the reasons Adobe should not be in the business of pulling off the shelf free libraries written by other people into Dreamweaver. I feel bad for the original poster, but it's kind of funny, in a sad way. You really expect people to accept this, huh?

    Sorry AL, but even though I agree about Dreamweaver not using 3rd party solution, the other 2 alternatives are in my opinion just as bad.

    We could ask Adobe to develop their own solutions, which we both know would probably be worse.

    The second alternative, is to leave everything to extension developers, which leaves Dw users with only what extension developers think we should have. Also unacceptable in my opinion.

    Of course, there is a 3rd possibility, and that is for Dw to improve its support for modern W3C standards, and modern javascript. That way users can develop their own solutions, but we both know how difficult, (almost impossible) it would be to get Dw to do that.