Disable Over a Dozen WordPress Features With the No Nonsense Plugin

One of the best things about WordPress is the hundreds of ways of turning things off. There are likely dozens of plugins for disabling various items, each with its own unique set of options. No Nonsense is no different. It is a plugin that allows users to control whether they want to use over a dozen features.

The plugin was developed by Room 34, a Minneapolis-based web development and creative consulting studio. No Nonsense is the team’s 11th free plugin available through the WordPress.org plugin directory.

The team’s plugin caught my eye because it has options for features that I routinely disable on WordPress site builds, such as emoji JavaScript, individual dashboard widgets, and the toolbar. Today’s update (version 1.2) even added an option to permanently remove the Hello Dolly plugin.

Before anyone asks — someone always asks —, the plugin does not disable the block editor. However, it does have an option for turning off the block-based widgets editor.

Room 34 released the plugin on Tuesday, so it has fewer than 10 active installs at the moment. It also does not have any reviews. I suppose this post will suffice as the first. Based on my experience and a peek at its code, the plugin looks solid.

Screenshot of a WordPress admin settings screen for the No Nonsense plugin.  It has a list of checkboxes for disabling various features.
Plugin settings screen.

I tested each feature and did not find any issues, so it gets a 5/5 for doing what it says on the tin. I would love to see a few more options. One example that immediately comes to mind is the the “Posts” screen. Since users can remove the “Comments” section in the admin, it makes sense to have a similar setting for posts. Both are related to blogging, and not all WordPress websites need them.

No Nonsense includes one of my favorite admin-access limitations. It can redirect logged-in users to the homepage when accessing anything other than their user profile in the WordPress admin.

Its toolbar options are all things I have lying around in my code toolbox. The plugin has settings for hiding it for users without editing access, removing the WordPress logo, and ditching the “Howdy” text.

The plugin includes options for many commonly-disabled features, but a new one that I had not thought about was the core update email. When managing sites for several family and friends, those “your site has updated to WordPress x.x.x” emails can become irritating. The plugin allows you to disable those except in cases of an error.

If someone has not already done so, I would love to see a deactivation plugin to end all deactivation plugins. It would feature a complete list of things that a site owner can turn off, disable, deactivate, remove, or whatever you want from a WordPress website.

No Nonsense looks like a good starting place, but there are always other things that I might remove from an install. I almost always give the ax to the theme and plugin editors. As well as the plugin works, there’s always just a little something more I need to get rid of, depending on the site in question. So, I am still looking for that behemoth plugin that gives me that one-click access to disable anything. For now, I can see myself deploying this on a few sites.

37

