i usally first deregister to avoid duplicates, then register it and enqueue it like so: function my_scripts_method() { wp_deregister_script( ‘jquery’ ); wp_register_script( ‘jquery’, ‘http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js’); wp_enqueue_script( ‘jquery’ ); } add_action(‘wp_enqueue_scripts’, ‘my_scripts_method’); Hope this helps, Sagive.
All other scripts running on that page depend on the correct jQuery file shipped with WordPress: admin bar, jQuery-UI or other plugins. Note that loading external resources is not possible in all setups, so your options page would not work in these cases. To use scripts that needs $ use $ = jQuery.noConflict(); or put … Read more
You have to define the dependencies for either styles or scripts when you register them. Or, if you’re avoiding the registration completely, then it’s ok to stuff them into the queueing process. See more on the Codex page. wp_register_style( ‘reset’, get_template_directory_uri().’/reset.css’ ); wp_register_style( ‘style’, get_template_directory_uri().’/style.css’, array( ‘reset’ ) ); wp_enqueue_style( ‘style’ ); Also avoid single … Read more
WordPress-specific script issues are generally limited to one of the following: Improperly enqueued script Proper script enqueueing involves use of wp_enqueue_script(). If the script is properly enqueued, you will see a <script….> link in the document head or footer Not accounting for jQuery no-conflict mode WordPress-bundled jQuery is configured for no-conflict mode, which requires wrapping … Read more
Here is the short sweet answer. Somewhere you, a plugin, or your theme are doing something like this: wp_register_script( ‘myscript’, get_template_directory_uri() . ‘/path/to/myscript.js’, ”, ”, true ); What should be happening is this: add_action( ‘wp_enqueue_scripts’, function() { wp_register_script( ‘myscript’, get_template_directory_uri() . ‘/path/to/myscript.js’, ”, ”, true ); } ); From the Notice: Scripts and styles should … Read more
How do I get my theme scripts to load in a custom theme built from Bootstrap
How to wp_enqueue_script with html?
You have to make sure your script is registered with wp_register_script before your call to wp_localize_script. So in your functions.php file: add_action(‘init’,’my demo_function’); function my demo_function() { // Register the script wp_register_script( ‘myuserscript’, ‘path/to/myscript.js’ ); // Localize the script with your data $theid=get_current_user_id(); $params = array( ‘userid’ => $theid ); wp_localize_script( ‘myuserscript’, ‘MyUserParams’, $params ); … Read more
This might work for you. try with enqueue instead of registering it. wp_deregister_script(‘jquery’); wp_enqueue_script( ‘jquery’, get_template_directory_uri() . ‘/js/libs/jquery-3.1.1.min.js’, array(), “3.1.1”, true );
Since wp-login.php control both login and registration, it is better to redirect the visitor to a login page from wp-login.php. You can use this code for redirecting your registration page – add_action(‘init’,’custom_registration_page’); function custom_registration_page() { $new_registration_page_url = home_url( ‘/register/’ ); global $pagenow; if( $pagenow == “wp-login.php?action=register” && $_SERVER[‘REQUEST_METHOD’] == ‘GET’) { wp_redirect($new_registration_page_url); exit; } } … Read more