Loading scripts correctly avoids conflicts, improves performance, and ensures loading on demand. Use the wp_enqueue_script function to manage load order, paths, and dependencies uniformly to avoid duplicate loading and dependency confusion; the basic usage is to register and load scripts in functions.php through the wp_enqueue_scripts hook; advanced tips include using wp_register_script to separate registration and loading to control timing; precautions include using built-in libraries such as jQuery without repeated loading to ensure handle uniqueness; tips are to add async or defer attributes to scripts through filters to optimize loading methods.
Correctly loading scripts in WordPress is the basic operation in theme and plug-in development, but many people just follow the rules and do not know the meaning and correct method behind it. Simply put: the correct enqueue method can avoid conflicts, improve performance, and ensure that scripts load on demand .
The following is based on several common scenarios and talk about how to truly "correctly" use wp_enqueue_script
.
Why can't I write the <script></script>
tag directly?
In order to save trouble, many novices will directly insert <script></script>
tags into the header or footer of the theme to introduce JS files. This seems to be fine, but there are actually many hidden dangers:
- It is easy to cause duplicate loading
- Unable to control dependencies (such as a script requires jQuery)
- Not conducive to cache optimization and performance management
- Conflicts are prone to between plug-ins and themes
Therefore, WordPress provides the wp_enqueue_script
function, which is to uniformly manage the loading order, path and dependencies of scripts.
Basic usage: Register and load a script
The most commonly used function is wp_enqueue_script()
, which is generally placed in the functions.php
file of the topic and is called through wp_enqueue_scripts
hook.
The sample code is as follows:
function my_theme_scripts() { wp_enqueue_script( 'my-script', get_template_directory_uri() . '/js/my-script.js', array( 'jquery' ), '1.0.0', true ); } add_action( 'wp_enqueue_scripts', 'my_theme_scripts' );
Parameter description:
-
'my-script'
: The handle of the script, used to identify this script - The second parameter is the URL path of the script
- The third parameter is the dependency array. For example, if you depend on jQuery, write
array('jquery')
- The fourth parameter is the version number, used for browser cache control
- The last one is whether it is loaded in footer (
true
means it is placed at the bottom)
Advanced tips: Use wp_register_script
to register and load separately
If you want more flexibility in controlling the time of script loading, you can register the script before deciding where to load it.
function my_theme_register_scripts() { wp_register_script( 'custom-slider', get_template_directory_uri() . '/js/slider.js', array( 'jquery' ), '1.0', true ); } add_action( 'wp_enqueue_scripts', 'my_theme_register_scripts' ); // Load if ( is_front_page() ) { wp_enqueue_script( 'custom-slider' ); }
The benefits of doing this are:
- Avoid unnecessary loading and improve page speed
- Better control over resource requirements on different pages
- Easier to collaborate with plugins or reuse scripts
Notes: Alias and Avoid Conflicts
WordPress has many commonly used libraries built in, such as jQuery, React, etc. Do not reload these libraries yourself , otherwise it may cause plug-in to fail or function abnormalities.
For example, if you want to use jQuery:
wp_enqueue_script( 'my-script', get_template_directory_uri() . '/js/my-script.js', array( 'jquery' ), null, true );
Just write 'jquery'
here, and WordPress will automatically load the built-in jQuery for you, and you don't need to manually specify the path.
In addition, when naming your own script, you should also pay attention to the unique handle, such as not calling jquery
or bootstrap
to avoid conflicts with other plug-ins.
Tips: Script loading location and asynchronous loading
By default, the script is loaded in the head area, and it will be placed in the footer unless you set the 5th parameter to true
.
If you want some scripts to load asynchronously (async) or deferredly (defer), you can add attributes through the filter:
function add_async_attribute( $tag, $handle ) { if ( 'my-script' === $handle ) { return str_replace( ' src', ' async src', $tag ); } return $tag; } add_filter( 'script_loader_tag', 'add_async_attribute', 10, 2 );
This approach is suitable for non-critical scripts, such as statistical code or third-party services.
Basically that's it. Although the enqueue script does not seem complicated, the details are not done properly, which can easily affect the website stability and user experience. By mastering these methods, you can better control front-end resources and write more robust WordPress themes and plug-ins.
The above is the detailed content of How to enqueue scripts correctly in WordPress. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

