WordPress本地环境中wp_enqueue加载脚本与样式失败求助

Hey there, let’s break down why your wp_enqueue_script and wp_enqueue_style calls aren’t loading assets even with correct paths and parameters—this is such a common pitfall in local WP environments, so let’s go through the most likely fixes step by step:

• Double-check your action hook
  Assets need to be hooked to the right WP action to load properly. For front-end assets, you must use the wp_enqueue_scripts hook (not init, wp_loaded, or anything else). If you’re targeting the admin area, use admin_enqueue_scripts, and for the login page, login_enqueue_scripts. A common mistake is misspelling the hook name or using the wrong one entirely. Here’s a correct example for front-end loading:

  function my_theme_load_custom_assets() {
      // Load script (depends on jQuery, loads in footer)
      wp_enqueue_script( 'my-custom-script', get_template_directory_uri() . '/js/custom.js', array('jquery'), '1.0.0', true );
      // Load style
      wp_enqueue_style( 'my-custom-style', get_template_directory_uri() . '/css/custom.css', array(), '1.0.0' );
  }
  add_action( 'wp_enqueue_scripts', 'my_theme_load_custom_assets' );
  

• Confirm your active theme and path functions
  If you’re adding this code to a theme’s functions.php, make sure that theme is actually active in your local WP install—it’s easy to accidentally switch themes and forget! Also, if you’re using a child theme, replace get_template_directory_uri() with get_stylesheet_directory_uri()—the former points to the parent theme’s folder, which might not be where your assets live.

• Avoid handle name conflicts
  The first parameter in wp_enqueue_script/wp_enqueue_style is a unique "handle" name. If your handle matches one that WP core or a plugin already uses (like jquery or style), WP will skip loading your asset because it assumes the resource is already enqueued. Try using a unique handle, like my-site-main-script, to rule this out.

• Clear all caches (yes, even local ones)
  Local environments can still have browser cache or leftover caching from plugins. Do a hard refresh in your browser (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to bypass cached assets. Also, temporarily disable any caching plugins you have installed—they might be suppressing your new assets from loading.

• Ensure your theme has wp_head() and wp_footer()
  WP needs these template tags to output enqueued assets. Check your theme’s header.php file for <?php wp_head(); ?> right before the closing </head> tag, and footer.php for <?php wp_footer(); ?> right before the closing </body> tag. If either is missing or commented out, your assets won’t have a place to load.

• Debug with WP’s built-in functions
  To confirm if your assets are actually being enqueued, add a quick debug snippet to your theme’s header or footer:

  // Check if script is enqueued
  var_dump( wp_script_is( 'my-custom-script', 'enqueued' ) );
  // Check if style is enqueued
  var_dump( wp_style_is( 'my-custom-style', 'enqueued' ) );
  

  If the output is bool(true), your enqueue code works—focus on browser cache or path validity. If it’s bool(false), your code isn’t being executed, so go back to check your hook, active theme, or syntax errors in functions.php.

内容的提问来源于stack exchange，提问作者Taqi Shah