Download

经典编辑器

By WordPress Contributors

Description

经典编辑器是由WordPress团队维护的官方插件，用以恢复较早版本（“经典”）的WordPress编辑器和“编辑文章”页面。此插件亦能供其他扩展该页、加入旧式meta box及其他依赖经典编辑器的插件使用。

经典编辑器是一个WordPress官方插件，会被支持及维护到至少2022年，或视需要延长。

总的来说，这个扩展加入了以下功能：

  • 管理员可以为所有用户设置默认编辑器。
  • 管理员可以允许用户修改他们的默认编辑器。
  • 如果允许，则用户可自由选择为每篇文章使用何种编辑器。
  • 无论由谁最后编辑，每篇文章都会以最后使用的编辑器打开。因为这能让编辑内容时的使用体验保持一致。

除此之外，传统编辑器插件包含了数个过滤器，能够让其他插件控制相关设置，亦能选择每篇文章或每种文章类型的编辑器选择。

此插件默认隐藏所有区块编辑器（“古腾堡”）的所有功能。

Screenshots

  • 设置 > 撰写页面的管理设置。
  • 在个人资料页面的用户设置。仅在用户能够切换编辑器时显示。
  • “动作链接”来选择另一个编辑器。仅在用户能够切换编辑器时显示。
  • 使用传统编辑器编辑文章时会显示的切换到区块编辑器的链接。仅在用户能够切换编辑器时显示。
  • 使用区块编辑器编辑文章时会显示的切换到传统编辑器的链接。仅在用户能够切换编辑器时显示。
  • 为网络选择默认编辑器及允许站点管理员进行修改的网络设置。
  • “切换到传统编辑器”链接。

FAQ

默认设置

在激活时，此插件会把WordPress的编辑器复原为较早版本（“经典”）的WordPress编辑器，并隐藏新的区块编辑器（“古腾堡”）。
这些设置可在设置 > 撰写页面中修改。

网络安装的默认设置

有两个选项：

  • 在站点属于网络时，此插件会将经典编辑器设为默认，并阻止站点管理员及用户修改编辑器。
    此设置可被修改。全网络默认的编辑器可在网络设置页选择。
  • 在站点不属于网络时，每个站点的管理员都能激活此插件并为用户选择编辑器。
找不到“切换到传统编辑器”链接

出现在区块编辑器主菜单中，请参见这张截图。

Reviews

Keep this plugin Classic Editor

2020年2月10日
Hi Thank you for availability A good program should have decent processing on the server. WordPress has shifted to heavyweight rather than lightweight processing Just compare the Gothenburg loading time with the classic one. Just ask for two simultaneous writing processes in Gothenburg! The core of WordPress forget that many users use shared servers. Members of the WordPress Core are active on a powerful dedicated server, But other public users are mostly on shared servers, There are not many virtual servers that users move to, They are very expensive and require expertise and support, Many users do not have the knowledge and money to do so , Instead of less processing, Gutenberg only changes the code and appearance of the data, Classic plug-in processing extremely low, Unfortunately, the WordPress team forgets to activate the release of its own debug, Activating other languages indicates status, Gutenberg wants sequential processing time to load each part, But the classic plugin displays them in 1 fast processing. You just need to understand when using server resources check. Just enable debugging and error recording to find out. This classic extension has been active since 5 million and Gutenberg 200,000. This means that many users will prefer the old version after testing it. That is, for the audience it is more important than the innovation of correct processing quality and low error. I hope the Gutenberg team will come to an understanding of what the audience needs, not the costly thinking. Keep enduring classic. Classic team Don't be tired Thanks to all the WordPress team members and developers

Please save Classic Editor as long as possible: results of my own test

2020年2月9日
I have been testing both, Classic Editor and Gutenberg. First I had learned and got used to using Gutenberg (I have 2 websites in different languages, so the content is equal - one of them was updated to Gutenberg while the 2d was left with Classic Editor). I did it for more than 1 year. So here's the result: one needs to spend +50% more time to publish the same article using Gutenberg! It's an awful waste of time!!! Please consider to keep this Classic Editor plugin up-to-date as long as possible (2022 is too close). Because GUTENBERG IS DEGRADATION and not the improvement!

useful for old school users and web developers

2020年2月5日
Even though I see how the Gutenberg block editor is useful and helfpul to non-technical people, for me personally I still prefer to have direct access to my HTML and CSS so I installed this useful plugin which brings back the classic editor.
Read all 771 reviews

Contributors & Developers

“经典编辑器” is open source software. The following people have contributed to this plugin.

Contributors

“经典编辑器” has been translated into 52 locales. Thank you to the translators for their contributions.

Translate “经典编辑器” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.5

  • Updated for WordPress 5.2 and Gutenberg 5.3+.
  • Enhanced and fixed the “open posts in the last editor used to edit them” logic.
  • Fixed adding post state so it can easily be accessed from other plugins.

1.4

  • On network installations removed the restriction for only network activation.
  • Added support for network administrators to choose the default network-wide editor.
  • Fixed the settings link in the warning on network About screen.
  • Properly added the “Switch to Classic Editor” menu item to the Block Editor menu.

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

Initial release.

Meta

Ratings

See all

Support

Issues resolved in last two months:

1 out of 22

View support forum