Ayuda WordPress

Fernando Tellado

<p>The most comprehensive solution to completely remove Gutenberg Block Editor and all its related features from your WordPress installation. This plugin doesn’t just disable the block editor – it eliminates every trace of block-related functionality for maximum performance and compatibility.</p>
<p><strong>What this plugin removes:</strong></p>
<h4>Core Gutenberg Features</h4>
<ul>
<li>Gutenberg Block Editor (completely disabled)</li>
<li>Full Site Editing (FSE) Global Styles and inline CSS</li>
<li>Block-based Widget Editor (reverts to Classic Widgets)</li>
<li>Block Patterns and Pattern Directory</li>
<li>Theme.json support and processing</li>
<li>Block Directory integration</li>
<li>Site Editor functionality</li>
</ul>
<h4>Performance Optimizations</h4>
<ul>
<li>Removes all block-related CSS and JavaScript files</li>
<li>Eliminates Global Styles inline CSS on every page</li>
<li>Removes unused block library assets</li>
<li>Disables block editor admin assets</li>
<li>Removes duotone and layout support filters</li>
</ul>
<h4>WooCommerce Integration</h4>
<ul>
<li>Disables WooCommerce block-based checkout and cart</li>
<li>Removes WooCommerce block editor for products</li>
<li>Eliminates WooCommerce block assets and styles</li>
<li>Forces classic WooCommerce experience</li>
</ul>
<h4>Admin Experience</h4>
<ul>
<li>Removes “Try Gutenberg” dashboard widgets</li>
<li>Disables Gutenberg-related admin menus</li>
<li>Removes Patterns submenu from Appearance menu (WP 6.5+)</li>
<li>Blocks access to Site Editor pages</li>
<li>Shows activation success notice</li>
<li>Adds support link to plugin actions</li>
</ul>
<p><strong>Zero Configuration Required</strong> – Simply activate the plugin and everything is automatically disabled. No settings page needed because it just works!</p>
<p>This plugin is perfect for:<br />
– Users who prefer the Classic Editor<br />
– Sites requiring maximum compatibility with legacy themes and plugins<br />
– Performance-focused installations<br />
– Users who want to eliminate block-related overhead completely</p>
<h3>Support</h3>
<h4>Need help or have suggestions?</h4>
<ul>
<li><a href="https://servicios.ayudawp.com/" rel="nofollow ugc">Official website</a></li>
<li><a href="https://wordpress.org/support/plugin/no-gutenberg/" rel="ugc">WordPress support forum</a></li>
<li><a href="https://www.youtube.com/AyudaWordPressES" rel="nofollow ugc">YouTube channel</a></li>
<li><a href="https://ayudawp.com/" rel="nofollow ugc">Documentation and tutorials</a></li>
</ul>
<p><strong>Love the plugin?</strong> Please leave us a 5-star review and help spread the word!</p>
<h3>About AyudaWP</h3>
<p>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.</p>


No Gutenberg – Disable Blocks Editor and Global Styles – Back to Classic Editor

Simple, light weight and cool. No, I don't dislike Gutenberg that's cool too. 

Nice Plugin

Complete elimination of Gutenberg Block Editor, FSE Global Styles, Block Widgets, Patterns, and WooCommerce blocks. Back to Classic Editor.

iansvo

<p>This block allows you to add an additional block content area to a site-editor template and store the block output inside a meta field. By default, WordPress posts or pages may only store blocks in one place: post_content. These blocks are output on the page using the core/post-content block. This block allows you to have multiple “outlets” where you can add blocks so you can have post-specific blocks appear in more than one location in the template.</p>
<p>The block is a fork of the core/post-content block that uses a customized version of the useEntityBlockEditor hook which supports meta keys. The blocks for your content area are then stored inside that meta key (instead of post_content). This allows you to keep the blocks separate and you can use as many of these on a single template as you want (but in most cases 2 is probably enough). It’s all up to you!</p>
<h3>Requirements</h3>
<ol>
<li>Using this plugin requires you to enable template previews (which will let you visually see the new content area you’re adding). This can be enabled on any given post or page, but you can optionally set it on by default using a filter.</li>
<li>Your theme must be a block theme (i.e. it uses the site editor). This won’t work for a hybrid or classic theme (which has no concept of live template preview in the block editor).</li>
</ol>
<h3>Hooks</h3>
<p>If you want to disable this meta key’s registration, add the following to your theme or plugin:</p>
<pre><code><?php
add_filter( 'content_area_block_register_default_meta', '__return_false' );
</code></pre>
<p>For advanced users, there is also a filter for the entire block’s output. See the below snippet from render.php:</p>
<pre><code><?php
/**
 * Filter the block's frontend output.
 *
 * @param string $parsed_content The parsed block content for output.
 * @param int    $block_post_id  The current post ID the block is displaying in.
 * @param array  $attributes     The block attributes.
 * @param string $content        The original unparsed block content.
 * @param object $block          The current parsed block object.
 *
 * @return The block content for output on the frontend.
 */
$output = apply_filters( 
    'content_area_block_content', 
    do_blocks( str_replace( ']]>', ']]&gt;', $content ) ), 
    $block_post_id, 
    $attributes, 
    $content, 
    $block 
);
</code></pre>
<h3>Contributing</h3>
<p>The plugin source code may be found here: https://github.com/iansvo/content-area-block.</p>
<p>To build the plugin from source, you must have NodeJS (v24+) installed.</p>
<p>Setup Steps:</p>
<ol>
<li>Navigate to the project folder in your terminal.</li>
<li>Run <code>npm i</code> to install dependencies.</li>
<li>Run <code>npm run build</code> to performn the initial build.</li>
</ol>
<p>If you’re using wp-env to run the plugin…<br />
1. Run <code>npm run wp-env start</code> to start the docker container.<br />
2. Run <code>npm run start</code> to watch for file changes.</p>


Content Area Block

Adds a block content area to a site editor template and stores the blocks in a specified meta field. By default, the plugin will add a new meta field  …

No Gutenberg – Disable Blocks Editor and Global Styles – Back to Classic Editor vs Content Area Block