Comments on: Prevent Update Checks for a WordPress Plugin

By: Thany

Thany — Sat, 23 Apr 2011 16:07:57 +0000

Oops, my bad. I didn’t realize WP only checks once every 12 hours, unless something has changed. Good to know, since it’s only hidden deeply in the source code and not mentioned on the plugins overview.

By: Thany

Thany — Sat, 23 Apr 2011 15:58:20 +0000

It doesn’t seem to be doing anything…
I just pasted the code at the bottom of my plugin file, and *even* putting a var_dump() in the function doesn’t output a single extra character. Seems the filter function is never called. What gives?

By: mahalie

mahalie — Thu, 24 Mar 2011 01:55:47 +0000

Hi, thanks for your script. Love it. Word of WARNING to others: make sure you change the function name if you use this on more than one plugin. Yeah, I’ve been hacking plugins – I know it’s not ideal but for some reason no one does exactly what the client needs!

So my little mistake of using the same function name in two plugins got me thinking. Is there a way to this to the next level and create a plugin that disables other plugins? It seems like if you can disable all updates including core update notification one should be able to write one would list all plugins (installed or not) and selectively control update notification for each?

By: eve

eve — Thu, 10 Mar 2011 18:31:19 +0000

thanks! You just saved me a ton of work from having to go re-add code everytime my client updated the darn plugin herself lol

By: chuck scott

chuck scott — Sun, 06 Mar 2011 17:23:13 +0000

Hi Pete – this function is great and works in MultiSite 3.1 network provided that the plugin php file exists in the root plugin folder – i.e., in the wp-contents/plugins/ but if in a folder further south, e.g., wp-contents/plugins/my-custom-plugin-dir/ then it does not work and the auto check for updates still continues to run …

e.g., i hacked the CIMY User Manager plugin for my own import needs and the plugin typically gets installed in a folder called “cimy-user-manager” which is then subset of the plugins folder … hacked plugin runs fine yet when i put your function in the main php file (ie., cimy_user_manager.php) then the auto check for updates continues thus your function does not work while in that sub folder … if i move cimy_user_manager.php to the root plugins folder, then your function does work (meaning it stops looking to be updated) …

thus i’m not sure if your $my_plugin variable needs to be prepended with the plugin directory or ..??..

regardless, muchisimo gracias for sharing as it certainly helped me for now and only share as fyi in case this sub-folder thing might be issue for others ..??..

cordially, chuck scott

By: Pete Mall

Pete Mall — Sat, 10 Jul 2010 00:21:34 +0000

Works with 3.0. You may be doing something wrong.

By: Pete Mall

Pete Mall — Sat, 10 Jul 2010 00:21:19 +0000

Yes, the plugin needs to be activated for the code to work.

By: Peter Verkooijen

Peter Verkooijen — Sat, 10 Jul 2010 00:09:48 +0000

Doesn’t work in WordPress 3.0? Or am I doing something wrong…?

By: Arne Seemann

Arne Seemann — Tue, 06 Jul 2010 11:41:27 +0000

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

By: Hanna Jones

Hanna Jones — Tue, 15 Jun 2010 13:12:18 +0000

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!