Disable Gutenberg vs SocialCrew Widgets

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! 🙂

SocialCrew Widgets loads the official SocialCrew widget runtime from widgets-api.socialcrew.io when a page contains a widget shortcode or the SocialCrew block. Shortcode [socialcrew_widget] with catalog parameters (type, team, league) or a direct space id. Shortcode [socialcrew_widget_saved] for presets you save under Settings → SocialCrew Widgets. Gutenberg block SocialCrew Widget to pick a saved preset. Settings screen with a shortcode builder, preview in a new window, and saved widget management. The plugin loads the space catalog from the SocialCrew widgets API (GET /plugin/v1/space-catalog) on the server. No setup is required after install—the production API URL and read-only credentials are built into the plugin. The catalog is cached briefly in WordPress transients. External services This plugin relies on SocialCrew’s hosted widget loader to render widgets in the visitor’s browser. What the service is: The endpoint https://widgets-api.socialcrew.io/load serves the JavaScript module that powers the widget UI (tables, fixtures, polls, etc.) when your site outputs the plugin shortcode or block. What data is sent and when: On each page view where a widget is embedded (or when you use the admin preview), the visitor’s browser requests that URL. Typical query parameters are space (the widget identifier), adaptive=true, and optional showHeader. The plugin does not intentionally send WordPress user credentials or private admin data to SocialCrew—only the public widget parameters needed to render the embed. Documentation (widgets product): SocialCrew Widgets Terms of Use: https://widgets.socialcrew.io/termos-de-uso Privacy policy: https://widgets.socialcrew.io/politica-de-privacidade Privacy When a visitor loads a page that embeds a SocialCrew widget, the browser requests a JavaScript module from widgets-api.socialcrew.io. Query parameters may include the widget space id, adaptive=true, and optional showHeader. On the server, the plugin may call api-v1.widgets.solutions to refresh the read-only space catalog (type/team/league to space id). That request uses credentials embedded in the plugin package; visitors never see those credentials. The plugin does not send your WordPress user data to SocialCrew by default. Site administrators configure widgets in wp-admin; only public widget parameters are used in the front-end script URL. For questions about data processed by SocialCrew’s servers, refer to the External services section above, the privacy policy at widgets.socialcrew.io/politica-de-privacidade, and the terms at widgets.socialcrew.io/termos-de-uso.