swinggraphics

<p><em>Intended for use with the Classic Editor plugin.</em></p>
<p>Ever get annoyed or frustrated by the way TinyMCE+wpautop+do_shortcode wreak havoc on your shortcodes, wrapping <code><p></code>s around <code><div></code>s, leaving orphan <code></p></code>s, and all sorts of craziness? This plugin allows you to specify shortcodes to be processed before those other actions, generating the clean code you expected.</p>
<p>Priority Shortcodes works by adding an action to <code>the_content</code> and <code>widget_text</code> hooks with a higher priority than <code>wpautop</code> and <code>do_shortcode</code>. The result is that those other actions run your shortcode’s final output, rather than trying to guess if it should be wrapped in <code><p></code> tags, etc.</p>
<p>The <a href="https://codex.wordpress.org/Shortcode_API#Output" rel="nofollow ugc">Codex says</a>:</p>
<blockquote>
<p>wpautop recognizes shortcode syntax and will attempt not to wrap p or br tags around shortcodes that stand alone on a line by themselves. Shortcodes intended for use in this manner should ensure that the output is wrapped in an appropriate block tag such as <code><p></code> or <code><div></code>.</p>
</blockquote>
<p>But sometimes shortcodes stand on their own on a line, wanting desperately to be wrapped in a paragraph tag, and sometimes they don’t. Like a shortcode that generates a <code><span></code> tag with some classes. <em>(Yeah, you might want to use <a href="https://codex.wordpress.org/TinyMCE_Custom_Styles" rel="nofollow ugc">custom TinyMCE styles</a> instead for a simple span.)</em></p>
<h4>Usage</h4>
<p>Where you want to process a shortcode with priority, use “[!” at the start. For example: <code>[my-shortcode]</code> becomes <code>[!my-shortcode]</code> and <code>[my-shortcode]Some content.[/my-shortcode]</code> becomes <code>[!my-shortcode]Some content.[/my-shortcode]</code>.</p>
<h4>Gutenberg</h4>
<p>Users of the new WordPress editor, “Gutenberg”, will probably not use Priority Shortcodes within the new editor, but the plugin continues to work in the Classic Editor.</p>


Priority Shortcodes

Processes specific shortcodes before wpautop() and do_shortcode()

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 private support or custom development?</h4>
<p>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 <a href="mailto:no-gutenberg@ayudawp.com" rel="nofollow ugc">contact me</a> and tell me what you need.</p>
<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.

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