ཞིབ་བརྗོད།
Classic Editor is an official plugin maintained by the WordPress team that restores the previous (“classic”) WordPress editor and the “Edit Post” screen. It makes it possible to use plugins that extend that screen, add old-style meta boxes, or otherwise depend on the previous editor.
Classic Editor is an official WordPress plugin, and will be fully supported and maintained until at least 2022, or as long as is necessary.
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.
In addition, the Classic Editor plugin includes several filters that let other plugins control the settings, and the editor choice per post and per post type.
By default, this plugin hides all functionality available in the new Block Editor (“Gutenberg”).
གཏུབ་རེིས།
Admin settings on the Settings -> Writing screen. 
User settings on the Profile screen. Visible when the users are allowed to switch editors. 
"Action links" to choose alternative editor. Visible when the users are allowed to switch editors. 
Link to switch to the Block Editor while editing a post in the Classic Editor. Visible when the users are allowed to switch editors. 
Link to switch to the Classic Editor while editing a post in the Block Editor. Visible when the users are allowed to switch editors. 
Network settings to select the default editor for the network and allow site admins to change it. 
The "Switch to Classic Editor" link.
FAQ
- Default settings
-
When activated this plugin will restore the previous (“classic”) WordPress editor and hide the new Block Editor (“Gutenberg”).
These settings can be changed at the Settings => Writing screen. - Default settings for network installation
-
There are two options:
- When network-activated this plugin will set the Classic Editor as default and prevent site administrators and users from changing editors.
The settings can be changed and default network-wide editor can be selected on the Network Settings screen. - When not network-activated each site administrator will be able to activate the plugin and choose options for their users.
- When network-activated this plugin will set the Classic Editor as default and prevent site administrators and users from changing editors.
- Cannot find the “Switch to Classic Editor” link
-
It is in the main Block Editor menu, see this screenshot.
གདེང་འཇོག
2020 ལོའི་ཟླ 2 ཚེས 11 ཉིན།
Bu eklentiyi kaldırmayın, çünkü hayat kurtarıyor..
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
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!
2020 ལོའི་ཟླ 2 ཚེས 7 ཉིན།
Classic editor is the best editing plugin for wordpress users. I have used this plugin last one year. Thanks !
2020 ལོའི་ཟླ 2 ཚེས 6 ཉིན།
Гутенберг - реальная помойка, клиенты плачут .... Спасибо за классический редактор!!!
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.
བྱས་རྗེས་འཇོག་མཁན། & གསར་འབྱེད་པ།
“Classic Editor” is open source software. The following people have contributed to this plugin.
བྱས་རྗེས་འཇོག་མཁན།
“Classic Editor” has been translated into 52 locales. Thank you to the translators for their contributions.
ཁྱེད་ཀྱི་སྐད་ཡིག་ནང་ལ་ “Classic Editor” ཡིག་སྒྱུར་བྱོས།
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
དག་བཅོས་ཉིན་ཐོ།
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-editorquery 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_settingsfilter.
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_postandclassic_editor_enabled_editors_for_post_typefilters. Can be used by other plugins to control or override the editor used for a particular post of post type. - Added
classic_editor_plugin_settingsfilter. 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.