[wp-hackers] How to mark a hacked file to skip update checks

Curtis McHale curtis at curtismchale.ca
Wed Aug 11 04:55:31 UTC 2010

I'm not sure if it's the recommended way but I move plugins that I've 
had to hack to my functions file. They don't show up in the plugin menu 
any longer so don't seem to get update notification, at least not that 
I've noticed. This also means that my clients can't deactivate it by 

Nathaniel Taintor wrote:
> Hi all... I've got a fairly basic question about best practices in hacking
> plugins or themes. (Yeah, I know its best not to do it at all, but sometimes
> budget or time makes it necessary... )
> My question is: what is the best way of marking a hacked plugin to keep it
> from checking for updates? Especially with the way the one-click updates
> work, I would really hate for a client to forget that I told them
> specifically not to update particular plugins and wipe out features that I
> worked hard to add in.
> I looked around and saw this blog post of Paul's talking about hooking into
> 'transient_update_plugins' to hide the update nag from specific plugins,
> which is a pretty neat trick:
> http://www.codehooligans.com/2009/08/30/disable-wordpress-plugins-update-indicator-for-inactive-plugins/
> But I would think it would make sense if there was an easier way to do it:
> say, a simple tag that could be added to the header to disable update
> checks. Is there anything like that out there?
> Than
> goldenapplesdesign.com
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

Curtis McHale


More information about the wp-hackers mailing list