Cancel

Jeff Chandler

Removing The Browser Nag Bar In WordPress

Scott Reilley who also goes by Coffee2Code is continuing his trend of releasing small but useful plugins for niche audiences. This time, he has released a plugin called No Browser Nag that removes the Outdated Browser nag found within newer versions of WordPress.

WordPress Browser Nag

While it’s a bit foolish to condone the use of outdated browsers, sometimes users don’t have a choice. At least with this plugin, that user group will be able to remove the constant nag and allow WordPress to get off their backs about a situation they may not be able to control. However, if possible, you should upgrade to the newest versions of your browser of choice as they often contain important security updates, performance improvements, etc.

Category:
Tags: , ,
10

10 responses to “Removing The Browser Nag Bar In WordPress”

  5. I used IE 9 to test out whether I would see the nag bar or not and I didn’t see it. Because of that, I also didn’t see the screens options area where I could simply remove the nag box which I thought you could do in earlier versions. If that’s still around, it definitely negates the need to use a plugin.

    Create forum topic from comment
    Reply

  6. @Kevinjohn Gallagher – Your blog post rant there, while entertaining, misses some of the point.

    IE6 and IE7 are actually insecure. There are known security issues that can happen because somebody is using IE6 and IE7. This is why they are being deprecated.

    Even Microsoft wants people to stop using IE6.

    Other points such as the problems with browser detection and so on are well-taken, however there are still fundamental underlying problems. Some older browsers really are actually insecure. We know this. It has been demonstrated. This is one of the reasons IE6 support was dropped from the WordPress admin entirely, and also why IE7 support is slated to be dropped as well (not in 3.3, it didn’t make that.. maybe in 3.4 or 3.5).

    Windows XP is 10 years old, and will be at its end-of-life in a bit over 2 years from now. It’s time to upgrade your OS too. I realize that you don’t like the whole idea of upgrading, but it’s a fundamental fact in computing that isn’t going to go away just because you and your clients don’t like doing it.

    Adapt. Or die. Either way is fine.

    Create forum topic from comment
    Reply

  7. @Kevinjohn Gallagher – Kevin, about the only thing that felt right about your “Browse Crappy” post was your proper spelling of “colour” (all the Americans are simply doing it wrong); the rest was like a knife to the heart.

    Yes, it’s not a pleasant era to live in where non-computer-savvy people are forced to click past warning dialogues, but if people don’t put their foot down sooner or later, it’s never going to end.

    I’ve purposefully dropped support for IE6 in my development work unless the client’s explicitly chosen to pay for the backwards compatibility. Seeing a warning message – as well as an unsightly mess of a website, should be enough to get the point across to the user.

    IE6 has to die sooner or later. It’s not about convenience (“I’m old and I prefer the bigger buttons of IE6, hurrr hurrrrrr”) – it’s a case of people letting go of old technologies.

    Create forum topic from comment
    Reply

  8. @Otto –

    Otto,

    You hopefully know how much I respect you, and I think we’re both fully aware that we’ll never see eye to eye on everything ;) but I think this is a really great microcosm for the disparage between us :)

    1) R U SRS Bro?
    We have a singular functionality, with a sole purpose to detect a user’s browser and tell them if it’s not the latest version, and… it doesn’t work.

    “problems with browser detection and so on are well-taken”

    I really appreciate your openness about this, as always, but come on. Given that most of the time this functionality fails with people using IE, and that the target audience is for… people using IE; doesn’t make this piece of functionality Not Fit for Purpose?

    It’s a browser detect that can’t accurately detect browsers.

    But we’re not making any attempt to fix it because, well it can’t target people on Macs, so who cares…

    2) Upgrading and the Veil of Ignorance

    I realize that you don’t like the whole idea of upgrading, but it’s a fundamental fact in computing that isn’t going to go away just because you and your clients don’t like doing it.

    I apologise if I’ve given you the idea that I don’t like upgrading, or being on the latest version appropriate of whatever software I’m using, I’m personally a bit of a beta bunny.

    But the rest of the world is not. If it was would we have to do all of this? Um… I’m being vague here to stay within NDA: One of my current clients received close to the same number of hits as Amazon and eBay last year (outside of Christmas and some holiday y’all have in November), and will probably do similar this year (maybe a little less). 41% of their traffic in the last 12 months came from people in WindowsXP. IE6 and 7 made up more than 30% of the browser share.

    I absolutely understand that’s just one website, but when comparing those numbers to the 500+ other websites in the company, the percentage of WindowsXP and IE6/7 didn’t drop below 40 and 20% respectfully.

    I fully understand that this is somewhat anecdotal, and it’s just one website, I do get that; but when those of us out in “the real world” are looking at that sort of statistic over and over, from site to site, from company to company, from country to country, it’s hard to get behind this idea that it’s just me or my clients that don’t like doing it.

    3) OS upgrading

    Windows XP is 10 years old, and will be at its end-of-life in a bit over 2 years from now. It’s time to upgrade your OS too.

    So I agree with the premise, but that argument isn’t really what people hear. To start with, end-of-life means nothing to the man on the street. What they hear is this:

    Windows XP is 10 years old, and Microsoft will no longer support it in a bit over 2 years from now.
    It’ll still work in the same way it does now, and the way it has done for 10 years, but it won’t be “officially supported”.
    You therefore have a bit over 2 years to pay to upgrade to the latest version of your Operating System, which will cost you about $100 – but if you pay for it now, note that you’ll not be on the latest version of the operating system next year when Windows 8 comes out.

    That’s what people like my Mum hear.

    When we techies hear 10 years old we think “holy crap I need to upgrade” but non-techies think “wow, that’s really stable, I’ll stick with that”. When we techies hear 2 years until end-of-life we think “holy crap I need to upgrade” but non-techies think “wow, that’s far away, I’ll save my money and maybe get something closer to the time”.

    4) The bubble

    So this is where we’ll disagree the most I think. We have 20,000 people who make a living from WordPress (according to your boss) – that’s an awesome number.

    But it gets harder to really sell WordPress to both individuals and companies who are resistant to change. I understand “Adapt. Or Die”. I’m a certified and practicing Scrum Master, Product Owner and Practitioner – I understand the premise of Agility from Darwin to XP programming. But it’s really hard to go into a company – of any size – and see people using IE or Windows XP/Vista, or have disabled people, or blind people, or know they current have an IIS server or any of the other types of people we’ve moved to edge cases we don’t really like; and attempt to say hand on heart, WordPress is the right software for you for the next 2 years.

    And I think thats the bit that you’re missing bro. If you/the-core-team/matt/Automattic/WordPress all don’t want to support IE6, IE7, WindowsXP or anything else – I’m ok with it. I may not agree with it, it may result in me using WordPress less, but it’s not my call. But how many users of WordPress, or any software, like being told off and having something added to the software they’re using that reduces the User Experience. It doesn’t come across as attempting to be helpful, it comes across to the end user as being an arrogant superior techie jerk.

    It’s hard to want to use software that constantly moans at you for something you may not be able to change.

    5) Finally

    If I may, another Anacdotal reference…

    My mother, a woman who used to code Pascal and Cobol, but really never liked computers (yeah, I know) recently asked me to uninstall that “web thing, that kept p*ssing her off by telling her to upgrade constantly when [she] only upgraded last week”.

    So Firefox 7.0 was removed from the computer, and she’s back using IE8.

    Efforts to move her to Chrome or IE9 were met with: “But doesn’t [ie8] do everything I want it to do?”. I had many arguments for IE9, but you know what, IE8 does what she needs it to do, and it already is on her machine, and it works. Sometimes, we techies focus on the cool new things a bit too much.

    Create forum topic from comment
    Reply

  9. @Alhadis –

    Yes, it’s not a pleasant era to live in where non-computer-savvy people are forced to click past warning dialogues, but if people don’t put their foot down sooner or later, it’s never going to end.

    This is where I really disagree. I’m 100% ok with dropping support for anything that you don’t want to support. If WordPress doesn’t want to support IE7, then thats cool.

    But to nag and moan and more importantly, stop people using the software, because we don’t happen to like the browser or OS you’re using… it’s close to childish.

    It also completely ruins the User Experience for “non-computer-savvy people”, which is funny given that the WordPress core now has a UX person on the core team (it’s ok, she only tests on Mac’s anyway, it’s how the WP3.3 beta was released with a menu that didn’t work on IE, oh obviously there’s no testers in the core team either).

    I’m not saying you have to support anything you don’t want to, but obey Wheaton’s law: https://twitter.com/#!/wilw/status/5966220832, and honestly, that HUGE browser nag thing really breaks it. Especially with all the false positives, and the fact that the browser detect, y’know, can’t accurately detect browsers… /facepalm

    Seeing a warning message – as well as an unsightly mess of a website, should be enough to get the point across to the user.

    It does, it says “don’t use this website”.

    It doesn’t say ” wow dear, this website is right, I had better upgrade my browser, i should listen to websites and banenr ads more often, whats this? vi*gra? I’ll click that, oh what now? you want my password – ofc – i mean, all people belive banner ads, especially because its in Red. Wow, I’ve won first prize, I’ll click everything I see…….”

    We’ve spent 10 years teaching people to ignore big bright things that tell them to upgrade. especially if they look like banner ads. it is, frankly, muppetry to believe that they’ll magically trust this annoying banner ad because it’s near the WordPress logo!

    Create forum topic from comment
    Reply

  10. I am using Firefox 7.0.1. Version 7.0 was first released on September 27, 2011. Three months old, and it’s out of date?

    Mozilla kinda strained my credulity, with the rapid release routine. I let them auto-update a few times, then decided I’d do manual updates at more reasonable intervals.

    Three month old Firefox is a security issue? Something legitmately worth theatrics in my Admin?

    I’m not convinced.

    Create forum topic from comment
    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

You may also like

Newsletter

Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Discover more from WP Tavern

Subscribe now to keep reading and get access to the full archive.

Continue reading