Jonathan Desrosiers

Linchpin

Aaron Ware

Note: This plugin does not support the block editor but should continue to work without issue when using it with custom post types and the <a href="https://wordpress.org/plugins/classic-editor/" rel="ugc">Classic Editor Plugin</a>.
Before WordPress displays a post’s content, the content gets passed through multiple filters to ensure that it safely appears how you enter it within the editor.
One of these filters is <a href="https://codex.wordpress.org/Function_Reference/wpautop" title="wpautop" rel="nofollow ugc">wpautop</a>, which replaces double line breaks with <code></code> tags, and single line breaks with <code> </code> tags. However, this filter sometimes causes issues when you are inputting a lot of HTML markup in the post editor.
This plugin displays a checkbox in the publish meta box of the post edit screen that disables the <a href="https://codex.wordpress.org/Function_Reference/wpautop" title="wpautop" rel="nofollow ugc">wpautop</a> filter for that post.
Also adds a ‘wpautop’, or ‘no-wpautop’ class to the post_class filter to help with CSS styling.

Toggle wpautop

Easily disable the default wpautop filter on a post by post basis.

Martyn Chamberlin

If you’ve ever had a WordPress blog post or page in which you found yourself writing more than a little HTML, you’ve experienced the frustration of finding your beautiful markup surrounded in <code></code> tags. The problem only gets worse when you start throwing jQuery into the mix. Who on earth gave WordPress permission to throw in <code> </code> tags inside a <code><script></code>, anyhow?!
Up until now, we’ve only had a couple of options:
<ul>
<li>First, we could use conditional logic to require an external PHP file. This was bad for several reasons.
<ul>
<li>It’s not friendly for the end user. Who wants to have to edit a PHP file?</li>
<li>The content is not in the WordPress database, which means it isn’t searchable inside the dashboard, and it isn’t backed up with the rest of the site.</li>
<li>It removes framework functionality. Robust WordPress frameworks have places to add content above and below the main post content area, and an external PHP file destroys this greatly.</li>
</ul>
</li>
<li>The second option is to use the existing plugins to disable WordPress formatting, but none of these plugins empower the user to toggle this setting on a page-by-page basis. After all, most articles don’t have that much <code>HTML</code> in them. Nobody wants to go through 500 old blog posts and manually add <code></code> tags to them, do they? We didn’t think so either.</li>
</ul>
As a web designer that’s used WordPress successfully for several years, I finally decided these shenanigans had to stop once and for good. I built a simple but elegant plugin that lets you disable auto-generated HTML on a page-by-page basis.
I hope you use and enjoy Don’t Muck My Markup as much as I enjoyed building it.
Note: this plugin does not work on all WordPress themes, because some themes don’t handle the filter sequence correctly. This plugin does work for well-programmed themes such as the Twenty Fourteen theme and the Genesis Framework (and child themes).

Don't Muck My Markup

Click disable auto-formatting for this post still allows Visual to be clicked, which generated auto-formatting.

To work in all cases, clicking Visual best also be disabled.

Kind works.

Don't Muck My Markup lets you disable all auto-generated HTML markup from your posts and pages on a page-by-page basis.

Toggle wpautop vs Don't Muck My Markup