How to disable JetPack nag messages in the WordPress Admin interface

I really like WordPress, and I really like JetPack. I use the plugin on many client websites, who usually have their own WordPress.com  account, which is necessary to enable the plugin successfully.

Most of them however choose not to sign up for a payment plan, which as of 2017 leads to (now rather annoyingly frequent) JetPack upsell messages at the top of the admin screen. So I as the administrator, am constantly exposed to such messages, and I was wondering how to suppress them – not being the target audience here.

Thanks to a super helpful article by Matt Medeiros I found a great solution with this one-liner of code he as kindly supplied on his website, together with his opinion on such messages:

Add this to your child theme’s functions.php file and those admin nags are history!

Thanks Matt!

About Jay Versluis

Jay is a medical miracle known as a Super Survivor. He runs two YouTube channels, five websites and several podcast feeds. To see what else he's up to, and to support him on his mission to make the world a better place, check out his Patreon Campaign.

10 thoughts on “How to disable JetPack nag messages in the WordPress Admin interface

    1. Ay caramba! Thanks for letting me know 🙂
      It seems to work fine with a single underscore, what’s the difference? I must admit that I’m not familiar with that notation in this context. I’d expect something like just plain “false”.

      1. The second argument in a hook is a function name (“callback”) to invoke. In this case, __return_false() is a special function in WP Core that does exactly as it says—returns FALSE. The reason it was likely working in spite of the mistake is that a bad function name would produce a notice/warning, but not a fatal error, which in either case is enough to change the TRUE value originally passed to the filter to something other than TRUE, causing it to abort execution.

        1. Ah, thank you so much for clarifying this – it makes perfect sense. I would have probably seen those warnings with DEBUG mode on, which was not active. I really appreciate you taking the time to share this 🙂

      1. D’oh!
        Thank you so much for bringing this to my attention – sometimes WordPress does weird things when pasting code. I’ve corrected the code above!

Add your voice!