New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Decide where the block editor stays and where the Classic Editor comes back. It also removes Global Styles, patterns, block widgets and block CSS. | You have to log in to add a translation. | Details |
Original untranslated
Decide where the block editor stays and where the Classic Editor comes back. It also removes Global Styles, patterns, block widgets and block CSS.
You have to log in to edit this translation. |
|||
| ↑ | No Gutenberg? - Choose Where to Use the Block Editor or the Classic Editor | You have to log in to add a translation. | Details |
Original untranslated
No Gutenberg? - Choose Where to Use the Block Editor or the Classic Editor
CommentPlugin name. You have to log in to edit this translation. |
|||
| With classic themes, and with plugins that do not depend on blocks, yes: it removes block features instead of fighting them for control. Block themes are the exception, and there is a question about them right below. A plugin that registers blocks of its own keeps working, but those blocks lose their styles on the frontend if you remove the block assets, which is what the status panel is there to warn you about. | You have to log in to add a translation. | Details | |
Original untranslated
With classic themes, and with plugins that do not depend on blocks, yes: it removes block features instead of fighting them for control. Block themes are the exception, and there is a question about them right below. A plugin that registers blocks of its own keeps working, but those blocks lose their styles on the frontend if you remove the block assets, which is what the status panel is there to warn you about.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Everything comes back immediately: the block editor, Global Styles, the patterns and the block assets. Your content is exactly as it was, because the plugin never rewrote any of it. | You have to log in to add a translation. | Details | |
Original untranslated
Everything comes back immediately: the block editor, Global Styles, the patterns and the block assets. Your content is exactly as it was, because the plugin never rewrote any of it.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| No. Activating the plugin disables everything across the site. The settings page under Settings > No Gutenberg? is there only if you want to bring some part of the block editor back. | You have to log in to add a translation. | Details | |
Original untranslated
No. Activating the plugin disables everything across the site. The settings page under Settings > No Gutenberg? is there only if you want to bring some part of the block editor back.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| That is it. The block editor is disabled across the site and the Classic Editor is back | You have to log in to add a translation. | Details | |
Original untranslated
That is it. The block editor is disabled across the site and the Classic Editor is back
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| It fits sites that:↵ - Work better in the Classic Editor and want it back↵ - Run classic themes and plugins that were never built around blocks↵ - Are paying for block CSS and JavaScript on pages with no blocks in them↵ - Need the Classic Editor for everyone except a few post types, roles or people↵ - Are a multisite network that wants the same editing experience on every site | You have to log in to add a translation. | Details | |
Original untranslated
It fits sites that:↵
- Work better in the Classic Editor and want it back↵
- Run classic themes and plugins that were never built around blocks↵
- Are paying for block CSS and JavaScript on pages with no blocks in them↵
- Need the Classic Editor for everyone except a few post types, roles or people↵
- Are a multisite network that wants the same editing experience on every site
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| <strong>A default that asks nothing, and a settings page for everything else</strong> - Activating the plugin disables the block editor and every block feature across the site, which is what most people install it for. The rest of this page is about wanting less than that. | You have to log in to add a translation. | Details | |
Original untranslated
<strong>A default that asks nothing, and a settings page for everything else</strong> - Activating the plugin disables the block editor and every block feature across the site, which is what most people install it for. The rest of this page is about wanting less than that.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Nothing else: leave blocks on for products and the block product editor keeps working | You have to log in to add a translation. | Details | |
Original untranslated
Nothing else: leave blocks on for products and the block product editor keeps working
CommentFound in description list item. You have to log in to edit this translation. |
|||
| The WooCommerce block styles and scripts, removed along with the rest of the block assets | You have to log in to add a translation. | Details | |
Original untranslated
The WooCommerce block styles and scripts, removed along with the rest of the block assets
CommentFound in description list item. You have to log in to edit this translation. |
|||
| The block based product editor, which follows the same rules as any other post type | You have to log in to add a translation. | Details | |
Original untranslated
The block based product editor, which follows the same rules as any other post type
CommentFound in description list item. You have to log in to edit this translation. |
|||
| The block editor assets in the admin, wherever the Classic Editor is the one opening | You have to log in to add a translation. | Details | |
Original untranslated
The block editor assets in the admin, wherever the Classic Editor is the one opening
CommentFound in description list item. You have to log in to edit this translation. |
|||
| The block assets of any other plugin that registers blocks, on pages where no block appears | You have to log in to add a translation. | Details | |
Original untranslated
The block assets of any other plugin that registers blocks, on pages where no block appears
CommentFound in description list item. You have to log in to edit this translation. |
|||
| The Global Styles inline CSS, which dequeuing the handle never reaches | You have to log in to add a translation. | Details | |
Original untranslated
The Global Styles inline CSS, which dequeuing the handle never reaches
CommentFound in description list item. You have to log in to edit this translation. |
|||
| The block library CSS and JavaScript that every page loads | You have to log in to add a translation. | Details | |
Original untranslated
The block library CSS and JavaScript that every page loads
CommentFound in description list item. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.