Hi fuzzllc,
Alright. I have had a look and it appears that the js to footer function may have indeed caused the error. That said, there are some responsive themes that need the JS libraries to be in the head section of the code. We are however, working on adding an option for the user to exclude scripts from being moved. In the meanwhile, you could comment out the specific function (line 35 – 46) by adding 2 x pre-pending // to each line so that instead of:
function footer_enqueue_scripts() {
remove_action('wp_head', 'wp_print_scripts');
remove_action('wp_head', 'wp_print_head_scripts', 9);
remove_action('wp_head', 'wp_enqueue_scripts', 1);
add_action('wp_footer', 'wp_print_scripts', 5);
add_action('wp_footer', 'wp_enqueue_scripts', 5);
add_action('wp_footer', 'wp_print_head_scripts', 5);
}
add_action('after_setup_theme', 'footer_enqueue_scripts');
it will now be :
// function footer_enqueue_scripts() {
// remove_action('wp_head', 'wp_print_scripts');
// remove_action('wp_head', 'wp_print_head_scripts', 9);
// remove_action('wp_head', 'wp_enqueue_scripts', 1);
// add_action('wp_footer', 'wp_print_scripts', 5);
// add_action('wp_footer', 'wp_enqueue_scripts', 5);
// add_action('wp_footer', 'wp_print_head_scripts', 5);
// }
// add_action('after_setup_theme', 'footer_enqueue_scripts');
If you’d like, I can make the change for you and send you a copy. Feel free to shoot me an email at [email protected]
Ps. We are adding a few more (awesome) speed boosting functions to the plugin.
