Classic Editor

Descrición

Classic Editor é un plugin oficial mantido polo equipo de WordPress que restaura o editor anterior (“clásico”) de WordPress e a pantalla de “Editar entrada”. Fai posible usar plugins que estenden esta pantalla, engaden metaboxes co estilo anterior ou dependen de calquera outra maneira do editor anterior.
Por defecto este plugin oculta todas as características dispoñibles no novo Editor de bloques (” Gutenberg”).

At a glance, this plugin adds the following:

  • Administrators can select the default editor for all users.
  • Administrators can allow users to change their default editor.
  • When allowed, the users can choose which editor to use for each post.
  • Each post opens in the last editor used regardless of who edited it last. This is important for maintaining a consistent experience when editing content.

Ademais, Classic Editor inclúe varios filtros que permiten que outros plugins controlen os axustes e a elección de editor por publicación e por tipo de contido.

Classic Editor é un plugin oficial de WordPress e recibirá mantemento e actualizacións polo menos ata 2022.

Capturas

  • Axustes do administrador na pantalla Axustes -> de Lectura.
  • Axustes de usuario na pantalla Perfil. Visible cando os usuarios teñen permitido cambiar de editor.
  • "Ligazóns de acción" para elixir editor alternativo. Visible cando os usuarios teñen permitido cambiar de editor.
  • Ligazón para cambiar ao Editor de bloques cando estás a editar unha entrada no Editor de clásico. Visible cando os usuarios teñen permitido cambiar de editor.
  • Ligazón para cambiar ao Editor clásico cando estás a editar unha entrada no Editor de bloques. Visible cando os usuarios teñen permitido cambiar de editor.
  • Axuste de rede para permitirlle aos editores de sitio cambiar as opcións por defecto.

Comentarios

Right plugin at the right time.

All my websites are built with custom fields. after upgrading to 5.0 I was totally worried about gutenberg. It may be easy but I still love the classic editor. all the themes I developed with the support of classic editor. Now I am happy that i’m using wp latest version 5.0 without any trouble.

SO HAPPY That this exists, I was panicking and scared until I found it

I manage a lot of website SEO for clients, about 1,000 articles and posts and pages a year. If this plugin had not been here I would have been totally just lost in my business. My workload for customers would have gone up so much I wouldn’t have been able to handle it. I was literally scared, as I spent the afternoon trying desperately to find a way to make the pages like I used to using Gutenburg and couldn’t. Scared me.

Saved me

Gutenberg has some major issues with ACF, arguably the most important plugin for WP developers. Switching back to the Classic Editor is a must until the Gutenberg bugs are all worked out.

How low will it take to sink in?

So since the release of WordPress 5.0, this Classic Editor plugin has been gaining about 100,000 new installs per day. Meanwhile, every few minutes the Gutenberg plugin receives a new 1-star rating. There is a 5-star rating every now and then, mostly by users who accidentally forgot to change the default 5-star rating to a 1-star rating.

I wonder how long it will take for the people behind WordPress to realize that Gutenberg was not wanted. My bet is that it will take a long time. If you have a look at the Make WordPress Core section of this website, it’s all about blocks, blocks, blocks, blocks, blocks, blocks, blocks, blocks, blocks, blocks, blocks, blocks, blocks, blocks, blocks, blocks, blocks, blocks and then some more blocks. If you look at the Plugins section, plugins that support blocks with fewer than 10 active installs are heavily promoted.

All good things come to an end and unfortunately WordPress is no exception.

Ler todas as 235 opinións

Colaboradores e desenvolvedores

“Classic Editor” é un software de código aberto. As seguintes persoas colaboraron con este plugin.

Colaboradores

“Classic Editor” foron traducidas ao 39 locales. Grazas a os desenvolvedores polas súas colaboacións.

Traducir “Classic Editor” ao teu idioma.

Interesado no desenvolvemento?

Revisa o código, bota unha ollada aorepositorio SVN, ou subscríbete ao log de desenvolvemento por RSS.

Rexistro de cambios

1.3

  • Fixed removal of the “Try Gutenberg” dashboard widget.
  • Fixed condition for displaying of the after upgrade notice on the “What’s New” screen. Shown when the Classic Editor is selected and users cannot switch editors.

1.2

  • Fixed switching editors from the Add New (post) screen before a draft post is saved.
  • Fixed typo that was appending the edit URL to the classic-editor query var.
  • Changed detecting of WordPress 5.0 to not use version check. Fixes a bug when testing 5.1-alpha.
  • Changed the default value of the option to allow users to switch editors to false.
  • Added disabling of the Gutenberg plugin and lowered the required WordPress version to 4.9.
  • Added classic_editor_network_default_settings filter.

1.1

Fixed a bug where it may attempt to load the Block Editor for post types that do not support editor when users are allowed to switch editors.

1.0

  • Updated for WordPress 5.0.
  • Changed all “Gutenberg” names/references to “Block Editor”.
  • Refreshed the settings UI.
  • Removed disabling of the Gutenberg plugin. This was added for testing in WordPress 4.9. Users who want to continue following the development of Gutenberg in WordPress 5.0 and beyond will not need another plugin to disable it.
  • Added support for per-user settings of default editor.
  • Added support for admins to set the default editor for the site.
  • Added support for admins to allow users to change their default editor.
  • Added support for network admins to prevent site admins from changing the default settings.
  • Added support to store the last editor used for each post and open it next time. Enabled when users can choose default editor.
  • Added “post editor state” in the listing of posts on the Posts screen. Shows the editor that will be opened for the post. Enabled when users can choose default editor.
  • Added classic_editor_enabled_editors_for_post and classic_editor_enabled_editors_for_post_type filters. Can be used by other plugins to control or override the editor used for a particular post of post type.
  • Added classic_editor_plugin_settings filter. Can be used by other plugins to override the settings and disable the settings UI.

0.5

  • Updated for Gutenberg 4.1 and WordPress 5.0-beta1.
  • Removed some functionality that now exists in Gutenberg.
  • Fixed redirecting back to the Classic Editor after looking at post revisions.

0.4

  • Fixed removing of the “Try Gutenberg” call-out when the Gutenberg plugin is not activated.
  • Fixed to always show the settings and the settings link in the plugins list table.
  • Updated the readme text.

0.3

  • Updated the option from a checkbox to couple of radio buttons, seems clearer. Thanks to @designsimply for the label text suggestions.
  • Some general updates and cleanup.

0.2

  • Update for Gutenberg 1.9.
  • Remove warning and automatic deactivation when Gutenberg is not active.

0.1

Versión inicial.