Create a new dir and file dedicated to your javascript. /js/scripts.js. Wrap your entire javascript like this: ( function( $ ) { var allStates = $(“svg.us > *”); allStates.on(“click”, function() { allStates.removeClass(“on”); $(this).addClass(“on”); }); } )( jQuery ); Then in your theme’s functions file, put this code. It loads your new js file. function your_scripts() … Read more
WP core uses an older version of jQuery for the purposes of browser compatibility, since it is part of its mandate to support older browsers. There are many ways you could include jQuery in your WP project and manage its version. The most straightforward would be to enqueue the script as you have suggested and … Read more
jQuery is included in noConflict mode in WordPress, so you can’t use the shorthand $, but must write jQuery(this).html(jQuery(this).html().replace(rx, ‘<b>$&</b>’));
On the front end (i.e. in a Theme) don’t enqueue jQuery or jQuery UI unless you actually need to use either of them. On the back end (i.e. in the Admin area), both will already be enqueued, since core uses them. Whatever the case, if you use a core-bundled script, you should always use the … Read more
If all three plugins load jQuery properly using wp_enqueue_script(“jquery”) then only one copy of jquery will be used. If you are seeing three copies then some plugins are not playing nice.
You really shouldn’t do it, it’s not a good practice. You should always use the jQuery version supplied with WordPress package. If you use your own jQuery version in your own file you would have to update it manually every time the jQuery gets updated in WordPress package. If you really insist on doing that, … Read more
You are trying to load your inline js script after jQuery just by calling add_action( ‘wp_footer’, ‘myscript’ ); after wp_enqueue_script( ‘jquery’ ); But this will not load your myscript after jQuery. It is not how wp_footer and wp_enqueue_script works. wp_footer has a third argument named “priority”. add_action( ‘wp_footer’, ‘your_function’, 100 ); //100 is priority here. … Read more
jQuery needs to be outside the wrapper like so: <script type=”text/javascript”> (function($) { $(document).ready(function() { alert(‘hello?’); }); })(jQuery); </script> Edit: A better way would be: jQuery(document).ready(function($) { // $() will work as an alias for jQuery() inside of this function }); Also make sure any inline script tags are AFTER your call to wp_head(); And … Read more
The fifth parameter is $in_footer. You have left that out. Add that parameter, set it to true. wp_register_script( ‘jquery’, “http” . ($_SERVER[‘SERVER_PORT’] == 443 ? “s” : “”) . “://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js”, false, null, true ); But I echo the concern expressed by @Andrew in a comment. You can cause yourself trouble by deregistering/replacing the core libraries. … Read more
The issue you have is that Slider is not accessible outside of its scope as that’s defined by the .ready() though you’ve used shorthand for that. The function needs to be available in the global scope: file1.js function Slider() { this.nb_ele = 10; } jQuery(function($) { // … }); file2.js jQuery(function($) { var slider = … Read more