Title: No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor Author: Fernando Tellado Published: 18 aprilie 2018 Last modified: 25 august 2026 --- Caută module ![](https://ps.w.org/no-gutenberg/assets/banner-772x250.jpg?rev=3633802) ![](https://ps.w.org/no-gutenberg/assets/icon-256x256.jpg?rev=3426834) # No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor De [Fernando Tellado](https://profiles.wordpress.org/fernandot/) [Descarcă](https://downloads.wordpress.org/plugin/no-gutenberg.2.3.2.zip) [Previzualizează live](https://ro.wordpress.org/plugins/no-gutenberg/?preview=1) * [Detalii](https://ro.wordpress.org/plugins/no-gutenberg/#description) * [Recenzii](https://ro.wordpress.org/plugins/no-gutenberg/#reviews) * [Instalare](https://ro.wordpress.org/plugins/no-gutenberg/#installation) * [Dezvoltare](https://ro.wordpress.org/plugins/no-gutenberg/#developers) [Suport](https://wordpress.org/support/plugin/no-gutenberg/) ## Descriere The most configurable way to leave the block editor behind. Activate it and everything block related is gone: the block editor, Global Styles, patterns, block widgets, the Site Editor and the block CSS and JavaScript that every page loads. From there you decide the scope: everywhere, or only for the post types, roles, templates and entries you choose. **What this plugin removes:** #### Core Gutenberg Features * Gutenberg Block Editor (completely disabled) * Full Site Editing (FSE) Global Styles and inline CSS * Block-based Widget Editor (reverts to Classic Widgets) * Block Patterns and Pattern Directory * Theme.json support and processing * Block Directory integration * Site Editor functionality #### Performance Optimizations * The block library CSS and JavaScript that every page loads * The Global Styles inline CSS, which dequeuing the handle never reaches * The block assets of any other plugin that registers blocks, on pages where no block appears * The block editor assets in the admin, wherever the Classic Editor is the one opening #### WooCommerce Integration * The block based product editor, which follows the same rules as any other post type * The WooCommerce block styles and scripts, removed along with the rest of the block assets * Nothing else: leave blocks on for products and the block product editor keeps working #### Admin Experience * Removes the welcome panel that promotes the block editor * Removes the Patterns submenu from the Appearance menu (WP 6.5+) * Removes the Fonts submenu from the Appearance menu (WP 7.0+) * Blocks access to Site Editor pages * Shows activation success notice * Warns you when a block theme is active * Adds settings and support links to plugin actions **A default that asks nothing, and a settings page for everything else** – Activating the plugin disables the block editor and every block feature across the site, which is what most people install it for. The rest of this page is about wanting less than that. **Full control when you need it** – The settings page lives under Settings > No Gutenberg?, built around one master switch. Leave it on and the whole site keeps the complete disable. Turn it off and you decide where the block editor goes away: by post type, by user role, by page template or by individual entry. The site wide pieces (classic widgets, block patterns, frontend block assets, theme.json and the Site Editor) are then yours to keep or remove one by one. Every checkbox means the same thing, so no setting ever undoes another one. **Switch editors entry by entry, where it makes sense** – Editor switching is chosen per post type, right next to the rule that disables the block editor. Enable it for pages, for instance, and every page gets „Edit (Classic)” and „Edit (Blocks)” links in the list plus a switch inside both editors, while your posts stay untouched. Each entry remembers the editor chosen for it, and that choice beats the rules in both directions: one landing page can stay on the Classic Editor while the rest keep blocks, or the other way around. **It tells you what it is doing** – The settings screen opens with a status panel for your particular site: how many block patterns are being blocked, how much weight is off every page, whether your theme is a block theme, and how much of your published content is really built with blocks. That last number is the one that should decide whether you strip the block styles from the frontend or not, and no other plugin tells you. **Built for agencies and managed sites** – The whole configuration can be fixed from wp-config.php, and the settings screen locked as read only or hidden altogether, so a site you deliver keeps the setup you left behind. **A whole network configured in one file** – This is where the plugin stands alone. Every single setting it has, and not just which editor opens, can be written in wp-config.php, the same file every site of a multisite network reads. A network of a hundred sites is set up once, all of them with the same rules, all of them with the same block CSS gone, and none of them able to drift away from it. The plugin can also be network activated and left alone, because settings are stored per site, so a network can equally let each site decide for itself. Same mechanism as the locking above, and this is how it is written. #### One configuration for a whole network, or for a site you deliver Everything the settings screen does can also be written in wp-config.php, where nobody changes it by accident, and what you write there wins over whatever is stored in the database. It is the same file for every site of a multisite network, so it is also how you set up a network without repeating the configuration site by site. Add the lines you need above the comment that says „That’s all, stop editing! Happy publishing.” To disable Gutenberg everywhere and leave no settings screen for anyone to touch, which is the usual setup both for a network and for a site you hand over to a client: ``` define( 'NO_GUTENBERG_OPTIONS', array( 'complete' => true ) ); define( 'NO_GUTENBERG_HIDE_SETTINGS', true ); ``` Drop that second line and the settings page is still there, showing the configuration the site is really running, but read only. And if all you want is to lock the screen, leaving the configuration as each site has it stored: ``` define( 'NO_GUTENBERG_LOCK_SETTINGS', true ); ``` NO_GUTENBERG_OPTIONS takes any of the settings on the screen, so a selective setup is written the same way: ``` define( 'NO_GUTENBERG_OPTIONS', array( 'complete' => false, 'disable_post_types' => array( 'post', 'page' ), 'disable_roles' => array( 'editor', 'author' ), 'frontend_css' => false, ) ); ``` The keys are the settings on the screen. complete, widgets, patterns, frontend_css, theme_json, site_editor and fse_notices take true or false, while disable_post_types, disable_roles, disable_templates and switch_post_types take an array of slugs, and disable_ids an array of entry IDs. Any key you leave out keeps the value stored on the site. Note that defining NO_GUTENBERG_OPTIONS already turns the whole screen read only, so NO_GUTENBERG_LOCK_SETTINGS is not needed on top of it. It fits sites that: – Work better in the Classic Editor and want it back – Run classic themes and plugins that were never built around blocks – Are paying for block CSS and JavaScript on pages with no blocks in them – Need the Classic Editor for everyone except a few post types, roles or people – Are a multisite network that wants the same editing experience on every site ### Support #### Need private support or custom development? Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just [contact me](https://ro.wordpress.org/plugins/no-gutenberg/no-gutenberg@ayudawp.com?output_format=md) and tell me what you need. #### Need help or have suggestions? * [Official website](https://servicios.ayudawp.com/) * [WordPress support forum](https://wordpress.org/support/plugin/no-gutenberg/) * [YouTube channel](https://www.youtube.com/AyudaWordPressES) * [Documentation and tutorials](https://ayudawp.com/) **Love the plugin?** Please leave us a 5-star review and help spread the word! ### About AyudaWP We are specialists in WordPress security, SEO, and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements. ## Capturi ecran [⌊WordPress posts page with Classic Editor restored⌉⌊WordPress posts page with Classic Editor restored⌉[ WordPress posts page with Classic Editor restored [⌊Classic Widgets interface instead of block widgets⌉⌊Classic Widgets interface instead of block widgets⌉[ Classic Widgets interface instead of block widgets [⌊Activation success notice⌉⌊Activation success notice⌉[ Activation success notice [⌊FSE theme activation warning⌉⌊FSE theme activation warning⌉[ FSE theme activation warning [⌊Settings page⌉⌊Settings page⌉[ Settings page ## Instalare 1. Go to your WP Dashboard > Plugins and search for ‘no gutenberg’ or… 2. Download the plugin from WP repository 3. Upload the ‘no-gutenberg’ folder to the ‘/wp-content/plugins/’ directory 4. Activate the plugin through the ‘Plugins’ menu in WordPress 5. That is it. The block editor is disabled across the site and the Classic Editor is back On a multisite network you can also Network Activate it, so it runs on every site of the network at once. Settings stay per site, and the description explains how to configure the whole network from wp-config.php. ## Întrebări frecvente ### Do I have to configure anything? No. Activating the plugin disables everything across the site. The settings page under Settings > No Gutenberg? is there only if you want to bring some part of the block editor back. ### Can I disable Gutenberg only for some content or some people? Yes. Go to Settings > No Gutenberg?, uncheck „Disable Gutenberg completely”, and then choose where the block editor should go away: post types, user roles, page templates or individual entry IDs. Rules are independent, so anything that matches gets the Classic Editor and everything else keeps working as usual. ### Can I disable just one part of Gutenberg? Yes. Once the master switch is off, the site wide pieces are independent checkboxes, so you can, for example, restore the classic Widgets screen and remove the block patterns while leaving the editor itself alone. ### If I only disable the editor for some content, what happens to the block styles? That is exactly why the plugin unchecks the frontend block assets and theme.json options for you when you switch to a partial setup: the content that still uses blocks would lose its styles on the frontend. The status panel tells you how many of your published entries are built with blocks, so you can decide with real numbers. ### Can I lock the configuration so a client cannot change it? Yes, from wp-config.php. `define( 'NO_GUTENBERG_LOCK_SETTINGS', true );` leaves Settings > No Gutenberg? visible but read only, and `define( 'NO_GUTENBERG_HIDE_SETTINGS', true );` takes it out of the menu. To fix the configuration itself, and not only lock the screen, there is NO_GUTENBERG_OPTIONS. The description has the three of them together, with the settings you can fix and the details worth knowing. ### Does it work on a multisite network? Yes, and it is what the plugin is best at. Activate it site by site, or Network Activate it and it runs on every site of the network. Settings are stored per site, so each site has its own Settings > No Gutenberg? and each site administrator manages their own. For the whole network at once, the place is wp-config.php, the same file every site reads: what you define there reaches all of them, covers every setting the plugin has and wins over whatever each site has stored. There is no network settings screen, because that file does the job for the entire network in a couple of lines. They are in the description, under „One configuration for a whole network, or for a site you deliver”. ### Can I open one entry with the other editor? Yes. In the post types table there is a second column, „Let each entry switch”: check it for the post types where it makes sense. Those entries then get „Edit ( Classic)” and „Edit (Blocks)” links in the list and a switch inside both editors, and each one remembers the editor you chose for it. ### Does this work with WooCommerce? Yes. Products behave like any other post type: with the master switch on, or with Products checked in the rules, the classic product editor is forced and the WooCommerce block assets are removed from the frontend. If you leave blocks on for products, the block based product editor keeps working, without a separate setting contradicting it. ### Will this break my existing content? No, and the plugin goes out of its way to keep it that way. It never rewrites a single entry, and an entry that is already built with blocks keeps the block editor whatever the rules say, so nothing you set here can send it to an editor that would reflow its markup. The entries list labels those entries and can be narrowed down to them, so you can see exactly what you have. There is one visible change on the frontend: with the frontend block assets removed, content built with blocks loses the block styles. The status panel tells you how many entries are affected before you decide. ### I want the Classic Editor on everything, block content included. Can I? Yes. Uncheck the content protection under the master switch, on the settings page. From that point the rules apply to every entry, and the plugin warns you inside the Classic Editor whenever you open one that is built with blocks, because saving it there can break its blocks. ### What happens if I deactivate the plugin? Everything comes back immediately: the block editor, Global Styles, the patterns and the block assets. Your content is exactly as it was, because the plugin never rewrote any of it. ### Is this compatible with my theme and my plugins? With classic themes, and with plugins that do not depend on blocks, yes: it removes block features instead of fighting them for control. Block themes are the exception, and there is a question about them right below. A plugin that registers blocks of its own keeps working, but those blocks lose their styles on the frontend if you remove the block assets, which is what the status panel is there to warn you about. ### Can I use it with a block theme? You can, but block themes are built around the very features this plugin removes, so their Site Editor and template editing will not work while it is active. The plugin warns you when it detects a block theme. If you need that theme, switch off the Site Editor and theme.json modules on the settings page, or use a classic theme instead. ### Why choose this over other similar plugins? Because it does not stop at the editor. Others disable the block editor and leave the rest running: this one also removes the FSE Global Styles, the block widgets, the patterns, the WooCommerce blocks and the block CSS and JavaScript that every page of your site is loading. It also tells you what it is doing, with a status panel measured on your own site instead of a list of promises. And on a multisite network it is configured for every site at once from a single file, all of it, not only which editor opens. ## Recenzii ![](https://secure.gravatar.com/avatar/871c28575990f53da9bea86693b3b828a8c198f032a7cd675013e307ca66f1d5? s=60&d=retro&r=g) ### 󠀁[Thank you](https://wordpress.org/support/topic/thank-you-3758/)󠁿 [Daniel Fuchs](https://profiles.wordpress.org/dfuchs72/) 13 iulie 2026 1 răspuns I’m very grateful for this plugin. I feel that all those full-site-editing and page- builder concepts are built on the flawed assumption that a maximum of choices is what people need. But the more options you have, the more complicated it gets, and with full-site editing and a lot of people playing around with it on a website, every page and post will look different – or you need a LOT of self-discipline. And if you have the technical understanding and patience to master those systems to good effect, you may as well learn PHP and CSS to program your own shortcodes which will do exactly what you want. I for one tried the block editor and found it much more fun to write my own classic theme with a sophisticated design but a minimum of options for the non-technical people who write posts for our website, so it’s all of one piece. And no, old Gutenberg is not to blame. He started his own media revolution, that’s true, and Neil Postman wrote critically about him, but he didn’t invent the block editor. Thank him for that. His full name, by the way, was Johannes Gensfleisch zum Gutenberg, which translates as „John Goose-Meat of the Good Mountain”. ![](https://secure.gravatar.com/avatar/97bcfdae06ad3f09f06835c88b84c5140403790faf36a48a660393f59afb0b54? s=60&d=retro&r=g) ### 󠀁[Excelente plugin – Excellent plugin](https://wordpress.org/support/topic/excelente-plugin-excellent-plugin-3/)󠁿 [Delia Carballo](https://profiles.wordpress.org/soydelia/) 21 ianuarie 2026 1 răspuns Es un plugin sencillo que hace exactamente lo que se espera de él: ¡deshacerse completamente de Gutenberg!––It is a simple plugin that does exactly what it is supposed to do: completely get rid of Gutenberg! ![](https://secure.gravatar.com/avatar/8439c0b8e69dba402a16468e80e8f09ee3113b50c71fecbe41426ef070b3d1cd? s=60&d=retro&r=g) ### 󠀁[Yeah!](https://wordpress.org/support/topic/yeah-66/)󠁿 [Alvaro Torres](https://profiles.wordpress.org/algato333/) 16 ianuarie 2026 1 răspuns Thanks for that! ![](https://secure.gravatar.com/avatar/4b92ef604315b62a1674ac426a2a1a9e952dbc76ab9475c5689915b292465118? s=60&d=retro&r=g) ### 󠀁[Of the best](https://wordpress.org/support/topic/of-the-best-2/)󠁿 [cf12](https://profiles.wordpress.org/cf12/) 21 februarie 2023 Thank you so much for this plugin! ![](https://secure.gravatar.com/avatar/4ce628d6c37c97d8bf7dbe1779249bf47e702d3d1ce415f64d7423a96b2caae9? s=60&d=retro&r=g) ### 󠀁[Gracias!](https://wordpress.org/support/topic/gracias-51/)󠁿 [Alain Aubry](https://profiles.wordpress.org/caban13/) 29 octombrie 2020 Gracias Fernando por esta iniciativa, la verdad uso otro plugin para esta funcionalidad, pero otro más siempre es útil. Espero que un dia abandonen la idea de que un editor de bloques es una buena idea … BRAVO !!! ![](https://secure.gravatar.com/avatar/a8c6fd07ccb1e60b83d43932050c2b8b089e169f8360529a2dfec387c21d8947? s=60&d=retro&r=g) ### 󠀁[A very good plugin](https://wordpress.org/support/topic/a-very-good-plugin-53/)󠁿 [elkanah2222](https://profiles.wordpress.org/elkanah2222/) 17 noiembrie 2019 I’ve never had any problems with this plugin. I loved the other one with the same name but when it did not work for me once, I started working with this one and it’s pretty cool. Love it big time. [ Citește toate cele 16 recenzii ](https://wordpress.org/support/plugin/no-gutenberg/reviews/) ## Contributori și dezvoltatori „No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor” este un software open-source. La acest modul au contribuit următoarele persoane. Contributori * [ Fernando Tellado ](https://profiles.wordpress.org/fernandot/) * [ Ayuda WordPress ](https://profiles.wordpress.org/ayudawp/) „No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor” a fost tradus în 13 locale. Mulțumim [traducătorilor](https://translate.wordpress.org/projects/wp-plugins/no-gutenberg/contributors) pentru contribuția lor. [Tradu „No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor” în limba ta.](https://translate.wordpress.org/projects/wp-plugins/no-gutenberg) ### Te interesează dezvoltarea? [Răsfoiește codul](https://plugins.trac.wordpress.org/browser/no-gutenberg/), vezi [depozitarul SVN](https://plugins.svn.wordpress.org/no-gutenberg/), sau abonează- te la [jurnalul de dezvoltare](https://plugins.trac.wordpress.org/log/no-gutenberg/) prin [RSS](https://plugins.trac.wordpress.org/log/no-gutenberg/?limit=100&mode=stop_on_copy&format=rss). ## Istoric modificări #### 2.3.2 * Fix: Sites running Divi 5 got a fatal error on every frontend page. Removing the block widgets from the classic Widgets screen unregistered the Block widget itself, and Divi asks WordPress for it while deciding which stylesheets a page needs. The classic Widgets screen is restored the same way as before, without touching the widget * Fix: Block widgets already saved on a site stopped being rendered on the frontend and disappeared from the Widgets screen. Nothing was lost, they are back on update, but do not save the Widgets screen while running 2.3.1 * Fix: Removed a filter removal that never did anything: the callback it named was never part of WordPress * Fix: The status panel said „1 still added by other plugins” when a single pattern was left, and gave translators two identical plural forms #### 2.3.1 * Improved: Tested up to WordPress 7.1, with no changes needed. The always iframed post editor, the persistent toolbar and the new client-side media processing headers only reach the block editor, and the Site Editor, Patterns and Fonts screens this plugin removes keep the same slugs * Improved: The plugin calls itself No Gutenberg? everywhere now, the same name it has on WordPress.org, instead of No Gutenberg in the plugins list, the Settings menu, its settings screen and its notices * Fix: Pages were loading the block styles and scripts of every plugin that registers blocks, even where no block appears. Removing the block CSS also turned off the on-demand loading that WordPress 6.8 tied to the same switch, so on a site with block plugins installed this plugin was adding weight instead of saving it * Fix: The Block widget is now really gone from the classic Widgets screen. The cleanup ran after WordPress had already registered it, so it stayed on the list #### 2.3.0 * New: Existing block content is protected. An entry that already contains blocks keeps the block editor whatever the rules say, so installing the plugin on a site with mixed content no longer sends that content to an editor that reflows its markup. A checkbox under the master switch gives the protection up when you really want the Classic Editor on everything * New: The entries list says which editor each entry opens with, and flags the entries built with blocks that are opening in the Classic Editor. A „Built with blocks” link next to All and Published narrows the list down to them, so you can finally see which entries they are instead of only how many * New: The Classic Editor warns you when the entry you are editing is built with blocks, before you save it, with a link to open it in the block editor instead * Improved: The editor chosen for a single entry is now honored whatever the configuration is, master switch included. It used to be read only where per entry switching was enabled, which left no way out on a site with everything disabled * Improved: Sites arriving from the Classic Editor plugin keep the editor it recorded for each entry, instead of starting from zero * Improved: The status panel counts drafts, pending, private and scheduled entries too, not only published ones, and links to the entries it is counting. A site in the middle of a migration was being told it had no block content * Improved: The activation notice says how many entries are built with blocks and what is going to happen to them * Fix: Uninstall now also removes the version option, the per entry editor meta and the content count transients For older changelog entries, please check the [changelog.txt](https://plugins.svn.wordpress.org/no-gutenberg/trunk/changelog.txt) file ## Meta * Versiunea **2.3.2** * Ultima actualizare **Acum 7 zile** * Instalări active: **9.000+** * Versiune WordPress ** 6.1 sau mai recentă ** * Testat până la **7.1** * Versiune PHP ** 7.4 sau mai recentă ** * Limbi * [Albanian](https://sq.wordpress.org/plugins/no-gutenberg/), [English (Canada)](https://en-ca.wordpress.org/plugins/no-gutenberg/), [English (UK)](https://en-gb.wordpress.org/plugins/no-gutenberg/), [English (US)](https://wordpress.org/plugins/no-gutenberg/), [Galician](https://gl.wordpress.org/plugins/no-gutenberg/), [German](https://de.wordpress.org/plugins/no-gutenberg/), [Spanish (Chile)](https://cl.wordpress.org/plugins/no-gutenberg/), [Spanish (Colombia)](https://es-co.wordpress.org/plugins/no-gutenberg/), [Spanish (Ecuador)](https://es-ec.wordpress.org/plugins/no-gutenberg/), [Spanish (Mexico)](https://es-mx.wordpress.org/plugins/no-gutenberg/), [Spanish (Spain)](https://es.wordpress.org/plugins/no-gutenberg/), [Spanish (Venezuela)](https://ve.wordpress.org/plugins/no-gutenberg/), [Swedish](https://sv.wordpress.org/plugins/no-gutenberg/) și [Ukrainian](https://uk.wordpress.org/plugins/no-gutenberg/). * [Tradu în limba ta](https://translate.wordpress.org/projects/wp-plugins/no-gutenberg) * Etichete * [blocks](https://ro.wordpress.org/plugins/tags/blocks/)[classic editor](https://ro.wordpress.org/plugins/tags/classic-editor/) [fse](https://ro.wordpress.org/plugins/tags/fse/)[gutenberg](https://ro.wordpress.org/plugins/tags/gutenberg/) [woocommerce](https://ro.wordpress.org/plugins/tags/woocommerce/) * [Vizualizare avansată](https://ro.wordpress.org/plugins/no-gutenberg/advanced/) ## Evaluări 5 din 5 stele. * [ 16 5 – recenzii (stele) ](https://wordpress.org/support/plugin/no-gutenberg/reviews/?filter=5) * [ 0 4 – recenzii (stele) ](https://wordpress.org/support/plugin/no-gutenberg/reviews/?filter=4) * [ 0 3 – recenzii (stele) ](https://wordpress.org/support/plugin/no-gutenberg/reviews/?filter=3) * [ 0 2 – recenzii (stele) ](https://wordpress.org/support/plugin/no-gutenberg/reviews/?filter=2) * [ 0 1 – recenzii (stele) ](https://wordpress.org/support/plugin/no-gutenberg/reviews/?filter=1) [Recenzia ta](https://wordpress.org/support/plugin/no-gutenberg/reviews/#new-post) [Vezi toate recenziile](https://wordpress.org/support/plugin/no-gutenberg/reviews/) ## Contributori * [ Fernando Tellado ](https://profiles.wordpress.org/fernandot/) * [ Ayuda WordPress ](https://profiles.wordpress.org/ayudawp/) ## Suport Probleme rezolvate în ultimele două luni: 1 din 1 [Vezi forumul pentru suport](https://wordpress.org/support/plugin/no-gutenberg/)