1. mathetos

    It’s a testament to the Open Source Philosophy and the Plugin Review Team that this plugin was accepted in the Plugin Directory. Decisions not Options is a great philosophy that allows you to DECIDE to add more options, like adding a plugin like this. I can definitely see the value of adding role permissions settings for this plugin as I often told clients “Don’t Touch That!” with the “Customize” menu item even BEFORE the Menu Customizer came along.

    Nevertheless, the Customizer is a really powerful tool that “when used well” can be very effective. But — just like animated GIFS — it can be very abused very easily.


  2. just some thoughts..

    Go ahead. Fork WordPress. I give it 2 months before it’s completely abandoned.

    I am embarrassed in behalf of these two developers. They obviously don’t understand the database structure around menus. Menus are taxonomy terms that tie taxonomies and menu items (post objects) together. So menus are therefore not content. No ones opinion on them can change what they actually are.

    An easy fix that core developers could take is to make a ‘Customizer_Remove_All’ class. Then this ‘plugin’ would never load.

    I will never install a plugin or do business with either of the developers involved. They could hardly do anything more to put down and belittle the countless hours put into the development done here.


  3. Nile Flores

    I’ll be breaking out of the customizer for some projects, but for simple ones, I can see the feature as useful. As someone who is dyslexic (it’s a miracle that I can get through reading, typing, and coding to a degree), I’m not up for everything all smooshed into one area. It’s daunting to me. I’m sure I’ll get use to this as I have other things.

    Merging the feature in, and having an option to break out of it is nice. I like that option. I use a similar concept with updating by having Update Control by Chip Bennett in place so I can backup things before upgrading.


  4. Rob Neu (@rob_neu)

    I don’t really see any problem with what this plugin does or how it does it, but calling it WP CRAP is pretty crappy. I’m not exactly known for my restraint or political correctness and even I think this is over the line.

    Whatever you think of the customizer, a ton of work has gone into making it. A lot of that work has been unpaid. If you want to disable it, criticize it, fork it, fine. No issue. You still need to respect the people who built it.


    • mathetos



    • Andy Wilkerson

      The name was not intended to be a criticism. I’m sorry it’s been interpreted that way. We were having fun. It took a few seconds to come up with.

      I don’t care what the name is. It’s not called that on the WP repo so if changing the name on GitHub will make a difference I’m happy to do that.


      • Rob Neu (@rob_neu)

        I think that’d be cool. I’ve definitely said and done plenty of things that were supposed to be funny but could be interpreted horribly.

        I just know that if I spent who knows how many hours of my life working on something only to have someone make something to disable it while calling it crap at the same time I’d feel pretty awful.

        Disagreeing about code stuff is normal and healthy, I just try to remember that there are real people on the other end of the keyboard. Sometimes it’s hard and I screw up. We all do.


    • Andreas Nurbo

      Calling a feature etc crap does not mean you disrespect the people that made it. Things can suck but still be well coded and so forth. People making stuff you dont like can still be great people. Its a chock I know. It came as a surprise to me too.
      Honestly people need to stop putting WordPress on a pedestal. When your thoughts leaves your brain it its the worlds right to react as it please. Stop living your life by what other people think, stop being a puppet and cut those strings.


      • Miroslav Glavić

        It is part of free speech to call something crap. We need to stop kissing rear ends in the community. If there is something you (or anyone) doesn’t like then say it. I remember a while ago, there was a theme that made your site look EXACTLY like twitter, and another like facebook. I called those themes complete garbage, e-mailed the author, e-mailed WordPress, they were gone 2 weeks later when I checked again for them.


  5. tjpa

    WordPress by its very nature democratizes web site development by freeing us from the tyranny of programming. In the same way Customizer by its very nature democratizes WordPress development by freeing us from the tyranny of programming. Customizer makes many themes and the work of many theme developers irrelevant; so anti-Customizer vitriol from these threatened developers should come as no surprise. I think these anti-Customizer developers did not fully understand its subversive nature when they decided to develop for WordPress. Customizer is just one more step in this same direction. Thus to fully realize anti-Customizer philosophy, WP-CRAP should also upon activation delete the WP database and replace the WP Admin screen with a command prompt. In other words, a developer who hates Customizer does not understand what WordPress is all about. Developers who were able to make a business of creating simple-minded themes need to step up their game if they want to continue developing for WordPress. Creating plugins to delete WP are a fruitless endeavor.


    • Alec Kinnear

      Resistance is futile. We are the Borg. Lower your shields and surrender your ships. We will add your biological and technological distinctiveness to our own. Your culture will adapt to service us.


      At this point, WordPress enslaves business owners and web developers to endless updates which break functionality and endless security incidents which are not patched without functionality changes.


  6. krzysiek

    In almost all sites ive developped for my clients customizer had no use and so i disabled It by preventing clients user role from accesing It. This plugin may be helpful for devs who give their clients access to administrator role although the name is a bad idea. Still, thank you for the plugin.

    As for the argument on whether the creation of the plugin was a good idea or not i think It was. It is a yet another option in making wordpress turn into a more useful and user friendly system for some specific projects and use cases. Not every project even requires menus or posts!


  7. Ajay

    I think the next step would be to force the Menu system back, should it ever get removed as per the current plans…


  8. Webmaster7

    Thanks for this plugin. The idea to push the menu in a sidebar is just crazy.

    Many of my company websites use WordPress as CMS with 2-4 menus with upto 50 entries each, multilingual via WPML, editing such menu in a sidebar is no-go!


  9. Ov3rfly

    Thanks for this great plugin.

    The programmers of the customizer seem to have a simple blog in mind when they think about WordPress.

    But times have changed, since a while already.

    The customizer itself should be a plugin.


  10. Babi

    Excellent–can’t wait to use this plugin. There are laudable goals behind development of the customizer, but boy, I hate using it. Bravo, Petersen and Wilkerson.


  11. bradkgriffin

    Pardon my southern + US Navy + more southern verbiage, but I thought the name was an abbreviation of Customizer Remove All Parts. Consequently =>C.R.A.P

    Hell, I’d leave the name, turn off the innerwebs and go mow the yard if I were in your shoes!


  12. jonathan

    i personally just don’t think the customizer is user friendly enough to start putting multiple layered menus in. Having to click, then slide then click then slide Etc etc is really annoying. It’s easier to just have one screen that shows everything.

    I don’t mind having things like Jesse said, background image, etc, but one you start adding extra windows and extra clicks to do something simple, it starts to become too cumbersome.

    If it was a full front end solution then awesome, but it’s still back end with a big preview window and a small pane with everything squeezed in. Moral: just keep it simple, not everything has to be in the Customizer


    • accaonline

      Totally agree!
      I have used Customizer only because i had to. not because I wanted to.. and it’s annoying when it loads .. Glad that this new plugin will turn it off for good!

      How many times are people managing the site edit Site name? Header image? once it’s done.. it’s usually done.

      I am surprised, there is no built in option to turn it off though.. and that it needs plugin.. :(

      I agree what is said above.
      Wordpress DOES need a full front end solution – not what is currently offered in Customizer

      why wordpress does not buy and improve one of the cool front end plugin? Just like “menus’ feature was bought and integrated?


  13. Summer

    The problem isn’t the existence of the Customizer. I think it’s a slick idea for people with little to no CSS knowledge to make tweaks to their site layouts on their own, saving them time, and perhaps even some money because they can make the changes themselves instead of hiring a dev or designer for a few quick changes.

    The problem is WP setting things up and eventually forcing the Customizer to the be default admin interface for everything, which if you read the various updates and discussions and commentary is pretty much what they’ve stated they intend to eventually do, years down the road.

    Forcing the Customizer to be the admin interface by default for everything without giving people who are more savvy admins the ability to choose otherwise is the big issue, and I don’t see the Customizer becoming advanced enough to be that streamlined and efficient.

    This has nothing to do with the diversionary excuse “oh, this is just an educational issue, they’ll get over it”, which is incorrect, dismissive, and blatantly disrespectful of the people trying to point out the misguided all-or-nothing attitude of “The Customizer Is Mother, The Customizer is Father” that the people making decisions seem to have adopted, needs some fine-tuning before going forward.

    It’s that dismissive and seemingly intentional deafness towards what the Customizer complaints really are about that has me confused. It’s not that difficult to see, and the fact that so many of us who have been pointing out the shortcomings are called out as being luddites or afraid of change and other childish names borders on arrogance. The folks pointing out the shortcomings aren’t the ones sticking fingers in ears and yelling LALALALALALA while ignoring the concerns of a lot of smart people.

    The Customizer has its uses and functions, but as a complete replacement for the admin interface for everything is IMO definitely not the way to go. But that’s where we seem to be getting pushed towards, for no clear reason why other than “gotta compete with Squarespace”.

    If that’s the vision, then make Customizer the default for WordPress.com and let the millions of people with self-installed sites who have legitimate concerns about how Customizer will affect the administrative functionality of their sites have an option to go a different way.

    At this point, it may be moot. 3-5 years from now, all backend admin functions will have been shoehorned into the Customizer, there will be a few dozen plugins that will switch the admin interface back to something more usable for those of us who prefer functionality over “drag & drop & make pretty only” content management, and the Customizer arguments will continue until the end of time, while many of the media management issues that have gone unremarked upon for years will still exist.


  14. Mahee Ferlini

    I’m looking forward to seeing what direction this takes in the near future. Many interesting points to consider. This does add options though. Thank you!


  15. Miroslav Glavić

    I started to love and prefer the Customizer, over the theme options option. I noticed so many theme authors over advertise all their other products on the theme options. stop doing that.


  16. Greg

    Love this, I use it on just about every site.

    I noticed without the customizer you can’t get to any settings for the site icon – which is used by 4.4 for the icon in the embed feature, amongst other things.

    I customized the old Jetpack Site Icon Module into a standalone plugin that moves the site icon option to the general settings page.

    Hopefully this helps others locate their site icon after disabling the customizer



Comments are closed.

%d bloggers like this: