Nope, doesn’t need either of those. Also, you can just disable the junk without totally disabling wp_head and wp_footer. For example, using the following in functions.php:
remove_action( ‘admin_print_styles’, ‘print_emoji_styles’ );
remove_action( ‘wp_head’, ‘print_emoji_detection_script’, 7 );
remove_action( ‘admin_print_scripts’, ‘print_emoji_detection_script’ );
remove_action( ‘wp_print_styles’, ‘print_emoji_styles’ );
remove_filter( ‘wp_mail’, ‘wp_staticize_emoji_for_email’ );
remove_filter( ‘the_content_feed’, ‘wp_staticize_emoji’ );
remove_filter( ‘comment_text_rss’, ‘wp_staticize_emoji’ );
remove_action(‘wp_head’, ‘wp_generator’);
remove_action(‘wp_head’, ‘wp_shortlink_wp_head’);
remove_action( ‘wp_head’, ‘feed_links_extra’, 3 );
remove_action( ‘wp_head’, ‘rsd_link’ );
remove_action( ‘wp_head’, ‘wlwmanifest_link’ );
Anyway, none of this has anything to do with Minify HTML working or not. It runs at the lowest level (on the init action). I’ve never seen a theme that messes with the init level (nor should it). The plugin-in is fairly straight-forward. Runs on init as long as not is_admin() and minify is turned on.
Tim
-
This reply was modified 8 years, 1 month ago by
Tim Eckel.