Comments on: Smartly resolving your WordPress pages and posts JavaScript and CSS dependences http://www.heavyworks.net/blog/posts/smartly-resolving-your-wordpress-pages-and-posts-javascript-and-css-dependences Extreme Software Engineering Thu, 09 Feb 2012 06:29:07 +0000 hourly 1 http://wordpress.org/?v=3.3 By: tkaranovhttp://www.heavyworks.net/blog/posts/smartly-resolving-your-wordpress-pages-and-posts-javascript-and-css-dependences/comment-page-1#comment-566 tkaranov Sat, 24 Dec 2011 15:28:46 +0000 http://www.heavyworks.net/?p=401#comment-566 I have similar code that takes the js file name from the custom field value: if ( get_post_meta($post->ID, 'javascript', true) ) { $script = get_post_meta($post->ID, 'javascript', true); $script_path = get_bloginfo('template_url') . '/scripts/' . $script . '.js'; wp_enqueue_script( $script, $script_path ); } The code above is in my header.php and each post that needs custom javascript has a custom field named javascript with a value = to the js file name. However, it only works when the post is viewed as a single post or is the first post on the home page. Once another post is added (making the relevant post now the 2nd post on the home page) this code doesn't work. It sounds like the use of "foreach" instead of "if" is the difference but don't know enough to change the code to a "foreach" statement instead of an "if" statement. Would you please advise how I can change this code to work as a "foreach" statement? I have similar code that takes the js file name from the custom field value:
if ( get_post_meta($post->ID, ‘javascript’, true) ) {
$script = get_post_meta($post->ID, ‘javascript’, true);

$script_path = get_bloginfo(‘template_url’) . ‘/scripts/’ . $script . ‘.js’;
wp_enqueue_script( $script, $script_path );
}
The code above is in my header.php and each post that needs custom javascript has a custom field named javascript with a value = to the js file name.

However, it only works when the post is viewed as a single post or is the first post on the home page. Once another post is added (making the relevant post now the 2nd post on the home page) this code doesn’t work.

It sounds like the use of “foreach” instead of “if” is the difference but don’t know enough to change the code to a “foreach” statement instead of an “if” statement.

Would you please advise how I can change this code to work as a “foreach” statement?

]]> By: Hessyhttp://www.heavyworks.net/blog/posts/smartly-resolving-your-wordpress-pages-and-posts-javascript-and-css-dependences/comment-page-1#comment-533 Hessy Tue, 12 Apr 2011 02:04:58 +0000 http://www.heavyworks.net/?p=401#comment-533 Good point. I hadn't tohguth about it quite that way. :) Good point. I hadn’t tohguth about it quite that way. :)

]]> By: Teigehttp://www.heavyworks.net/blog/posts/smartly-resolving-your-wordpress-pages-and-posts-javascript-and-css-dependences/comment-page-1#comment-528 Teige Mon, 11 Apr 2011 23:19:23 +0000 http://www.heavyworks.net/?p=401#comment-528 IMHO you've got the right aneswr! IMHO you’ve got the right aneswr!

]]> By: Jan Seidlhttp://www.heavyworks.net/blog/posts/smartly-resolving-your-wordpress-pages-and-posts-javascript-and-css-dependences/comment-page-1#comment-306 Jan Seidl Wed, 24 Feb 2010 02:43:51 +0000 http://www.heavyworks.net/?p=401#comment-306 That's a nice idea Bruno! Will test it out and update the post! Thanks for the tip! That’s a nice idea Bruno! Will test it out and update the post! Thanks for the tip!

]]> By: Bruno Lustosahttp://www.heavyworks.net/blog/posts/smartly-resolving-your-wordpress-pages-and-posts-javascript-and-css-dependences/comment-page-1#comment-305 Bruno Lustosa Wed, 24 Feb 2010 00:33:49 +0000 http://www.heavyworks.net/?p=401#comment-305 Very fine article. Using custom fields to store javascript and stylesheet info is very clever. Perhaps it could be made better by hooking to wp_head and placing both foreachs in functions.php. This would leave the template file with less kludge. Very fine article. Using custom fields to store javascript and stylesheet info is very clever.
Perhaps it could be made better by hooking to wp_head and placing both foreachs in functions.php. This would leave the template file with less kludge.

]]>