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

Tercan Keskin

<p>WP Heading Buttons adds quick heading buttons (H1-H6) to both Classic Editor (TinyMCE) and Block Editor toolbars.<br />
Choose which levels appear, toggle Classic block support, and keep icons consistent with shared SVGs.</p>


WP Heading Buttons

One-click heading buttons (H1-H6) for WordPress Classic Editor and Gutenberg (Block Editor).

Priority Shortcodes vs WP Heading Buttons