To circumvent this, you can use strpos() with the_posts hook, which gets fired before wp_head. But one of the drawbacks is that its an extra pass at the data. You’re essentially doing the same inside the callback you’re hooking onto wp_head, i don’t see the difference.. (please clarify if you think otherwise).. Whether you hook … Read more
I have not tested it, but could is_main_query() (appeared in 3.3) be used here to test that the query being run is the query used to populate ‘the Loop’. (I’m not sure how it handles new WP_Query instances, though). The Codex says that it can be used on the pre_get_posts, but looking at the code … Read more
Yes you can. But to make sure the script has not already been registered or enqueued, use wp_script_is() as follows: foreach( $jquery_ui as $ui ) { if( !wp_script_is( $ui ) ) { wp_enqueue_script( $ui ); } } This will prevent conflicts due to another instance of the script being already enqueued.
One problem: if you define the script in a wp_register_script() like so: wp_register_script( ‘jquery.imagemapster.js’, get_template_directory_uri() . ‘/javascripts/jquery.imagemapster.js’, array(‘jquery’), ‘1.2.6’, false ); …then you only need to reference the defined script’s name in the wp_enqueue_script() call, like so: wp_enqueue_script( ‘jquery.imagemapster.js’ ); Re-declaring all of the parameters in wp_enqueue_script() shouldn’t cause the fatal error you describe; however, … Read more
Well the first thing to consider is that the wp_enqueue_scripts action hook fires before the filters on the page/post content are run. So I would add a function to the wp action hook and test the content for oembeds there. add_action( ‘wp’, ‘your_oembed_test_function’ ); function your_oembed_test_function(){ //earliest reliable hook to get $post variable global $post; … Read more
Why are you manually controlling Plugin’s javascript files? 1) It’s never bad practice to do things like they are supposed to be. That way, when you need to, it’s not a mountain to climb. 2) If you’re sick and I’m hired to look at your code, I expect javascripts and css to be loaded the … Read more
It looks like you’ve overlooked the 5th input parameter of: wp_enqueue_script( $handle, $src, $deps, $ver, $in_footer ); Namely the boolean $in_footer part, that will put the script in the footer, if set as true, else in the header. You can also use $deps to handle dependencies. Check out the Codex for more info. => I … Read more
All scripts and styles which get included by either wp_enqueue_script() or wp_enqueue_style() get displayed in the action hook wp_head or wp_footer. So the proper moment to merge them together would be there. Hook in very early and do your magic there. The wp_enqueue_styles hook is not necessarily the best one, since it is not always … Read more
There is no filter when a script is registered, so it is hard to track that down. Use a full text search in all your theme and plugin files to find the source. In addition, you can filter the URL before it is printed: add_filter( ‘script_loader_src’, function( $url ) { if ( 0 !== strpos( … Read more
In the codex for wp_enqueue_style, there is an argument for dependencies. So if I enqueue style A with deps B and C, A will be loaded after B and C. 🙂