#Enqueue jquery wordpress code
You cannot enqueue scripts directly from your plugin code page when it is loaded. Plugins_url( '/js/myjquery.js', _FILE_ ), The enqueue call for our example looks like this: wp_enqueue_script( Always use an array even if it is for a single dependency. Since we are using jQuery to send an AJAX request, you will at least need to list ‘jquery’ in the array. The third parameter is an array of any script tags that your script is dependent on. If you are enqueuing the script for something besides a plugin, use some related function to create a proper URL – never hardcode it. For portability, use plugins_url() to build the proper URL. The second is the complete URL to your script file.
The first is an arbitrary tag or handle that is used to refer to your script in other functions. The enqueue function takes three parameters. As a plugin developer, you do not have ready access to the header template, but this rule bears mentioning anyway. Never hardcode such links in the header template. Use the function wp_enqueue_script() to get WordPress to insert a meta link to your script in the page’s section. Never send requests directly to your plugin pages. The other is that all AJAX requests need to be sent through wp-admin/admin-ajax.php. One is the need to enqueue scripts in order to get meta links to appear correctly in the page’s head section.
This section covers the two major quirks of AJAX in WordPress that trip up experienced coders new to WordPress. Second is the actual handling of the AJAX request. First we need to enqueue the jQuery script on the web page and localize any PHP values that the jQuery script needs. I have concatenated all plugins together and required scripts to default to the footer.There are two parts to the server side PHP script that are needed to implement AJAX communication. I’m pretty sure I am this down pat with some changes from the open post. Loading jQuery should never be done this way in a theme that is being released to the public. Implementing this is only appropriate on your own site. Theme developers implementing jQuery this way cause countless hours of support for plugin developers and their users when they don’t know what they are doing. Do the community a favor and don’t change it unless you know what you are doing and you AREN’T releasing the theme to the public. If a plugin is expecting jQuery v1.7.1 because that is what is built into WordPress v3.3 and your theme comes along and it has reregistered jQuery and has registered jQuery v1.2.1 from Google’s servers? Shit’s going to break because you may have plugins that are expecting jQuery v1.7.1 and instead your theme is loading jQuery v1.2.1. You are changing the global WordPress environment for all other plugins and WordPress itself by doing this. If you have deregistered the built in jQuery call, and registered a call to an old version of jQuery on Google’s servers… you are asking for problems and headaches down the road. WordPress Plugins developed using best practices enqueue jQuery via wp_enqueue_script(‘jquery’) and they expect that to load the version of jQuery that the current version of WordPress is using.
If you are releasing a theme to the public (commercial or free) ALWAYS load jQuery simply by using the wp_enqueue_script(‘jquery’) call and NEVER deregister the built in jQuery and call it from an external source. I would suggest that you ONLY implement jQuery this way on sites you yourself are running and managing AND sites that you will be making sure are always running the latest version of jQuery.
#Enqueue jquery wordpress free
Be it a commercial theme or a free theme that you plan on making publicly available. Do the WordPress community a huge favor and NEVER implement jQuery this way in a theme you will be releasing to the public.
0 kommentar(er)
