Disable Gutenberg vs Responsive Block Controls

This plugin disables the new Gutenberg Editor (aka Block Editor) and replaces it with the Classic Editor. You can disable Gutenberg completely, or selectively disable for posts, pages, roles, post types, and theme templates. Plus you can hide the Gutenberg nag, menu item, and more! ♠ The all-in-one, COMPLETE solution for handling Gutenberg ♠ Hide ALL traces of Gutenberg and replace with Classic Editor ♠ Restores original Edit Post screen (TinyMCE, meta boxes, etc.) The Disable Gutenberg plugin restores the classic (original) WordPress editor and the “Edit Post” screen. So you can continue using plugins and theme functions that extend the Classic Editor. Supports awesome features like Meta Boxes, Quicktags, Custom Fields, and everything else the Classic Editor can do. Easy to Use Just activate and done! The default plugin settings are configured to hide all traces of the Gutenberg Block Editor, and fully restore the original Classic Editor. Further options for customizing when/where Gutenberg is enabled are available in the plugin settings. ♠ Disable Block Widgets and restore Classic Widgets 🙂 Options Disable Gutenberg completely (all post types) Disable Gutenberg for any post type Disable Gutenberg for any user role Disable Gutenberg for any theme template Disable Gutenberg for any post/page IDs Disable Gutenberg admin notice (nag) Option to restore Classic Widgets Option to hide the plugin menu item Option to hide the Gutenberg plugin menu item (settings link) Adds “Classic Editor” link to each post on the Posts screen Adds item to the WP sidebar menu: “Add New (Classic)” Option to enable Custom Fields Meta Box for ACF Choose which editor to use for each post Whitelist any post title, slug, or ID Option to enable/disable frontend Gutenberg stylesheet ♠ Works same as Classic Editor plugin, but can do a LOT more! ♠ Lightweight and super fast, built with WP APIs 🙂 Fully configurable, enable or disable Gutenberg and restore the Classic Editor wherever is necessary. Automatically replaces Gutenberg with the Classic Editor. Features Super simple Clean, secure code Built with the WordPress API Lightweight, fast and flexible Regularly updated and “future proof” Works great with other WordPress plugins Plugin options configurable via settings screen Focused on flexibility, performance, and security One-click restore plugin default options Translation ready ♠ Works great with Google AMP and the WordPress AMP plugin Disable Gutenberg is developed and maintained by Jeff Starr, 15-year WordPress developer and book author. Super light & fast plugin, super easy on server resources! Why? Gutenberg is a useful editor but sometimes you want to disable it for specific posts, pages, user roles, post types, and/or theme templates. This plugin enables you to disable Gutenberg and replace it with the Classic Editor wherever you want. For example, lots of WordPress users already enjoy robust page-building functionality via one of the many great plugins like Composer or Elementor. So many options, no need to feel “locked in” to using Gutenberg! If you like Disable Gutenberg, please give it a 5-star rating, thank you! Privacy This plugin does not collect or store any user data. It does not set any cookies, and it does not connect to any third-party locations. Thus, this plugin does not affect user privacy in any way. Support development I develop and maintain this free plugin with love for the WordPress community. To show support, you can make a donation or purchase one of my books: The Tao of WordPress Digging into WordPress .htaccess made easy WordPress Themes In Depth Wizard’s SQL Recipes for WordPress And/or purchase one of my premium WordPress plugins: BBQ Pro – Blazing fast WordPress firewall Blackhole Pro – Automatically block bad bots Banhammer Pro – Monitor traffic and ban the bad guys GA Google Analytics Pro – Connect WordPress to Google Analytics Head Meta Pro – Ultimate Meta Tags for WordPress REST Pro Tools – Awesome tools for managing the WP REST API Simple Ajax Chat Pro – Unlimited chat rooms USP Pro – Unlimited front-end forms Links, tweets and likes also appreciated. Thanks! 🙂

Responsive Block Controls adds practical responsive controls to supported native Gutenberg blocks. Adjust layouts, spacing, column widths, Query Loop grids, Gallery columns, and Spacer heights without replacing core blocks or moving content into a page builder. Native WordPress blocks are fast, portable, and theme-friendly, but responsive layout tweaks often still require custom CSS, duplicated blocks, or a full page builder. This plugin keeps your content in native blocks and adds the missing breakpoint controls directly in the block inspector. Why use it? Add responsive controls to supported native Gutenberg blocks. Keep existing core blocks, patterns, synced patterns, reusable blocks, and template parts. Avoid extra builder markup, shortcodes, and content lock-in. Adjust columns, gaps, custom widths, order, Media & Text layouts, Query Loop grids, Gallery layouts, and Spacer heights from the editor sidebar. Preserve desktop behavior and theme spacing defaults unless you override them. Remove the plugin without breaking the saved content structure. Supported blocks Support is added block by block. In this version, responsive controls are available for: core/columns — responsive column counts, gap controls, and custom-width mode. core/column — per-breakpoint width and order controls when custom-width mode is enabled on the parent Columns block. core/post-template inside Query Loop — manual column controls, auto-fit minimum width, responsive gaps, and optional Masonry for supported fixed-column grids. core/gallery — responsive columns and gap controls while keeping the native Gallery block. core/spacer — tablet and mobile height overrides while keeping the native desktop Spacer height. core/media-text — side-by-side or stacked layouts and stacked order across four non-desktop breakpoints. How it works The plugin stores settings as native block attributes and renders a small set of CSS classes and custom properties. It does not register replacement layout blocks and does not wrap your content in custom frontend markup. Your theme stays in control of the base layout. Responsive Block Controls only applies supported responsive values at the configured breakpoints. If the plugin is removed, WordPress ignores the extra attributes and the blocks fall back to their normal core behavior. Editor experience Responsive controls appear only when the selected block is supported. Breakpoint tabs follow desktop, tablet, and mobile editing workflows. Smaller breakpoints inherit from larger breakpoints until you override them. Gap controls support px, rem, and em values with predictable reset behavior. Custom-width Columns layouts support per-column width and simple order controls. Query Loop grids support manual columns, auto-fit minimum width, and Masonry guidance where available. Spacer height can be customized for tablet and mobile previews. Media & Text can inherit, stay side by side, or stack with media first or text first at each non-desktop breakpoint. Theme spacing defaults are detected when possible. Reset actions are scoped to the active setting and breakpoint, so inherited values and unrelated responsive settings are preserved. WordPress 7.1 responsive styles WordPress 7.1 introduces responsive values for standard block supports. Responsive Block Controls keeps those native values and its own four-breakpoint values separate: Leave Advanced 4 breakpoints disabled to let WordPress control overlapping responsive layout and gap properties. Enable Advanced 4 breakpoints when you need separate tablet landscape, tablet portrait, mobile landscape, and mobile portrait values. If both systems contain overlapping values, the editor shows a conflict warning and the plugin’s Advanced 4 breakpoints take precedence only for supported overlapping layout and gap properties. Switching back to WordPress responsive styles is reversible: plugin settings and native WordPress settings are preserved rather than migrated or deleted. Native responsive typography, padding, colors, and other non-overlapping block supports continue to work. Accessibility and localization Inspector controls are keyboard accessible and labeled for screen readers. Strings are translation-ready via the responsive-columns text domain.