Klassieke editor


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 Klassieke editor. Visible when the users are allowed to switch editors.
  • Link to switch to the Klassieke 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 Klassieke editor" link.


Standaard instellingen

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.

Standaard instellingen voor netwerk installatie

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.
Cannot find the “Switch to Classic Editor” link

It is in the main Block Editor menu, see this screenshot.


14 september 2019
J'ai toujours trouvé WordPress intuitif. Toutes les améliorations étaient jusque là une option ou une modification qui ne changeaient pas trop l'écriture de mes articles. Au passage en Guttenberg, j'avais quelques articles en cours. J'avais donc l'écriture classique. Mais lorsque j'ai du créer un nouvel article, je me suis retrouvé perdu. Guttenberg était si nébuleux que je n'arrivais plus à me concentrer sur mon écriture. J'ai laissé passer les vacances en espérant qu'une pause éclaircirait ce nouveau mode dans ma tête. A la reprise, j'ai passé quelques heures pour essayer de comprendre la logique "Block" de guttemberg, entre les images et le texte. Mais rien à faire, je suis resté bloqué. J'étais désespéré. Je me suis dit que j'aurais plus vite fait d'apprendre le code Html. Et puis, le Plug-in "Classic Editor" est apparu. Le sauveur ! Je revis, plus de sueur ! Au vu du nombre de téléchargement, les concepteurs de WordPress devraient prendre en compte cette vague de contestations. Ceux que je plains, ce sont les nouveaux utilisateurs de WordPress qui doivent être complètement déroutés s'ils n'ont pas une bonne formation. Je pense même, que cela peut être un sérieux frein aux nouvelles installations. Guttenberg doit rester optionnel ou disparaître pour la pérennité de WordPress
11 september 2019
The wordpress managment f***ed up pretty good with theyr "new" and "awsome" editor. EVERY web site I make using clasic editor. I newer used the new one. I can't belive that they did that sh*t. I'm mad because I force to fix things, that worked well >:[
9 september 2019
Why do something new that has worse functionality?! Why make me and others tear our hair out? Really, guys, it's pathetic beyond belief. Did you even get feedback before making it the default? I guess I'll have to install this until you fix the new 'improved' default. WP used to be brilliant! Now you're taking it backwards. Not smart.
6 september 2019
This should be put back into core. My clients prefer it, I prefer it and I have yet to meet an average user who has worked with Gutenberg and doesn't prefer the Classic editor!
5 september 2019
Thank you to the devs who maintain this plugin. It works really well. Keep up the good work! Although saying that, it is completely ridiculous that it is necessary. A plugin to remove a terrible addition to core that should have remained a plugin itself. Hopefully Matt will rethink Gutenberg and actually listen to the community for a change, although I won't hold my breath on that one!
Lees alle 698 beoordelingen

Bijdragers & ontwikkelaars

“Klassieke editor” is open source software. De volgende personen hebben bijgedragen aan deze plugin.


“Klassieke editor” is vertaald in 48 talen. Dank voor de vertalers voor hun bijdragen.

Vertaal “Klassieke editor” naar jouw taal.

Interesse in ontwikkeling?

Bekijk de code, haal de SVN repository op, of abonneer je op het ontwikkellog via RSS.



  • Bijgewerkt voor WordPress 5.2 en 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.


  • 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.


  • 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.


  • 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.


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.


  • Bijgewerkt voor 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.


  • 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.


  • 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.
  • De leesmij-tekst bijgewerkt.


  • Updated the option from a checkbox to couple of radio buttons, seems clearer. Thanks to @designsimply for the label text suggestions.
  • Enkele algemene updates en opschoning.


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


Eerste versie.