Enqueue your script instead of putting it in your template, you can enqueue your code as is, or put your code in an actual file. The benefit of doing this is you gain control over output, as you can see there is a $priority parameter for add_action. add_action( $hook, $function_to_add, $priority, $accepted_args ); Futhermore wp_enqueue_script … Read more
I would use jquery-masonry included in WordPress core: function my_scripts() { wp_enqueue_script( ‘jquery-masonry’, true ); } add_action( ‘wp_enqueue_scripts’, ‘my_scripts’ ); If you really need the standalone masonry library, you should use your “first way” but I would not use “my_masonry” as handle for the script, I would use “masonry” if you have not modified the … Read more
My guess would be that you are remove the action before it is actually being added in the parent theme. The parent’s theme functions.php file gets loaded after the child one so it looks like your removing something that is not there yet. The 3rd parameter in remove_action() is the priority. Try playing around with … Read more
Use in_array(): if ( in_array( $hook, [ ‘user-edit.php’, ‘profile.php’ ] ) ) // do something Or wait for the action personal_options, and enqueue the script for the footer. This action is fired in both cases. See this old example.
It seems that you need to add styles and scripts to a single post. The best way to achieve this is to make use of the conditional tag is_single() With that you target specific single posts or all single posts. Styles should always be loaded in the header. <link> tags outside the <head></head> tags are … Read more
Straight outta the Codex: wp_enqueue_scripts is the proper hook to use when enqueuing items that are meant to appear on the front end. Despite the name, it is used for enqueuing both scripts and styles. So the simple answer to your question is yes, wp_enqueue_scripts is always the correct action for enqueuing scripts AND styles. … Read more
Usually it is bp-legacy-js. But if you place a buddypress.js in wp-content/themes/your-theme/buddypress/js/ this file will be taken instead. The handle will be bp-parent-js The same goes for CSS files, if you place them in /your-theme/buddypress/css/. If you place the buddypress.js in a childtheme, the handle will be bp-child-js.
Would you please try below code to your plugin page. if the script file is your plugin root directory. function plugin_adding_scripts() { wp_register_script(‘my_test_script’, plugins_url(‘testscript.js’, __FILE__), array(‘jquery’),’1.1′, true); wp_enqueue_script(‘my_test_script’); } add_action( ‘wp_enqueue_scripts’, ‘plugin_adding_scripts’ ); Also: http://blog.aztora.com/add-css-js-into-wordpress-plugin/
You can use get_stylesheet_directory_uri(); while enqueuing the scripts and styles. It returns the directory path in which your child stylesheet is stored.
jQuery is there because something else, probably a plugin, enqueued it. The enqueue API won’t load it twice, so if you need it you need to ask for it. The “right way” is to tell WP what you need, and let WP work out the dependencies and duplicates. Now, there is a rather large “but” … Read more