wp_enqueue_scripts – How to Enqueue Your Resources
Dec 27, 2023 1:18:33 GMT -3
Post by account_disabled on Dec 27, 2023 1:18:33 GMT -3
In WordPress, instead of simply adding them to the header, you follow a method called enqueuing, which is a standardized way of managing your assets with the added bonus of dependency management. Find out how to do it in this article using wp_enqueue_scripts. How Queuing Works. Managing Dependencies Load the Scripts in the Footer Specify Media Styles How Queuing Works There are two steps to follow when appending a script or style. First you register it – that is, tell WordPress that it is there – and then you append it, possibly inserting it in the header or immediately before the closing tag of the body. The reason for having two steps is modularity. Sometimes you will need to let WordPress know that a resource exists, but you may not want to use it on every page.
For example: if you are creating a custom gallery shortcode that uses Javascript, you actually Buy Bulk SMS Service only need to load the JS file when the shortcode is used – probably not on every page. The way to do this is to record the script first and only append it when the shortcode is shown (suggested reading: Ultimate Guide to WordPress Shortcodes ). To append scripts and styles in the front end you need to use the hook wp_enqueue_scripts. Inside the hooked function you can use the functions.In the example above, I registered and enqueued the assets within the same function, which is a bit redundant. In fact, you can use the record and append functions to record and append at the same time, using the same arguments you use in the record functions: Gallery code here.
Managing Dependencies The WordPress enqueueing mechanism has built-in support for managing dependencies, thanks to the use of the third argument of both. You can also use the enqueuing functions right away if you don't need to separate them. The third parameter is an array of the registered scripts and styles, which must be loaded before the current asset is enqueued. Our example would most likely rely on jQuery, so let's specify this: add_action. Suppose that the first script is a gallery, the second is an extension that opens the images in a lightbox. Note that even though our second script is based on jQuery, we don't need to specify this, as our first script will already load jQuery.
For example: if you are creating a custom gallery shortcode that uses Javascript, you actually Buy Bulk SMS Service only need to load the JS file when the shortcode is used – probably not on every page. The way to do this is to record the script first and only append it when the shortcode is shown (suggested reading: Ultimate Guide to WordPress Shortcodes ). To append scripts and styles in the front end you need to use the hook wp_enqueue_scripts. Inside the hooked function you can use the functions.In the example above, I registered and enqueued the assets within the same function, which is a bit redundant. In fact, you can use the record and append functions to record and append at the same time, using the same arguments you use in the record functions: Gallery code here.
Managing Dependencies The WordPress enqueueing mechanism has built-in support for managing dependencies, thanks to the use of the third argument of both. You can also use the enqueuing functions right away if you don't need to separate them. The third parameter is an array of the registered scripts and styles, which must be loaded before the current asset is enqueued. Our example would most likely rely on jQuery, so let's specify this: add_action. Suppose that the first script is a gallery, the second is an extension that opens the images in a lightbox. Note that even though our second script is based on jQuery, we don't need to specify this, as our first script will already load jQuery.