Disable Gutenberg
This plugin disables the new Gutenberg Editor (aka Block Editor) and replaces it with the Classic Editor. You can disable Gutenberg completely, or selectively disable for posts, pages, roles, post types, and theme templates. Plus you can hide the Gutenberg nag, menu item, and more! ♠ The all-in-one, COMPLETE solution for handling Gutenberg ♠ Hide ALL traces of Gutenberg and replace with Classic Editor ♠ Restores original Edit Post screen (TinyMCE, meta boxes, etc.) The Disable Gutenberg plugin restores the classic (original) WordPress editor and the “Edit Post” screen. So you can continue using plugins and theme functions that extend the Classic Editor. Supports awesome features like Meta Boxes, Quicktags, Custom Fields, and everything else the Classic Editor can do. Easy to Use Just activate and done! The default plugin settings are configured to hide all traces of the Gutenberg Block Editor, and fully restore the original Classic Editor. Further options for customizing when/where Gutenberg is enabled are available in the plugin settings. ♠ Disable Block Widgets and restore Classic Widgets 🙂 Options Disable Gutenberg completely (all post types) Disable Gutenberg for any post type Disable Gutenberg for any user role Disable Gutenberg for any theme template Disable Gutenberg for any post/page IDs Disable Gutenberg admin notice (nag) Option to restore Classic Widgets Option to hide the plugin menu item Option to hide the Gutenberg plugin menu item (settings link) Adds “Classic Editor” link to each post on the Posts screen Adds item to the WP sidebar menu: “Add New (Classic)” Option to enable Custom Fields Meta Box for ACF Choose which editor to use for each post Whitelist any post title, slug, or ID Option to enable/disable frontend Gutenberg stylesheet ♠ Works same as Classic Editor plugin, but can do a LOT more! ♠ Lightweight and super fast, built with WP APIs 🙂 Fully configurable, enable or disable Gutenberg and restore the Classic Editor wherever is necessary. Automatically replaces Gutenberg with the Classic Editor. Features Super simple Clean, secure code Built with the WordPress API Lightweight, fast and flexible Regularly updated and “future proof” Works great with other WordPress plugins Plugin options configurable via settings screen Focused on flexibility, performance, and security One-click restore plugin default options Translation ready ♠ Works great with Google AMP and the WordPress AMP plugin Disable Gutenberg is developed and maintained by Jeff Starr, 15-year WordPress developer and book author. Super light & fast plugin, super easy on server resources! Why? Gutenberg is a useful editor but sometimes you want to disable it for specific posts, pages, user roles, post types, and/or theme templates. This plugin enables you to disable Gutenberg and replace it with the Classic Editor wherever you want. For example, lots of WordPress users already enjoy robust page-building functionality via one of the many great plugins like Composer or Elementor. So many options, no need to feel “locked in” to using Gutenberg! If you like Disable Gutenberg, please give it a 5-star rating, thank you! Privacy This plugin does not collect or store any user data. It does not set any cookies, and it does not connect to any third-party locations. Thus, this plugin does not affect user privacy in any way. Support development I develop and maintain this free plugin with love for the WordPress community. To show support, you can make a donation or purchase one of my books: The Tao of WordPress Digging into WordPress .htaccess made easy WordPress Themes In Depth Wizard’s SQL Recipes for WordPress And/or purchase one of my premium WordPress plugins: BBQ Pro – Blazing fast WordPress firewall Blackhole Pro – Automatically block bad bots Banhammer Pro – Monitor traffic and ban the bad guys GA Google Analytics Pro – Connect WordPress to Google Analytics Head Meta Pro – Ultimate Meta Tags for WordPress REST Pro Tools – Awesome tools for managing the WP REST API Simple Ajax Chat Pro – Unlimited chat rooms USP Pro – Unlimited front-end forms Links, tweets and likes also appreciated. Thanks! 🙂
Top keywords
- gutenberg23×3.53%
- disable16×2.46%
- editor16×2.46%
- wordpress15×2.30%
- classic14×2.15%
- disable gutenberg12×1.84%
- classic editor10×1.54%
- post10×1.54%
- pro8×1.23%
- hide5×0.77%
- meta5×0.77%
- option5×0.77%
Quick Translate POT/PO/MO
Quick Translate POT/PO/MO Plugin Manual 1. Introduction “Quick Translate POT/PO/MO” is a tool for generating and modifying WordPress plugin translation files. It allows you to instantly see the effects of your changes and complete the following tasks directly in your browser. Generate POT files (Translation Template): Extract translatable strings from a plugin’s source code to create a template file. Generate and Update PO files (Translation File): Create a new PO file for a specific language based on a POT file, or update an existing one. Edit PO Files: Directly edit translation strings in an existing PO file. Generate MO Files (Binary File): Automatically create the binary MO file that WordPress uses when you save your PO file edits. PO File Automatic Translation Tool: It automatically translates the untranslated parts of a PO file using Google Translation or DeepL. Download POT, PO, and MO Files: Download each POT, PO, and MO file to your local directory. Delete MO Files: Remove unnecessary MO files. 2. How to Use Step 1: Generating a POT File Go to the “1. Generate POT file” section. Select the target plugin from the “Select a Plugin” dropdown. Click the “Generate POT” button. If a POT file already exists, a confirmation pop-up will appear. ➡ This will create a [text-domain].pot file in the plugin’s languages directory. Step 2: Generating and Updating a PO File Go to the “2. Generate / Update PO file from POT” section. Select the target plugin from the “Select a Plugin” dropdown. Click the “Generate / Update PO” button. ➡ This will generate a PO file (e.g., ja.po) based on your WordPress language settings. ➡ If the PO file already exists, the existing translations (msgstr) corresponding to the strings (msgid) in the POT file will be preserved in the updated PO file. Step 3: Editing a PO File and Generating an MO File Go to the “3. Edit PO file & Generate MO file” section. Select the target plugin from the “Select a Plugin” dropdown. Click “Load PO” to display the PO file contents in a table. Edit translations directly in the “msgstr” column. Click “Save Changes and Generate MO” to save changes and create the MO file. ➡ Changes in the editor are saved to the PO file and the MO file is generated simultaneously only when you click the “Save Changes and Generate MO” button. For more effective translation work: Step 2.5: Automatically Translate a PO File Click the “Go to PO Auto Fill Tool” button. Select the target plugin from the “Select a Plugin” dropdown. Choose either Google API or DeepL API. Enter the corresponding API key. Click the “Preview Translation” button. Click the “Save” button to save the results to the PO file. Click the “Back to Quick Translate POT/PO/MO” button to edit the saved PO file. ➡ To use this tool for automatic translation, you need to register with Google Translation or DeepL and obtain an API key. Both services can be used within their free usage limits. Table Operations msgid (Source String): Original string (not editable). msgstr (Translation): Editable translation string. Download A POT File Click the “Download POT” button to download the current POT file. Download A PO File Click the “Download PO” button to download the current PO file. Download A MO File Click the “Download MO” button to download the current MO file. Deleting an MO File Click the “Delete MO” button to remove the current MO file.