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

Irish_Cathal

Description: Classic Editor on off is a plugin that gives the ability to turn off all or some of Gutenberg, reverting to classic editor – where needed. Gutenberg (Gutenberg Blocks / Gutenberg Editor) replaced the Classic Editor but there may be times you wish to use the classic editor. Disable Gutenberg Blocks completely, or choose to disable for widgets, posts or pages.
If you prefer the old editors or just need to do some testing, this plugin will assist you in reverting to non Gutenberg setups by replacing with the Classic Editor.
Use this plugin to restores original Edit Post screen / Widgets screen (TinyMCE, meta boxes, etc.).
For temporary changes or disable permanently: Widgets, posts or pages – you choose!

Classic Editor on off


Plugin does just what it says it does... loads Gutenberg on some or all or none of the posts, pages and widgets. Great on plugins that do not support Blocks' meta boxes. You can disable for posts only so you have a custom metabox showing in the editor but then leave Blocks enabled for pages so you can use blocks to build pages. 


Simple and Useful

Description: Classic Editor on off is a plugin that gives the ability to turn off all or some of Gutenberg, reverting to classic editor - where needed …

Priority Shortcodes vs Classic Editor on off