No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor vs ZoloBlocks – Advanced Gutenberg Blocks, Website Builder & Page Design Toolkit

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 and tell me what you need. Need help or have suggestions? Official website WordPress support forum YouTube channel Documentation and tutorials 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.

ZoloBlocks is a collection of blocks, patterns, and page templates for the WordPress block editor. It helps you design complete pages using the native editor without a third-party page builder. Live Demo | Pro Version | Documentation What ZoloBlocks Provides A library of advanced blocks that extend the default WordPress block editor. Pre-designed patterns and page templates you can insert into pages. Full Site Editing compatibility with block themes. Dynamic content options for site, post, or user data. Query loop options for posts, products, or custom post types. Animation and visual effect options for supported blocks. Optional AI text generation to help draft headings and paragraphs (third-party service, see “External services” below). Pattern import and export for reuse across sites. Key Features Layout building with pre-built sections and templates. Responsive containers for mobile, tablet, and desktop. Mega menu for multi-level navigation. Dynamic content and query loop for posts or custom post types. Entrance and scroll-based animations on supported blocks. Optional AI text generation inside the editor (third-party service). Pattern import / export for reuse across pages or sites. Available Blocks ZoloBlocks ships 60+ free and pro blocks across categories such as Image, Slider & Carousel, Post, Review, Form, Popup, Utility, Creative, Loop & Animation, Grid & List, Single Page Elements, and Advanced. A full list with live demos is available at https://zoloblocks.com/demo/. Who Is It For Website designers, freelancers, agencies, bloggers, content creators, small business owners, portfolio builders, and digital marketers who want to design WordPress pages directly in the block editor. Support The team behind ZoloBlocks ships regular updates. For help, contact support. Visit BdThemes for more plugins and documentation. Source code The compiled JavaScript and CSS files in the build/ and assets/ directories are generated from the source code in the src/ directory. Public source repository: https://github.com/bdthemes/zoloblocks Build instructions: Clone the repository. Run npm install to install dependencies. Run npm run build to generate the production assets in build/. Run composer install to install PHP dependencies (used for development tooling only). External services This plugin connects to several third-party services. Each service is only contacted when the related feature is used or configured. No personal data is sent unless the corresponding feature is enabled or the user interacts with it. 1. Google reCAPTCHA Used by the Form block when the site administrator enables reCAPTCHA protection and provides site / secret keys in ZoloBlocks settings. – What is sent: the reCAPTCHA token generated in the visitor’s browser, the visitor’s IP address, and the configured secret key, sent to https://www.google.com/recaptcha/api/siteverify on form submission. The Google reCAPTCHA JavaScript (https://www.google.com/recaptcha/api.js) is loaded on pages containing a form when reCAPTCHA is enabled. – When: only when reCAPTCHA is enabled and a form is submitted. – Provider: Google LLC. Terms: https://policies.google.com/terms Privacy: https://policies.google.com/privacy 2. Google Maps Used by the Google Map block when added to a page. – What is sent: the configured Google Maps API key and a request to load the Google Maps JavaScript API from https://maps.googleapis.com/maps/api/js. The browser of any visitor viewing a page containing a Google Map block will load map tiles from Google. – When: only when a Google Map block is present on a page. – Provider: Google LLC. Terms: https://cloud.google.com/maps-platform/terms Privacy: https://policies.google.com/privacy 3. Google Fonts list (WordPress.org mirror) Optional. Used by the typography controls only when a site administrator enables Settings → Editor Options → Load Google Fonts catalog (WordPress.org mirror) in the ZoloBlocks dashboard. – What is sent: a simple HTTP GET request (no personal data) to https://s.w.org/images/fonts/wp-7.0/collections/google-fonts-with-preview.json to retrieve the list of Google Fonts. – When: only after the option is enabled, and only when the block editor needs to refresh the font list. – Provider: WordPress.org. Terms and privacy: https://wordpress.org/about/privacy/ 4. Zolo AI (AI text generation by Sigmative) Used by the optional AI text generation feature inside the block editor. – What is sent: the prompt text entered by the site administrator in the editor, and the API key configured in ZoloBlocks settings, sent to https://ai.sigmative.com/api/prompt/v1/generation/chat/completions. – When: only when an administrator clicks the AI generation action in the editor. – Provider: Sigmative. Privacy: https://sigmative.com/privacy-policy 5. Mailchimp (optional Form integration) Used only when a site administrator configures a Form block to send subscriber data to Mailchimp. – What is sent: the visitor’s email address, optional first name, the configured Mailchimp API key and list ID, sent to https:// .api.mailchimp.com/3.0/lists/{list_id}/members (where is the data center prefix derived from the API key). – When: only when a visitor submits a form whose Mailchimp integration has been configured by the administrator. – Provider: Intuit Mailchimp. Terms: https://mailchimp.com/legal/terms/ Privacy: https://www.intuit.com/privacy/statement/ 6. Custom Webhooks (optional Form integration) Used only when a site administrator pastes a custom webhook URL into the Form block settings. – What is sent: the visitor’s email address and optional first name, sent as a JSON POST request to the URL configured by the administrator. – When: only when a visitor submits a form whose webhook URL has been configured by the administrator. – Provider: the third-party service chosen by the administrator. The administrator is responsible for ensuring the destination has an appropriate privacy policy.