Comparison · generated on request
Disable Gutenberg vs FrontEdit – Live Frontend Block Editor
Both plugins as this registry currently observes them. Figures come from the same daily snapshot, so they are directly comparable, which two separate wordpress.org pages, read minutes apart, are not.
| Disable Gutenberg | FrontEdit – Live Frontend Block Editor | |
|---|---|---|
| What it does | Disable Gutenberg Block Editor and restore the Classic Editor and original Edit Post screen (TinyMCE, meta boxes, etc.). | Make content updates easier. Now supporting Custom Post Types. Clients and teams can update live pages safely with zero wp-admin training. |
| Active installs | 500,000+ | 2,000+ |
| Rating | 5.0★ (735) | 5.0★ (2) |
| Last release | 2 months ago | 4 days ago |
| Current owner | Jeff Starr | Pierce |
| Added to directory | 18 Apr 2018 | 20 Jul 2026 |
| Tested up to | WP 7.1 | WP 7.1 |
| Requires PHP | 5.6.20 | 7.4 |
Install figures are rounded by WordPress.org to one significant digit, so a gap smaller than a band step is not a difference. Nothing here ranks the two plugins or recommends either, and no link on this page earns anything.
Why this page is not in search results
There are roughly 1.8 billion possible pairs of WordPress plugins. Generating them would be scaled content abuse, so this registry does not: a comparison renders for anyone who asks for it, and is offered to search engines only once 25 different people have asked for that same pair within 60 days. This one has been requested by 0. Until it crosses, the page works normally but stays out of the index.
Records: Disable Gutenberg · FrontEdit – Live Frontend Block Editor