The main reasons why WordPress causes the surge in server CPU usage include plug-in problems, inefficient database query, poor quality of theme code, or surge in traffic. 1. First, confirm whether it is a high load caused by WordPress through top, htop or control panel tools; 2. Enter troubleshooting mode to gradually enable plug-ins to troubleshoot performance bottlenecks, use QueryMonitor to analyze the plug-in execution and delete or replace inefficient plug-ins; 3. Install cache plug-ins, clean up redundant data, analyze slow query logs to optimize the database; 4. Check whether the topic has problems such as overloading content, complex queries, or lack of caching mechanisms. It is recommended to use standard topic tests to compare and optimize the code logic. Follow the above steps to check and solve the location and solve the problem one by one.

Miniving JavaScript files can improve WordPress website loading speed by removing blanks, comments, and useless code. 1. Use cache plug-ins that support merge compression, such as W3TotalCache, enable and select compression mode in the "Minify" option; 2. Use a dedicated compression plug-in such as FastVelocityMinify to provide more granular control; 3. Manually compress JS files and upload them through FTP, suitable for users familiar with development tools. Note that some themes or plug-in scripts may conflict with the compression function, and you need to thoroughly test the website functions after activation.

Methods to optimize WordPress sites that do not rely on plug-ins include: 1. Use lightweight themes, such as Astra or GeneratePress, to avoid pile-up themes; 2. Manually compress and merge CSS and JS files to reduce HTTP requests; 3. Optimize images before uploading, use WebP format and control file size; 4. Configure.htaccess to enable browser cache, and connect to CDN to improve static resource loading speed; 5. Limit article revisions and regularly clean database redundant data.

PluginCheck is a tool that helps WordPress users quickly check plug-in compatibility and performance. It is mainly used to identify whether the currently installed plug-in has problems such as incompatible with the latest version of WordPress, security vulnerabilities, etc. 1. How to start the check? After installation and activation, click the "RunaScan" button in the background to automatically scan all plug-ins; 2. The report contains the plug-in name, detection type, problem description and solution suggestions, which facilitates priority handling of serious problems; 3. It is recommended to run inspections before updating WordPress, when website abnormalities are abnormal, or regularly run to discover hidden dangers in advance and avoid major problems in the future.

TransientsAPI is a built-in tool in WordPress for temporarily storing automatic expiration data. Its core functions are set_transient, get_transient and delete_transient. Compared with OptionsAPI, transients supports setting time of survival (TTL), which is suitable for scenarios such as cache API request results and complex computing data. When using it, you need to pay attention to the uniqueness of key naming and namespace, cache "lazy deletion" mechanism, and the issue that may not last in the object cache environment. Typical application scenarios include reducing external request frequency, controlling code execution rhythm, and improving page loading performance.

The most effective way to prevent comment spam is to automatically identify and intercept it through programmatic means. 1. Use verification code mechanisms (such as Googler CAPTCHA or hCaptcha) to effectively distinguish between humans and robots, especially suitable for public websites; 2. Set hidden fields (Honeypot technology), and use robots to automatically fill in features to identify spam comments without affecting user experience; 3. Check the blacklist of comment content keywords, filter spam information through sensitive word matching, and pay attention to avoid misjudgment; 4. Judge the frequency and source IP of comments, limit the number of submissions per unit time and establish a blacklist; 5. Use third-party anti-spam services (such as Akismet, Cloudflare) to improve identification accuracy. Can be based on the website

When developing Gutenberg blocks, the correct method of enqueue assets includes: 1. Use register_block_type to specify the paths of editor_script, editor_style and style; 2. Register resources through wp_register_script and wp_register_style in functions.php or plug-in, and set the correct dependencies and versions; 3. Configure the build tool to output the appropriate module format and ensure that the path is consistent; 4. Control the loading logic of the front-end style through add_theme_support or enqueue_block_assets to ensure that the loading logic of the front-end style is ensured.

To add custom user fields, you need to select the extension method according to the platform and pay attention to data verification and permission control. Common practices include: 1. Use additional tables or key-value pairs of the database to store information; 2. Add input boxes to the front end and integrate with the back end; 3. Constrain format checks and access permissions for sensitive data; 4. Update interfaces and templates to support new field display and editing, while taking into account mobile adaptation and user experience.
