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

Supracorona

<p>💬<br />
<em>Dear and respected members of the WordPress community, especially those who still believe that “Code is Poetry” — believe it or not, there are people like me for whom this removed feature still matters.</em></p>
<p>This plugin restores the classic<br />
<strong>“Visual Editor Options”</strong><br />
section to the user profile screen.</p>
<p>It’s a clean, dependable tweak — made for those who prefer writing in plain text, without distraction, without visual clutter.</p>
<p>No extra settings. No noise. Just the option that once was.</p>
<p>Perfect for:</p>
<ul>
<li>writers who live in the HTML tab,</li>
<li>developers who avoid visual editors,</li>
<li>or anyone who simply misses that checkbox.</li>
</ul>
<p>It works with both the Classic and Block editors,<br />
and doesn’t require any additional plugins.</p>
<p>Just install, and enjoy the silence of plain text.</p>
<h3>How It Works</h3>
<ol>
<li>A checkbox labeled <strong>“Disable the visual editor when writing”</strong> is added to each user’s profile page.</li>
<li>When checked, the plugin disables visual editing features and saves the preference (<code>rich_editing = false</code>).</li>
<li>Both TinyMCE and Gutenberg are bypassed — only the plain text editor is shown.</li>
</ol>
<p>Additional behaviors (enabled by default):</p>
<ul>
<li>Prevents loading of unnecessary editor scripts and styles for users who opt out.</li>
<li>Removes visual editor metaboxes when not needed.</li>
<li>Displays a dismissible admin notice if visual editing is disabled but the plugin is no longer active.</li>
</ul>
<h3>Compatibility</h3>
<ul>
<li>Works with both Classic and Block (Gutenberg) editors.</li>
<li>Compatible with the Genesis Framework and most modern themes.</li>
<li>Functions independently — does <strong>not</strong> require the Classic Editor plugin.</li>
<li>Honors native WordPress capabilities like <code>user_can_richedit</code> and <code>use_block_editor_for_post</code>.</li>
</ul>
<h3>Translations</h3>
<p>This plugin is translation-ready.<br />
Currently available in:</p>
<ul>
<li>Japanese (thanks to @kimipooh)  </li>
</ul>
<p>If you would like to contribute a translation, please visit:<br />
https://translate.wordpress.org/projects/wp-plugins/classic-visual-editor-options/</p>


Classic Visual Editor Options


Thank you for providing such a great plugin!I translated the main part into Japanese \^^/;.



When entering code in the classic editor, the forced substitution function would sometimes be activated in the visual editor, so this feature was very useful. I agree with Gutenbeng's philosophy, but it's a shame that the option for a simpler editor is disappearing.


Great plugin!

Restores the “Visual Editor Options” section in user profiles.

Priority Shortcodes vs Classic Visual Editor Options