Granular control to disable Gutenberg and enable the Legacy (TinyMCE) Editor per post type with automatic settings redirect.

Vaibhaw Kumar

<p>The V7 Legacy Editor Enabler plugin provides fine-grained control over the WordPress editor experience. Since WordPress 5.0, Gutenberg (Block Editor) became the default editor, but many users prefer the familiar legacy TinyMCE editor interface. This plugin allows you to disable Gutenberg and enable the Legacy Editor selectively for different post types.</p>
<h4>Why Choose V7 Legacy Editor Enabler?</h4>
<p>V7 Legacy Editor Enabler gives you <strong>granular control</strong>:<br />
* Choose Legacy Editor for Posts only, or Pages only, or both<br />
* Automatic redirect to settings page after activation for instant configuration<br />
* Per-post-type control – Perfect for mixed workflows<br />
* Clean, professional code built with WordPress security standards<br />
* Zero external dependencies – Lightweight and fast</p>
<h4>Perfect For</h4>
<ul>
<li><strong>Content Creators</strong>: Use Legacy Editor for blog posts while keeping Gutenberg for landing pages</li>
<li><strong>Developers</strong>: Clients who prefer Legacy Editor but want modern page building tools</li>
<li><strong>Hybrid Workflows</strong>: Mix Legacy and Gutenberg editors based on content type</li>
<li><strong>Performance</strong>: Minimal overhead with clean, efficient code</li>
</ul>
<h4>Key Features</h4>
<ul>
<li><strong>Selective Enablement</strong>: Choose which post types use Legacy Editor (Posts, Pages, or both)</li>
<li><strong>Automatic Redirect</strong>: Redirects to settings page immediately after activation for easy configuration</li>
<li><strong>User-Friendly Settings</strong>: Simple checkbox interface under Settings menu</li>
<li><strong>Post-Type Specific</strong>: Control editor per post type independently</li>
<li><strong>Professional Code</strong>: Built with WordPress best practices and security standards</li>
<li><strong>Lightweight</strong>: Minimal impact on site performance</li>
</ul>
<h4>How It Works</h4>
<ul>
<li><strong>Posts</strong>: Enable/disable Legacy Editor for blog posts</li>
<li><strong>Pages</strong>: Enable/disable Legacy Editor for static pages</li>
<li><strong>Flexible Control</strong>: Mix and match – use Legacy for posts but Gutenberg for pages, or vice versa</li>
</ul>
<h4>Privacy & GDPR Compliance</h4>
<p>V7 Legacy Editor Enabler is fully GDPR compliant:<br />
* <strong>No Data Collection</strong>: This plugin does not collect, store, or transmit any personal data<br />
* <strong>No Cookies</strong>: No cookies are set by this plugin<br />
* <strong>No External Services</strong>: No external API calls or third-party services<br />
* <strong>No Tracking</strong>: No analytics or user tracking of any kind<br />
* <strong>Local Storage Only</strong>: All settings are stored locally in your WordPress database</p>
<h3>Additional Info</h3>
<h4>Requirements</h4>
<ul>
<li>WordPress 5.0 or higher</li>
<li>PHP 7.4 or higher</li>
</ul>
<h4>Support</h4>
<p>For support, bug reports, or feature requests:</p>
<ul>
<li><strong>Author:</strong> Vaibhaw Kumar</li>
<li><strong>Email:</strong> imvaibhaw@gmail.com</li>
<li><strong>Website:</strong> <a href="https://vaibhawkumarparashar.in" rel="nofollow ugc">vaibhawkumarparashar.in</a></li>
</ul>
<h4>Contributing</h4>
<p>Contributions are welcome! Please feel free to submit a Pull Request on <a href="https://github.com/TheVaibhaw/v7-legacy-editor-enabler" rel="nofollow ugc">GitHub</a>.</p>


Alternatives to V7 Legacy Editor Enabler

Top alternatives