swinggraphics

Intended for use with the Classic Editor plugin.
Ever get annoyed or frustrated by the way TinyMCE+wpautop+do_shortcode wreak havoc on your shortcodes, wrapping <code></code>s around <code><div></code>s, leaving orphan <code></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.
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></code> tags, etc.
The <a href="https://codex.wordpress.org/Shortcode_API#Output" rel="nofollow ugc">Codex says</a>:
<blockquote>
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></code> or <code><div></code>.
</blockquote>
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></code> tag with some classes. (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.)
<h4>Usage</h4>
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>.
<h4>Gutenberg</h4>
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.

Priority Shortcodes

Processes specific shortcodes before wpautop() and do_shortcode()

Ayon M

This is a lightweight Classic Editor plugin that gives you complete control over when to use the Classic Editor vs the Block Editor (Gutenberg). Despite the introduction of Gutenberg, a brand new block editor with WordPress 5.x, many users still prefer the Classic Editor due to its compatibility and ease of use.
What does this plugin do?
<ul>
<li>Disables the Gutenberg Block Editor (with granular control)</li>
<li>Reverts back to the Classic WordPress Editor</li>
<li>Reverts to Classic Widgets section</li>
<li>Configure which post types use Classic Editor</li>
<li>Configure which user roles use Classic Editor</li>
<li>Simple mode for quick setup or Advanced mode for granular control</li>
<li>Modern, user-friendly settings interface</li>
</ul>
How to use this plugin?
<ul>
<li>Simple Mode: Just activate the plugin and it works immediately (default)</li>
<li>Advanced Mode: Enable “Advanced Settings” to configure per post type and user role</li>
</ul>

Enable Classic Editor & Widgets

A simple & lightweight plugin to enable the classic editor on WordPress with advanced configuration options.

Priority Shortcodes vs Enable Classic Editor & Widgets