Earlier today, Jason Gegere asked me how to prevent WordPress from checking for updates on a plugin. This may be helpful if you are running a custom version of a plugin from the repository and you don’t want to accidently update the plugin and lose the customizations, or if you are running a private plugin and don’t want WordPress to check for updates from the plugin repository. WordPress doesn’t know if your plugin is in the WordPress plugins repository and it will request the update check on all installed plugins.
WordPress checks for updates using wp_update_plugins() in wp-includes/update.php but there are no hooks in this function which could be used to exclude your plugin from the update check. However, you can hook into http_request_args and remove your plugin from the query arguments passed in the http request. You can add the following code to your plugin to prevent WordPress from checking for updates for your plugin:
add_filter( 'http_request_args', 'dm_prevent_update_check', 10, 2 );
function dm_prevent_update_check( $r, $url ) {
if ( 0 === strpos( $url, 'http://api.wordpress.org/plugins/update-check/' ) ) {
$my_plugin = plugin_basename( __FILE__ );
$plugins = unserialize( $r['body']['plugins'] );
unset( $plugins->plugins[$my_plugin] );
unset( $plugins->active[array_search( $my_plugin, $plugins->active )] );
$r['body']['plugins'] = serialize( $plugins );
}
return $r;
}
Related posts:
Let me be specific. To correctly use this function. Would this example be correct for the commonly used “Art Direction” plugin?
add_filter( ‘http_request_args’, ‘dm_prevent_update_check’, 10, ‘http://wordpress.org/extend/plugins/art-direction’ );
What does the variable $r = 10 specify.
No, that’s not correct.
add_filter()takes in four parameters and you can read more about it in the codex here. The two arguments,$rand$url, come from thewp_remote_post()inwp_includes/updates.php. You’ll just need to paste the code as-is in your plugin.Very nice, I’m a huge fan of WordPress and it’s great to see new really useful plugins getting released. Going to download and check it out, looks exactly like what I was looking for for weeks. So, thanks alot!
Just one question regarding the code above:
does the plugin need to be activated to actually work?
In a short test with an outdated plugin (which was not active at that moment) on my WordPress MU the code had no further effect.
However, thanks for all your exceptionally insightful posts
Yes, the plugin needs to be activated for the code to work.
Doesn’t work in WordPress 3.0? Or am I doing something wrong…?
Works with 3.0. You may be doing something wrong.