The simple answer is, “No”. Although admin_enqueue_scripts and wp_enqueue_scripts hooks does exactly the same thing, the do their work in separate places which do not have any reference to the other. wp_enqueue_scripts runs on the public side or front end admin_enqueue_scripts As the name suggests, it runs on the admin side or back end Your … Read more
General answer: you can call wp_enqueue_script() directly inline in the template, as of WordPress 3.4 (IIRC). So, if you have: <script src=”https://wordpress.stackexchange.com/questions/82668/myscriptforthispageonly.js”></script> You could replace it with: <?php wp_enqueue_script( ‘this-page-script’, get_template_directory_uri() . ‘/myscriptforthispageonly.js’, array( ‘jquery’ ), null, true ); ?> Edit From this comment: This is from within a page. As in a WordPress page. … Read more
I think you should just enqueue the script as well (for your validate script). I would wrap it around one whole function as well to avoid issue #11526: calling out Thus all together: <head> … <?php function mytheme_enqueue_script() { // Load jQuery wp_enqueue_script(‘jquery’); // Load draggable wp_enqueue_script(‘jquery-ui-draggable’); //load your script wp_enqueue_script(‘commonfunctions’, child_template_directory . ‘/script/commonfunctions.js’, array(‘jquery’, … Read more
Here’s an alternative way to load a popular script like jquery-ui (using google api’s) <?php // first, check to see if jquery-ui is already loaded if( !wp_script_is(‘jquery-ui’) ) { // you don’t have to use googleapi’s, but I think it helps. It saves the user’s browser from loading the same script again if it has … Read more
Yes. You’re right. It’s because of the jQuery noConflict mode. You need to use jQuery instead of $. Or you can wrap everything in a function like this to define it’s scope (function($){ $(“#generateForm”).validate({ submitHandler: function(form) { $(form).ajaxSubmit(); }, rules: { … } }, messages: { … } } }); })(jQuery); Based on several posts, … Read more
When you look at the <style|script> tags in your head, you will notice the id attribute there. Example: id=’bootstrap-css’ This – in most cases – was added by a function hooked to wp_enqueue_scripts, wp_enqueue_styles or wp_register_scripts or wp_register_styles hook. In the worst case it was hooked to either the wp_head or the wp_print_scripts hook. In … Read more
This could be one of a few different issues. 1. Wrong Hook / Not Hooked You need to make sure that wp_enqueue_script is hooked to wp_enqueue_scripts. Otherwise, the call can get fired too late or (possibly in this case?) too early? Try this (also with your php cleaned up a bit: function wpse53364() { if( … Read more
First of all, you are NOT enqueuing the script.. Try this code, working in my test install. function load_my_scripts() { // Create the localizations array $localize = array( ‘ajaxurl’ => admin_url( ‘admin-ajax.php’ ), ); // Register The Script First wp_register_script(‘custom-js’, get_stylesheet_directory_uri() . ‘/js/custom.js’, array(‘jquery’)); wp_enqueue_script(‘twentyfifteen-custom-js’, get_template_directory_uri() . ‘/js/custom.js’, array(), ‘20141010’, true); // Register the localization … Read more
Script dequeuing calls should be added to the wp_print_scripts action hook, like so: add_action(‘wp_print_scripts’,’example_dequeue_myscript’); function example_dequeue_myscript() { wp_dequeue_script( ‘myscript’ ); } This is because scripts are typically enqueued on the wp_enqueue_script hook, which happens early in the wp_head process. The wp_print_scripts hook happens right before scripts are printed, and thus is latest in the process.
Just a note before I get into the solution, get_template_directory_uri() is preferred to get_bloginfo() because it is a filtered output. That said, in the corrected code I have left it the way you had it, to save you typing in the case that you had a reason for leaving it that way. Your issue is … Read more