37 responses to “Disable Over a Dozen WordPress Features With the No Nonsense Plugin”

  1. I use Daniele De Rosa’s WP Disable Automatic Updates plugin and turn all automatic updates off. Thus I don’t get the “your site has updated to WordPress x.x.x” e-mails.

    Yes, I do keep my sites updated. I do manage A LOT of sites for friends, family and clients. I keep an excel sheet with what plugins are installed in each site so let’s say Akismet is on site 1, 3, 4, 200, 310 and 501……….I only go to those sites when I see an update on for Akismet.

  2. Perfect! I was thinking about this type of thing again recently and wondering if there is a master list of everything that can be (relatively easily turned off) — and if there is a significant performance gain in doing so. I’d love to learn more about this.

    It’s been on my list for a while to figure out just how much can be shut down to provide the most minimalistic WordPress experience possible.

  3. Great Post!
    This is so relevant stuff.
    I never really understood why WP, especially in recent times where performance has such an impact on the web, never put something like this on core. Or, even better, why the WP installation doesn’t come completely clean and light.

    And now, where the creation of websites/apps with it’s becoming less code/developer intensive, it could be even more a core strategy.
    I will definitely install this in all my sites – congrats to the authors.

    And a big thanks to you for discovering these gems and for testing them to the core bones – something I don’t really know how to do and always makes me anxious before installing a new plugin.

    About automatic updates, they are essential, they should always be on. But they can cause damage. Why isn’t there a way, in core, to rollback to a previous stable version?
    Maybe there could be a log file (last to be read on the site, to see if everything is working?) which keeps track of all installations (core + plugins) and sends a message to the admin if something is wrong and with a “click here to restore” option – it could even have different restore points according to latest installations?
    Probably this isn’t possible or it’s a nightmare to develop but it sounds good.

    • WP-Rollback from the smart folks at Impress.org provides the rollback functionality you’re referring to, as long as the theme or plugin is from the WordPress Repository.

      It doesn’t have the overall automation that you’re looking for, but as a quick way to manually roll back when unexpected update issues arise, it’s helpful and straightforward, compared to having to find and reupload previous versions.

      • Thanks for the suggestion!
        Not sure if it’s what I was thinking but I’ll give it a try!
        I suppose you have to login to WP to access it? My idea was when your site crashes with an auto-update and you can’t access the dashboard. I’m not sure if this still happens but you get the idea.
        In this case, you would receive an email with a quick link warning you to restore it.
        And it just came to my mind we could chose the preferable hour for auto-updates just for less impact on site downtime.

  4. Disabling that core update email is kinda foolish. As is letting WP update automatically. These updates sometimes break the layout and/or functionality of websites. Best practice is to test the update on a hidden test version of the websites before rolling out the update on the live website.

    • All of the settings in the plugin are optional, and it only disables the emails if the update runs without an error. I have a ton of clients who are set up as admins on their sites and they are at best confused and at worst annoyed when these emails come through.

  5. It’s s great idea, I have quite a few different lines of code in functions PHP and plugins to reduce bloat from WordPress to try and squeeze extra performance from the site . Having an all in one solution is better! Will have to give it a try.

  6. That’s an interesting one. I don’t like messing with wordpress code so I find myself needing many different plugin to disable some of these features that the plugin can help with. One plugin that does it all sounds like an interesting one. Will give it a go.

  7. (No Nonsense dev here)

    Thanks for the great review! I’m pretty excited about this plugin. I had never bothered to create something like this AS a plugin, because I had a custom starter theme I used for all of my clients in which I had already stuck most of this functionality. But I’ve been moving away from using that starter theme — long story — and I realized that I needed to encapsulate all of these handy features in a plugin for myself.

    I’m pleased to see the positive response it’s getting, and yes I dream of this being the “deactivation plugin to end all deactivation plugins”… so please offer suggestions for new features you’d like to see! (The WordPress support forums are the best place for that. I’ll see them for sure.)

    Version 1.4.0 is out now, with a bunch of new features including the ability to selectively remove a bunch of the link tags WP sticks in the head of every page.

  8. So it’s not just me to gets annoyed with the “Howdy”! As a German speaking WP user who grew up learning British English, Howdy always makes me feel like I’m a Western movie where I should have a horse tied up outside ready to ride into the sunset …

    • Obviously I am in favor of removing “Howdy” altogether, but it is probably worth noting that you can change the system language (under Settings > General > Language) from the default “English (United States)”. If you switch to “English (UK)”, for instance, it says “Hi” instead of “Howdy.” And if you switch to “English (Australia)” it says “G’Day.”

      I’m planning to modify No Nonsense in a future update to be i18n aware and remove the greeting term, no matter what the system language is set to, but for now, I know “Howdy” is the thing that really irritates people.

      • FYI, in a german WordPress also with the current No Nonsense plugin release, the term is already translated “Willkommen” in No Nonsense plugin settings but not removed from admin bar.

        Simple fix, replace this line:

        'title' => str_replace('Howdy, ', '', $my_account->title),

        With this line:

        'title' => str_replace(str_replace('%s', '', __('Howdy, %s')), '', $my_account->title),

        Problem solved no matter what the system language is set to. And you might want to get/print the correct term from __('Howdy, %s') for plugin settings description as well.

        • Thanks for the suggestion… I actually just rolled out version 1.5.0 which accomplishes the same goal in a slightly different way, by stripping all text before the span tag that contains the user’s display name. (Of course, this doesn’t address languages where the greeting might come after the name, so your suggestion might be better.)

          I have a feeling though that there’s a world of difference between wanting to remove the greeting in general, vs. specifically wanting to remove the word “Howdy” from the U.S. English version. :D

    • The plugin is open source, you can see and take any functions you like from there and use them for your needs.

      Publishing copy&paste snippets is not advisable as then people without any clue about what is going on will copy them to some code snippets plugin or any other place where they might not work as expected or break their site. Been there, seen that, code copied to wp-includes/functions.php and similar…

      The (very low) “hurdle” of knowing how to look into plugin source code is actually a protection for clueless (not in a negative way) people.

Newsletter

Subscribe Via Email

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