The wp_enqueue_script function is the best solution for loading JavaScript files into your WordPress site. If you're developing a theme that uses JavaScript or JavaScript Libraries, the wp_enqueue_script function is the way to go. If you haven't really used this before though, it can be confusions... so today, we'll be taking an in depth look into how to properly load scripts into your theme or plugin using the enqueue function.

Subsequent Changes to Techniques & Software Certain aspects of applications or techniques used in this tutorial have changed since it was originally published. This might make it a little difficult to follow along. We'd recommend looking at these more recent tutorials on the same topic: How to Include JavaScript and CSS in Your WordPress Themes and Plugins

Why Do We Use The Enqueue Function?

If you're coming from a basic HTML background, you're probably used to simply loading up Javascript files (including anything from jQuery to plugin scripts) directly into the header or footer of your document. That's fine when you're in a standalone environment like a basic HTML page... but once you introduce the myriad of other scripts that might potentially run on a WordPress installation, it gets trickier to do what I'll call "crowd management" with your scripts.

So why not load your JavaScript in the Header or the Footer? The answer is pretty simple: By including your JavaScript like that, you run the risk of having conflicts with your JavaScript across your installation (think, multiple plugins trying to load the same scripts, or different versions of that script). Furthermore, your JavaScript will load on every page, even if you don't need it to. This will cause an unnecessarily longer load time for you pages, and can interfere with other JavaScript, like from a plugin or within the dashboard... and that's a No No in WP development.

By using the wp_enqueue_script function. You'll have better control with how and when you load your JavaScript. You can even decide whether to load into the header or footer.

Understanding the wp_enqueue_script Function

The wp_enqueue_script function is what loads scripts into you WordPress site. You're usually going to use it in your functions.php file.

The wp_enqueue_script function itself is pretty straight forward, so let's take a look it's structure.

wp_enqueue_script( $handle, $src, $deps, $ver, $in_footer );

$handle This is the handle (the name) of the script to be loaded. It should be in all lower case. This is Required Default: None

$scr This is the URL of the script. If you're loading locally from your server you shouldn't hard code the URL for scripts on your server. It's better to use content_url , bloginfo("template_url") , or get_template_directory_uri() (recommended by the WordPress Function Reference) for themes, and plugins_url for plugins. If you're loading your script from another server. For example, loading the jQuery Library from the Google CDN. You just put the URL of the file to be loaded. This is Optional Default: false

$deps This is an array that handles any script dependencies. For example, is your fade.js script requires jQuery to run. This parameter will associate your script to the jQuery Library. You use "false" if you don't want to use this parameter, but want to use other parameters. The required script must be loaded first. You use the required script's handle for the array. This is Optional Default: array()

$ver This is the version of your script. The version is concatenated to the end of the path as a query string. The version can be the version number, false, or NULL. If you use false for the version. The WordPress version will be used. If you use NULL. Nothing will be used as a version. This is not recommended by the WordPress Function Reference. If you don't use the $ver parameter.The WordPress version will be used by default. This is Optional Default: false

$in_footer This will determine where your script is place on the page. This parameter is a boolean ("true" or "false") By default your script will be placed in the <head >, but it is better to place it right before the close of the <body > tag. This is accomplished by passing "true" to the parameter. This is Optional Default: false



As you can see, all of the parameters except $handle are optional. At first glance this may seem odd. Especially the $scr parameter. How can WordPress locate the script without a url?

The reason behind this is that WordPress comes with scripts built in. For example jQuery is part of the WordPress core, and the WordPress development team made it super simple to load these built in scripts. All you have to do is pass the script's handle to wp_enqueue_script .

For the complete list of built in WordPress scripts and thier handles.Take a look at the WordPress Function Reference.

Using Enqueue Script with Your WordPress Theme

Now that you understand the parts of wp_enqueue_script . Let's look at how you actually use this with your WordPress theme.

First Things First

There are other WordPress functions that you need to know before you can start enqueing scripts properly.

wp_register_script The wp_register_script function is used to register your script with WordPress. What this means is, you will be able to use wp_enqueue_script for your scripts just like the built in scripts that come with WordPress The parameter structure for wp_register_script is exactly the same as the wp_enqueue_script structure, so I'm not going to go over it again. You can reference the section above if needed. Just set up wp_register_script just as you would for wp_enqueue_script . Then enqueue the script with wp_enqueue_script by passing the handle to it.

wp_deregister_script The wp_deregister_script removes a registered script. All you need to do is pass the handle to it.

wp_deregister_script The wp_dequeue_script removes a registered script. All you need to do is pass the handle to it.



Loading Your Scripts

The easiest way to load your script is to place the wp_enqueue_script where ever you want it on your page.

Easy enough, just not to elegant. A better way, is to use your function.php file to load your scripts. To do this you need to make a custom function. Then use add_action to initialize your function.

Line 2 creates a function called load_my_scripts

Line 3 registers the script myscript

Line 4 enqueues the script myscript

Line 6 initializes the function load_my_scripts

The script we just loaded needs the current version jQuery to run, so let's deregister the default version that comes with WordPress add the new version to our function.

Line 2 deregisters the default jQuery that comes with WordPress

Line 3 registers another version of jQuery

Line 4 enqueues the script myscript

OK, good practices for WordPress coding dictates we need to check if a function exists before we run it. This is accomplished like this.

This checks if your function already exists.If it doesn't, it'll run your function.

Let's add this to our load_my_scripts function

Now, if you go to your admin page you don't want your script to load. It might cause a conflict and break the admin page. A general rule of thumb is that you don't want your custom scripts to load in the admin page. Scripts for plugins is a different story. I'll go over that later.

We're going to check if the page loaded is not the admin page with !is_admin(). If it's not, our scripts will load.

Now the function looks like this.

There you go. A nice template for you to use for you to enqueue scripts

Using Enqueue Script for Your Plugins

OK, now that you got that down. Let's add a script that will only load on your plugin's admin page.

It's actually very simple. Just write your script function just like the on we did in the previous section in your plugin's file. Only now instead of using 'init' in the add_action, use 'admin_init'.

That's it, now your script will only load when you go to you plugin's admin page.

Conclusion

I hope this will help you better understand Enqueue Scripts within WordPress, so now you can get out there and load some scripts of your own!

If there is anything you don't understand or would like to read up on. I recommend visiting the WordPress Codex. Here's a list of some other relevant codex links for ya as well: