Joshua David Nelson

Jairo,

That sounds like a good plan. It seems like you have quite a few scripts that need to be in the header, and may or may not be dependent on jquery. If it turns out that the majority of your scripts are dependent on jquery, and they need to be loaded in the header, I would suggest not using this plugin.

Instead, I would de-enqueue the scripts you want in the footer, and then re-enqueue them with the $in_footer set to true. This will place those scripts into the footer automatically. Unfortunately, this can’t be done as default for all scripts because scripts can be called from multiple places within themes and plugins, which is why this plugin disables a few hooks, forcing all scripts in the footer.

Does that make sense? Hope that helps!

Cheers,
Joshua

Ah, yes. Well, jquery is a popular script and it is often referenced by others as being dependent on it. This means that those scripts essentially piggy-back on jquery and only load after it.

There are a multitude of places and ways to enqueue a script, and they could be from one/more plugins or your theme, so it is very hard to diagnose a solution for a specific combination of theme/plugins that may be dependent on jquery.

My suggestion would be to either take the easier route and disable the plugin on the specific page(s) where you’re having the issue – keeping them in the header. Or, a more lengthy process would be to deactivate all your other plugins, then activate theme one-by-one and figure out where the specific script is registered, deregister it similar to above and re-register it without the jquery dependency. The latter option is not exactly standard procedure though, and could cause issues should you ever deactivate this plugin and the order gets mixed up again.

It could also be that what you need is a plugin to minify your scripts instead of this plugin to move them to the footer.

Hope that helps!
Joshua

This is most likely an issue with your theme or plugins. I responded to your email, but again:

There is no reason way uninstalling this plugin would not work. Have you deleted it from your plugins folder? You should verify that it is in fact deactivated and deleted. (Go into your FTP and make sure it is not in your plugins folder).

Also, try deactivating all your plugins and reverting to a default theme (twenty fourteen or twenty twelve theme). Then reactivate your other plugins one by one. It is likely a plugin conflict or theme error. Let me know if you have any issues after that and if you’ve discovered a plugin that Scripts-to-footer conflicts with so we can fix any issue.

Thanks,
Joshua

Bala666,

I’m happy to help you resolve this issue, but it would be appreciated if you reached out for support on your own thread only and re-rated the plugin once we’ve resolved this. Your issue is likely due to another plugin or theme setting, it’s impossible for this code to still work once it’s been removed – so if you did delete it and deactivate it – AND your theme and other plugins are coded to standards – there would be no issue.

Joshua

Jario,

Yes, there is a built-in way to do this when you enqueue a script – by setting it dependent on another script, like jquery, it will only be loaded if jquery has been loaded.

That said, while Scripts-to-footer should, in theory, place everything in the footer in the same order – there are plenty of scripts that actually need to be placed in the header in order for page elements or in-line scripts to work. That might be the case for your issue.

You can either disable the plugin on the specific page that is having the issue, or you can use this tutorial to place specific scripts in the header. Just be sure you are grabbing the correct scripts and placing them in the correct order.

Cheers,
Joshua

Semagoff,

Any luck? I’m not able to replicate this issue in any other site and the other instance of this error is no longer an issue either.

Thanks,
Joshua

Andres,

I received a reply from Kazu, the developer for your directory plugin. First, be sure to update to the newest Scripts-to-Footer plugin version, I just updated to 0.5 to include a filter you can use for this purpose (you can see more information on the main plugin page).

Kazu suggested the following code for creating a conditional statement for his sabai directory plugin:

if (!function_exists('is_sabai')) {
	function is_sabai() {
		return is_page()
			&& isset($GLOBALS['post'])
			&& ($slugs = get_option('sabai_sabai_page_slugs', false))
			&& is_array($slugs[2])
			&& in_array($GLOBALS['post']->ID, $slugs[2]);
	}
}

You would place that code above in your functions.php file, then place this in there as well:

add_filter( 'scripts_to_footer_exclude_page', 'andres_excluded_sabai' );
function andres_excluded_sabai( $exclude_page ) {
	if( function_exists( 'is_sabai' ) && is_sabai() ) {
		$exclude_page = 'on'; // this turns on the "exclude" option for any sabai
	}
	return $exclude_page;
}

Please note that I don’t have any way to test Kazu’s code because I don’t have access to his plugin. In theory, this should work, but let me know if you get any error messages or have any other issues. The filter code I have tested with other conditionals in a similar fashion, so hopefully the is_sabai function works as well.

Cheers,
Joshua