Fires when scripts and styles are enqueued.
Source
do_action( 'wp_enqueue_scripts' );
Changelog
| Version | Description |
|---|---|
| 2.8.0 | Introduced. |
Fires when scripts and styles are enqueued.
do_action( 'wp_enqueue_scripts' );
| Version | Description |
|---|---|
| 2.8.0 | Introduced. |
You must log in before being able to contribute a note or feedback.
Basic Example
Instead of this Action, use ‘admin_enqueue_scripts’ for Admin pages and ‘login_enqueue_scripts’ for the login page.
If you want to add dynamic inline styles.
Selectively load JS files into specific pages like so:
do_blocks()is called beforewp_enqueue_scriptsso if you are correctly registering scripts and only enqueuing on pages it’s needed on (which most developers do not seem to do), keep in mind that if you use something likewp_localize_script, it will not work if you’re registering your script inwp_enqueue_scriptshook and enqueueing it from some kind of trigger generated by content, shortcode, template files, or something else that could be loaded bydo_blocks.This will result in javascript errors saying
XYZ variable is not definedI had a lot of plugin clients report issues because of this, as my call to
wp_enqueue_scriptis normally triggered by a template file or something that now gets loaded indo_blocks()(like a shortcode), which is BEFOREwp_enqueue_scriptsaction is triggered, meaning the script is not registered yet.The solution for me in this situation was to create a conditional check before calling
wp_localize_scriptand thenwp_enqueue_script, to see if the script has been registered already, and if not, make sure to callwp_register_scriptfirst.This actions passes an argument
$hookthat is handy when for example to prevent the script from loading on certain pages;wp_enqueue_scriptsaction, however, it does apply for theadmin_enqueue_scriptsaction.