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

Jamie Dąbrowiecki

<p>Headingo is a lightweight utility plugin that allows administrators to control which heading levels are available in the editor toolbar. This tool only works for websites using the Classic Editor.</p>
<p>These settings are applied to all users with editing permissions.</p>
<p>The configurable heading levels are:</p>
<ul>
<li>Heading 1</li>
<li>Heading 2</li>
<li>Heading 3</li>
<li>Heading 4</li>
<li>Heading 5</li>
<li>Heading 6</li>
<li>Preformatted</li>
</ul>
<p>This is especially useful for removing the Heading 1 (H1) option to prevent editors from mistakenly selecting it, as well as removing heading levels which are not required on your website.</p>
<p>This plugin is intended for websites that rely on the Classic Editor editing experience. It does not attempt to modify the Block Editor (Gutenberg), where heading availability is governed by editor and theme configuration (theme.json) by design. The Classic Editor plugin is required for this plugin to work (or a theme that allows you to switch to the Classic Editor without the plugin).</p>
<h3>Classic Editor</h3>
<p>The Classic Editor (TinyMCE) is fully supported. Selected heading levels and Preformatted can be hidden from the formatting dropdown while remaining available via keyboard shortcuts or pasted HTML. The Paragraph option is always available and cannot be toggled.</p>
<h3>Block Editor (Gutenberg)</h3>
<p>This plugin does not control heading levels in the Block Editor. Gutenberg does not currently provide a reliable API for plugins to override available heading levels, as these are controlled by editor and theme settings.</p>


Headingo

Choose which heading levels are visible in the Classic Editor toolbar.

Priority Shortcodes vs Headingo