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

WordPress.org

Andrew Ozz

luciano-croce

Jonathan Desrosiers

Mel Choyce-Dwan

Gary Pendergast

Riad Benguella

Brian Alexander

Josepha

Alexis Lloyd

Classic Editor is an official plugin maintained by the WordPress team that restores the previous (“classic”) WordPress editor and the “Edit Post” screen. It makes it possible to use plugins that extend that screen, add old-style meta boxes, or otherwise depend on the previous editor.
Classic Editor is an official WordPress plugin, and will be fully supported and maintained until 2024, or as long as is necessary.
At a glance, this plugin adds the following:
<ul>
<li>Administrators can select the default editor for all users.</li>
<li>Administrators can allow users to change their default editor.</li>
<li>When allowed, the users can choose which editor to use for each post.</li>
<li>Each post opens in the last editor used regardless of who edited it last. This is important for maintaining a consistent experience when editing content.</li>
</ul>
In addition, the Classic Editor plugin includes several filters that let other plugins control the settings, and the editor choice per post and per post type.
By default, this plugin hides all functionality available in the new block editor (“Gutenberg”).

Classic Editor

Great plugin

This is the first plugin I install on any new website. I wish this was an option built into WordPress, as I feel like it's essential to be able to manage content using a WYSIWYG editor. 

My top plugin

Toda vez esse plugin me salva, ele é incrível, eu detesto a nova interface!

Esse plugin me salva

This plugin is not compatible with the latest releases of WordPress. I really liked the feature for being able to switch between classic and gutenberg editing - it was perfect for migrating sites to gutenberg.

Not compatible with WP6


I wish this was installed automatically instead of hello dolly!


I wish this was standard

No comments


I know the block editor is a major effort, but I still find it gets in my way more than it helps. For me, enabling the Classic Editor is a necessity.


One of my must-have plugins


Thanks for this!!! This makes my life easier!


LOVE IT

My favorite Editor.


I really thankful wordpress team for their work but gutenberg is a wrong turn in wordpress history.


Best plugin ever


Must have plugin. Simple, fast and easy to use.


no block no pain :)


Simple understandable and really better than blocks at this time, maybe in the future I move to blocks but currently I'm using classic mode. 


Good

Love it


Classic Editor is simple, fast, and reliable. It keeps the editing experience clean without unnecessary distractions. I appreciate how stable it is even with the latest WordPress versions. A must-have plugin for those who prefer the traditional way of editing content.


Still the Most Reliable Editor

Enables the previous "classic" editor and the old-style Edit Post screen with TinyMCE, Meta Boxes, etc. Supports all plugins that extend this screen.

Priority Shortcodes vs Classic Editor