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()

Ravi A. Vadhel

Have you upgraded WordPress and stucked with the new editor? Don’t worry, Just install the Remove Gutenberg plugin and enjoy the Classic editor. Additionally, There is an option in Reading settings from you can enable/disable the feature.

If you like this plugin, please write a few words about it at wordpress.org. Your opinion will help other people.

<a href="https://wordpress.org/support/plugin/restore-classic-editor/reviews/?rate=5&filter=5#new-post" rel="ugc">Rate plugin</a>

Remove Gutenberg

This is very light weight and perfect plugin to remove Gutenberg and restore the old classic editor. Once update the WordPress, it was like headache to manage composer and other things. Thanks to the developer to resolve my issue. :)

Perfect

Remove Gutenberg Editor and get back to old version of editor. This provides Original Classic Editor and more.

Priority Shortcodes vs Remove Gutenberg