Support » How-To and Troubleshooting » [Resolved] Disable ‘A new version of WordPress is available! Please update now.’ message

[Resolved] Disable ‘A new version of WordPress is available! Please update now.’ message

  • Where can I disable the message: ‘A new version of WordPress is available! Please update now.’ in my wp-admin?

Viewing 15 replies - 1 through 15 (of 19 total)
  • Anybody can help me please?

    Why do you want to disable it? Isn’t a good feature to give you a friendly reminder!


    Yes, but I don’t want to update to every new verion it’s comming out. The 2.3 works fine. And when there is a new update I see it fast enough on my dashboard page. So how can I disable this function?

    This should work:

    in wp-admin.css, add “display: none;” to #update-nag

    This plugin should do the trick:


    Although, please do not have the attitude of “it works fine for me, why should I upgrade?”. WordPress 2.3.1 was released because WordPress 2.3 has security issues and by not upgrading, you are creating an opportunity for crackers to crack your blog and deface it or create spam links, contributing to the spam problem.

    Thanks. It works.

    Keeping a single blog up to date is becoming a job in itself, but managing over 30 is just incredibly soul destroying. I’m not sure how many more ‘updates’ I can take.

    Why don’t you care about keeping your blog safe, secured and updated?

    I’m of the opinion that every major release (such as 2.3) should already be safe and secure!!!

    If a release isn’t ready to be stable for at least 6 months it should be beta tested for longer. WordPress are updating with security fixes more than bloody Windows these days. At least Windows has the courtesy to automate its process.

    Re. SpencerLavery:

    I’m of the opinion that every major release (such as 2.3) should already be safe and secure!!!

    That is an incredibly naive attitude, and evidences complete ignorance of the realities of running an interactive web application.

    First of all, “safe and secure” entails two very relative adjectives; how safe and secure… and safe and secure from what, exactly. The internet is a “wild and woolly place”, with new exploits developed and revealed continually.

    Secondly, “nothing” accessible over the web can ever be completely “safe and secure” in the strictest sense of the words; it’s all a matter of risk mitigation.

    Finally, you should view security related updates a a necessary step due to the “arms race” nature of the ongoing struggle between developers and those that would exploit the applications they create. Today’s “safe and secure” application is rendered vulnerable when the bad guys find a weakness, the developers identify the attack vector and provide a fix, and the process repeats itself on an ongoing basis.

    Sure, updating can be an aggravation at times, but that is not nearly as “aggravating” as the damage suffered from leaving “unpatched” vulnerabilities in the wild to be exploited. I’m thankful WordPress developers release, as they need, to plug security vulnerabilities. To me, this is much more important than features.

    Ultimately, the choice of whether or not to upgrade, or when to upgrade, is up to you but you should be aware of the risks you face if you refuse to except that an application you are running is vulnerable and just bury you head in the sand. 😉


    Even if I

    Who is burying their head in the sand???

    I’d like to see you try to keep over 30 blogs up to date and not get frustrated by the short lives of each release.

    We predominantly use custom build CMSs where I work, and have over 100 deployed, most of which for years, and are yet to experience any ‘security’ problems. It is entirely possible to create safe and secure web applications, and if running WordPress is “vulnerable” to quote you, then I think it’s high time we all switched over.

    I think the WordPress devs would have a fair amount to say about that claim of yours.

    I’m not complaining about having to update anyway, I’m frustrated by my clients seeing a “your WordPress is out of date” note without any prior knowledge, features like that should be marked clearly on the upgrade page to give people like me time to prepare themselves for the barrage of 30 panic-stricken phonecalls.

    I’m sorry but if you think having to go through a complete upgrade every single month is acceptable for a web app then you’re the one that is naive and ignorant, and have clearly never worked with a professional web application in your life. I accept the shortcomings of using a popular open-source app, but don’t tell me all apps are like this because they’re simply not (used Expression Engine lately? Mephisto? Light CMS?). You’re a fool for thinking so.

    Wow, I must have struck a sensitive note there, eh? The WordPress devs have made it clear how they feel about vulnerabilities with their recommendations to upgrade to address potential vulnerabilities.

    I occasionally get frustrated with having to update the 20 or so blogs I maintain on a regular basis (and the 30 or so CMS applications), but it’s a part of the business we are in. I’d still rather update than run “unpatched” and expose my clients to potential exploits I could have mitigated had I not been too lazy (or greedy) to update when I could have.

    Your lack of having experienced “any security problems” has nothing at all to do with whether vulnerabilities exist; it only shows that you have not been exploited. Congratualtions! Hopefully, you will continue to be able to report such fortuitous experience in the future.

    I stand by what I’ve written; *you* decide when, and if, it is appropriate or desirable to upgrade your installation. Thankfully, the WordPress devs have a more realistic perception of threats to online applications than you do and continue to release security related updates as often as they deem them to be necessary.

    If you can’t be bothered, then don’t update and continue to dance with the devil hoping that you will never have to explain to those “over 30” blog operators why their sites were exploited via a known attack vector that could have been mitigated had their sites been kept up to date. Good luck with that, seriously!

    Final point: If you don’t like your clients seeing that they are running “less than current” or “out of date” versions of WordPress, you can always take advantage of the Open Source nature of WordPress, and the license under which it is released, by removing those warnings. Alternately, you could even roll up your sleeves and code an automated update script so you could upgrade all those blogs much more easily (see the DreamHost “one-click” installer/.upgrader for an example).

    *That’s* what many who routinely “work with professional web applications” do.

    Meh – “professional”, “fool”, “naive and ignorant”, whatever. You perceive the security issues one way, I perceive them in another. We have different experiences on which to base our perceptions. PAX

    Discussions like this are good, but try to play nice. Let’s not get this thread closed because of that awful forum virus, inflame-uenza.

    Kafkaesqui –

    Point taken, and I apologize for any inflaming verbiage. Dialed back immediately, and thanks for the reminder.

    Yeah apologies on my part also – I wasn’t best pleased at being accused of being naive, ignorant and burying my head in the sand.

    But back to the discussion at hand:

    I agree that security vulnerabilities need to be patched as soon as they’re made aware of – but I as the developer would rather know about these issues/upgrades BEFORE my clients do. Historically I’ve done that by checking the WordPress site often, and that is something I’m more than happy to do.

    I don’t think that that is an unreasonable request at all.

    Hacking the ‘open-source’ WordPress is all well and good until one month later I *need* to upgrade and re-do the hacks completely. As I’m sure you’re well aware, when it comes to managing 20+ installations, even remembering which hacks you’ve implemented on which blog is a task in itself.

    Note: I should point out that the majority of these clients have no on-going maintenance contract with us, therefore keeping these installations up-to-date is a free, courtesy service that is increasingly eating more and more of my time. Where to draw the line with regard to support and ‘secure’ applications is very blurry in this case indeed.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘[Resolved] Disable ‘A new version of WordPress is available! Please update now.’ message’ is closed to new replies.