• WordPress is a really good script!

    There is just 1 thing I think is pretty annoying and that is in the admin panel I can see like “update to 2.7.1” etc on three places… at the admin “start page”

    Wouldn’t it be enough with one “update info” text?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Well, considering that you have yet to update, then apparently even showing it in three places is not enough.

    It’s telling you to update because you need to update. If you didn’t, it wouldn’t tell you that any more.

    You can make a plugin to suppress it. I’m only a beginner with PHP stuff and plugins, etc., but I took a look at at a plugin called Admin Themer, and used that as a basis for adding a stylesheet to the admin header.

    Here’s how your custom plugin might look:

    /*
    Plugin Name: Suppress upgrade nag
    Plugin URI:
    Description: get rid of upgrade nag
    Version:
    Author:
    Author URI:
    */
    
    function suppress_update_nag () {
    print "<link rel='stylesheet' type='text/css' href='";
    
    bloginfo('template_directory');
    
    print "/suppress_nag.css'";
    
    print " />\n";
    }
    
    add_filter('admin_head', 'suppress_update_nag');
    ?>

    This filters the admin_head (used in the admin pages) and adds a link stylesheet in your theme folder called “suppress_nag.css” to the header of the admin pages.

    Then, in your theme folder, you put the stylesheet “suppress_nag.css”:

    /* disable main update nag
    leaves plugin nags alone  */
    
    #update-nag, #update-nag a {
    	display: none;
    }

    This particular one leaves the plugin nags alone, because I wanted to retain them.

    If you look in the wp-admin folder, you’ll find a stylesheet called “wp-admin.css”. That controls the styles for the admin pages. ARound line 554 (I’m using WP 2.6.5), you’ll find the styles for the update nag. In my stylesheet above, I simply told them not to display.

    The advantage of doing it this way is that it doesn’t alter any core files — it just filters the head and calls on a stylesheet in your theme folder, which won’t get overwritten when you do upgrade.

    You can use this technique to change various css aspects of your admin panels.

    Use at your own risk, obviously — there’s an inherent security risk in not using the most up-to-date WP version. Personally, I’m quite aware of what version I’m using, but I didn’t want the nag to be there for editors and authors, etc., and especially subscribers visiting their profile (why the hell should they be told to advise the admin to upgrade?).

    Thread Starter Felix J

    (@felix-j)

    I would be aware that I had a older version of wordpress than the latest version with only 1 update notice… so it would be enough. I dont think having three update notices will make more people updating to be honest…

    For example the update notice at “top of screen” is kinda impossible to miss in my opinion so that one would be enough.

    I am writing this to make my opinion more clear.

    By the way, thanks StrangeAttractor for the code input.

    Hey,

    If you want to also supress the plugin upgrade notices you can change the CSS to the following (I just FireBugged the page to find the classes for the plugin nags):

    supress_nag.css:

    #update-nag, #update-nag a, span.update-plugins, td.plugin-update {
        display: none;
    }

    I am doing this since I have modified some plugins’ code and don’t want any other admins to auto-upgrade and overwrite my changes. To find out if there are any plugins that need updating just deactivate the ‘supress nag’ plugin to see the notices, and then re-activate it again when you’re done.

    Matt

    I always use the disable-core-update plugin to suppress these messages. I build websites for clients and I do not want them asking me about why they are not on the latest release. If the websites are already serving their function without any problems, there is no need to upgrade. WP 2.6 is still a good CMS.

    It is not a big deal since it is easy to get rid of the nags but if it were up to me, they would only be displayed to an admin user and there would be a setting to turn them off.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘One thing that is annoying…’ is closed to new replies.