programmin

In case any Youtube-channel-gallery developers are reading this, you should be able to see the problem we’re all getting intermittently by adding a line to wp-includes/http-functions.php:

function wp_remote_get($url, $args = array()) {
	return new WP_Error('ouch');
	$http = _wp_http_get_object();
	return $http->get( $url, $args );
}

and to wp-includes/http.php

function wp_remote_get($url, $args = array()) {
	return new WP_Error('ouch');
	$http = _wp_http_get_object();
	return $http->get( $url, $args );
}

to simulate network not working.

By the way it seems to be an odd design decision that you must put your api key in the shortcode!? Why not make it a global option for the plugin and all Youtube displays? Also, whenever the plugin is deactivated everyone would see the shortcode api key. Will this also be fixed in a new release soon?

Thanks, I assume this was some line left from testing, that will be removed in future version?

Why would it not just wp_enqueue_style( ‘dashicons’ ) ?

Thanks, that’s next best thing to not having the in_admin check I suppose. Btw I think I asked this before, but do you have documentation for all those options in ngg_options in wp_options table?

Thanks, but this fix is unfortunately not really usable. Since that filter is called initially, and not on an action like ‘init’, it’s not likely to ever actually be filtered.

As you can see in wp-settings.php, the functions.php of themes are called after the plugins have all been called up – and in this case, it has decided whether or not to register shortcodes. I think even other plugins may or may not be able to filter depending on order of loading – unless you can call something within Nextgen to tell it to re-add-shortcodes in this case?

As you can see in the answers to this question, plugins that use this is_admin() really shouldn’t need to: http://wordpress.stackexchange.com/questions/188942/why-not-register-shortcodes-if-is-admin-dashboard

I wonder what the specific reason was for this behavior in Nextgen?

Yes, I’m still seeing the same behavior with Nextgen 2.1, even with only Nextgen plugin active, 2014 theme, and “post name” permalinks.