By Caleb

2011-06-21 10:12:38 8 Comments

Is there a way to disable update notifications for specific plugins?

As a plugin developer, I have some plugins installed on my personal site using the svn trunk version for testing, but the same plugins are available from the plugin site. In these cases WP considers the latest version to be the most recently published version and constantly tries to warn me that updates are available.

I still want to see notifications for updates on other plugins, but it's anoying to constantly ignore the Updates (2) notice in the header!


@Super Model 2018-05-09 11:09:18

Disable All Update Notifications with Code

function remove_core_updates(){
        global $wp_version;return(object) array('last_checked'=> time(),'version_checked'=> $wp_version,);

Code will disable update notifications for the WordPress core, plugins, and themes.

@Gangesh 2019-07-18 10:30:01

"individual plugins" is the key

@Super Model 2019-07-18 13:20:02

@Gangesh, I think he wants to disable some specific plugin's notifications

@circlecube 2015-01-27 15:01:04

Hameedullah Khan's answer will throw a PHP warning. Include this if clause to check to make sure it's an object before unsetting the response for that plugin.

'Warning: Attempt to modify property of non-object'

Try this to avoid the warnings (code for the plugin file itself):

// remove update notice for forked plugins
function remove_update_notifications($value) {

    if ( isset( $value ) && is_object( $value ) ) {
        unset( $value->response[ plugin_basename(__FILE__) ] );

    return $value;
add_filter( 'site_transient_update_plugins', 'remove_update_notifications' );

I like to put this in the actual plugin. Since I've only ever disabled updates on a plugin because I've edited or forked the code and don't want to lose my edits on an update, I've already edited the plugin and thus don't mind editing it more. It keeps my functions file a bit cleaner. But if you wish you can put it in the functions file and a benefit to that method is you can remove multiple plugins from updates by adding another unset line for that plugin like so (code for functions.php):

// remove update notice for forked plugins
function remove_update_notifications( $value ) {

    if ( isset( $value ) && is_object( $value ) ) {
        unset( $value->response[ 'hello.php' ] );
        unset( $value->response[ 'akismet/akismet.php' ] );

    return $value;
add_filter( 'site_transient_update_plugins', 'remove_update_notifications' );

@Philip Ingram 2019-04-04 01:38:36

Thx for this. I had issues using this code directly within plugins, seemed ok when it was one plugin but as soon as I did it with others (diff func names) I lost notifications for all plugins and the "view details" link for wp-repo plugins also disappeared. Using your checks but placing in my theme's functions.php has been more reliable without interference of update notifications for other plugins. Lastly, not being in the plugin has the benefit of not needing that plugin to be active for it to work. Disabling a plugin with this code will obviously present update notifications again.

@Hameedullah Khan 2011-06-21 14:44:01

For example if you don't want Wordpress to show update notifications for akismet, you will do it like:

function filter_plugin_updates( $value ) {
    unset( $value->response['akismet/akismet.php'] );
    return $value;
add_filter( 'site_transient_update_plugins', 'filter_plugin_updates' );

@Caleb 2011-06-21 15:20:36

I placed that at the end of ./wp-config.php, replaced the plugin file path and it did the job.

@Hameedullah Khan 2011-06-21 17:07:36

You can put that in your theme's functions.php if not possible then you can put in a separate plugin file. In my view putting this into wp-config.php is not a good idea.

@Caleb 2011-06-22 13:20:13

I don't really want my function tied to the theme, and adding a plugin seems like as much of a hack as just hacking the plugin I've got. Can you explain why you think wp-config.php is not a good place to put site specific configuration hacks?

@Lars Koudal 2011-11-13 10:28:15

Very good solution, which worked fine for me in functions.php. It is easy to add more plugins to the list simply by adding another unset()... Good tip Hameedullah..

@Hameedullah Khan 2011-11-14 06:18:29

Glad to see you here. :) I hope you remember me still. Wonderful that this tip worked for you.

@wordpress 2015-04-22 01:02:58

Worked perfect for me!! I'm so glad I ignored the other ones I was about to try and hack and kept searching and found this. PLUS, THANK YOU Caleb for telling me where to put this; at the end of wp-config.php IS the correct place! (NOT functions.php!)

@Charles 2016-10-06 13:34:24

For those with the same remarks as @Caleb, create in the wp-content folder a new folder named: mu-plugins and create a little plugin which you drop inthere. To add it as mentioned above by some in the wp-config.php is imho absolutely the wrong place to do.

@Gangesh 2019-07-18 10:38:34

It does remove update nag, but update message still remains.

Related Questions

Sponsored Content

1 Answered Questions

Plugin updates are not shown

  • 2015-10-10 07:55:17
  • amit singh
  • 3536 View
  • 3 Score
  • 1 Answer
  • Tags:   plugins updates

1 Answered Questions

1 Answered Questions

2 Answered Questions

3 Answered Questions

2 Answered Questions

[SOLVED] How can I stop a plugin being updated?

  • 2016-11-07 08:32:39
  • glvr
  • 102 View
  • 1 Score
  • 2 Answer
  • Tags:   plugins

1 Answered Questions

[SOLVED] Enable update notification, disable updates

1 Answered Questions

[SOLVED] How to update plugins with database updates if I use svn

  • 2014-05-23 02:39:49
  • Rebecca Dessonville
  • 219 View
  • 1 Score
  • 1 Answer
  • Tags:   plugins updates svn

1 Answered Questions

[SOLVED] Remove updates text on plugin or themes list page

Sponsored Content