wp-enqueue-script

Default priorities are fine unless you have special cases where things need to load in a specific order, and even then, you should be defining dependencies for them instead of relying on priority numbers. Priority numbers are a last resort mechanism, like CSS !important. Avoid setting them unless actually needed.

So simple I will explain it step by step: First, use the $hook variable that is WordPress default like this: function the_themescripts($hook) { echo $hook; } add_action( ‘admin_enqueue_scripts’, ‘dr_theme_options_style_scripts’ ); Now go to custom page in your admin WP Dashboard and at the top you will see something like toplevel_page_your_theme_page_slug if it does not visible … Read more

You could use add_query_arg() but then you’d have to parse the uri everytime, I’d rather create a wrapper function for wp_enqueue_script/style: function my_enqueuer($my_handle, $relpath, $type=”script”, $my_deps=array()) { $uri = get_theme_file_uri($relpath); $vsn = filemtime(get_theme_file_path($relpath)); if($type == ‘script’) wp_enqueue_script($my_handle, $uri, $my_deps, $vsn); else if($type == ‘style’) wp_enqueue_style($my_handle, $uri, $my_deps, $vsn); } Add this in your functions file … Read more

The “init” action runs both on frontend page loads, and on backend page loads. Try hooking these to the “wp_enqueue_scripts” action instead. I believe it does not run on admin page loads. Example Code: (By OP) function wpse54388_scripts_styles() { wp_enqueue_style( … ); wp_enqueue_script( … ); } add_action( ‘wp_enqueue_scripts’, ‘wpse54388_scripts_styles’ );