wp_enqueue_script has $deps parameter which exactly does what you need. wp_enqueue_script( $handle, $src, $deps, $ver, $in_footer ) Let’s say that your custom code is in a file named custom.js which is enqueued with a handle my-custom and you want this to be loded before my-script1 which is en-queued with a handle. wp_enqueue_script( ‘my-custom’, ‘/path/to/customjs’, array() … Read more
This is not quite simple (as copying and pasting into new functions.php :D), but you can create a plugin that will load this every time. A (very) good and simple guide can be found here. Addition by Original Poster (johannes) I created a plugin for that: I created a simple php file and put it … Read more
Your theme has to call wp_head() in the head section of the html (probably best to place it at the end of it) and wp_footer() somewhere in your footer section. Those are mandatory function calls for all themes that want to be able to integrate with plugins and some core functionality like enqueuing JS and … Read more
Put this in your .js file (function($) { // Your code inside here; })(jQuery); This is called an anonymous function, you’re passing the jQuery object as a parameter to it. OR var $ = jQuery; // This at the top of the file This is simple, you’re just assigning the jQuery object to the $ … Read more
You shouldn’t enqueue jQuery by manually using wp_enqueue_script(‘jquery’);. WordPress can enqueue it for you the right way. All you have to do is to declare jQuery as your script’s dependency: wp_enqueue_script( ‘my-script’, get_template_directory_uri() .’/my-script.js’, array(‘jquery’), null, true ); You can pass an array of dependencies as the 3rd parameter. Also, by setting the 5th parameter … Read more
Your syntax is wrong. The action must be defined outside of the callback. Also, you are using plugin_dir_path() function, which gets the path to plugin directoy in the filesystem of the server, not the url. You should use plugin_dir_url() instead. add_action( ‘wp_enqueue_scripts’, ‘myplugin_load_script’ ); function myplugin_load_script() { wp_enqueue_script( ‘myplugin-testjs’, plugin_dir_url( __FILE__ ) . “scripts/myplugin-test.js”, array(‘jquery’), … Read more
If you want to output a single line of javascript, you might not need to put it in a js file and go through enqueuing it and stuff. Simply output it by using the wp_footer() action hook: add_action(‘wp_footer’,’print_my_script’); function print_my_script(){ echo ‘<script> // Your script here </script>’; } However, this is good just for small … Read more
I’d go for A) (but give that function another name to avoid collisions), because you can be absolutely sure that all manipulation of the request is over once admin_enqueue_scripts is fired. You cannot be sure if you just put it into the functions.php (or where ever this code will live). I don’t really see a … Read more
plugin_dir_url( __FILE__ ) returns plugin URL with a trailing slash (/). So you have to remove the extra trailing slash. wp_enqueue_script( ‘awesome_form_validation’, plugin_dir_url( __FILE__ ). ‘js/form_validation.js’, array(), ‘1.0.0’, true );
You can use the global $wp_scripts and global $wp_styles; to get all registerd scripts and styles. Eg. All Scripts // All Scripts global $wp_scripts; $all_scripts = array(); foreach( $wp_scripts->registered as $script ) : $all_scripts[$script->handle] = $script->src; endforeach; // echo ‘<pre>’; // print_r( $all_scripts ); // echo ‘</pre>’; All Styles // All Styles global $wp_styles; $all_styles … Read more