Classic Editor +

Beschreibung

DSGVO-konform: Es werden keine Benutzerdaten gesammelt

The free „Classic Editor +“ plugin is targeted at everyone who does not want to use the WP Block Editor (Gutenberg), introduced in WordPress 5.0. Install it now on sites and the UX remains the same as you are used to without redundant styling being added to the frontend of your site!

What’s New:
No longer dependent on Classic Editor plugin; you may remove it.

This plugin simply disables the WP Block Editor, removes any and all styling from both front- and backend and disables the block editor for widgets too.

And if WooCommerce has been installed on the site, „Classic Editor +“ removes the block styles of that plugin too.

There are no Settings, it simply does what it says on the label.

Therefore I highly recommend installing this „Classic Editor +“ plugin.

I support this plugin exclusively through Github. Therefore, if you have any questions, need help and/or want to make a feature request, please open an issue here. You can also browse through open and closed issues to find what you are looking for and perhaps even help others.

Danke für dein Verständnis und deine Mitarbeit.

If you like the „Classic Editor +“ plugin, please consider leaving a review. Thanks!

„Classic Editor +“ by Pieter Bos and Greg Schoppe.

FAQ

What is the WP block editor?

The release of WordPress 5.0 came with a replacement of the TinyMCE editor you had gotten used to for adding or editing content. Some find it an improvement, others don’t. More information can be found on the WP 5.0 release post.

Why this plugin? Isn’t the purpose of the Classic Editor plugin to disable the new block editor?

The Classic Editor plugin does not remove any of the frontend styling, even when one selects the option to disable the block editor. In terms of site optimisation that is not good practice.
This „Classic Editor +“ simply removes the block editor and all its styling from both frontend and backend and if your site uses WooCommerce, it also removes block styling related to that from the frontend.

Do I still need the Classic Editor plugin on my site?

Version 4.0 of the „Classic Editor +“ plugin has been a complete rewrite (and simplification) and it is no longer depending on the Classic Editor plugin. When the latter is active, it will be deactivated and then you can safely remove it.

Ich habe ein Problem mit diesem Plugin, wo erhalte ich Hilfe?

Bitte öffne ein Issue auf Github (engl.)

Rezensionen

21. Dezember 2022 1 Antwort
I had serious issues editing a few pages. Somehow the Gutenberg block editor got stuck on and you couldn’t switch it back to classic. I added plugins to fix it such as “Enable Classic Editor” by Ayon GK, “Disable Gutenberg” by WebDevStudios and a few others. I had so many plugins deactivated and nothing was working even with this “Classic Editor Plus”. Those didn't fix anything. “Classic Editor Plus” must be used solo to work or so it seems. After all plugins were deactivated. I only activated “Classic Editor Plus” and Wa-La, it was fixed and that damn nasty block was gone. How to remove the block option is another issue but I won’t touch it. Call me old fashioned but I know my way around classic. Thanks guys.
24. November 2022 3 Antworten
Upon updating to this new version, today, the tweet urls are being removed in the editor's pane, as alien script. This is a major malfunction which makes the update useless to me.
30. April 2022 1 Antwort
Just fantastic for those who hate the new Gutenberg UI.
17. November 2020 1 Antwort
Gutenberg is a battle. It fights back. It won't let me do things I was always used to doing. I could publish in Classic, but my theme had a nasty habit of pushing Gutenberg back on me for edits after a piece was published. This seems to prevent that. Thank you!
Alle 26 Rezensionen lesen

Mitwirkende & Entwickler

„Classic Editor +“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

„Classic Editor +“ wurde in 11 Sprachen übersetzt. Danke an die Übersetzerinnen und Übersetzer für ihre Mitwirkung.

Übersetze „Classic Editor +“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

4.0.2

  • November 23, 2022
  • rename to prevent conflicts with other plugin

4.0.1

  • November 23, 2022
  • use consistent function prefixes
  • change FAQ readme

4.0

  • November 22, 2022
  • complete rewrite where dependency on Classic Editor plugin is removed
  • rename plugin

3.1.0

  • October 27, 2022
  • integrate Classic Widgets filters

3.0.1

  • January 24, 2022
  • adjust link to plugin search page

3.0.0

  • January 24, 2022
  • replaced dependency library with simple dependency check/notice, due to many issues with 2.6.4 security update

2.6.4

  • January 24, 2022
  • update WP Dependency Installer library
  • tested up to WP 5.9

2.6.3

  • August 3, 2020
  • rollback removal of WooCommerce block-ui scripts

2.6.2

  • August 1, 2020
  • remove WooCommerce block-ui scripts
  • update WP Dependency Installer
  • tested up to WP 5.5.0

2.6.1

  • March 5, 2020
  • update WP Dependency Installer to 3.0.0

2.6.0

  • November 14, 2019
  • update WP Dependency Installer to 2.0.0
  • increase minimum PHP version to 5.6 (requirement of WP Dependency Installer)
  • WP 5.3 compatible fixes this issue

2.5.0

  • October 11, 2019
  • add function that removes the 1 block editor style call from the <head> section of your site when WooCommerce is running

2.4.0

  • January 22, 2019
  • add function that removes the 2 block editor style calls from the <head> section of your site

2.3.1

  • December 17, 2018
  • increase minimum PHP version to 5.4 due to introduction new shorthand syntax of WP Dependency Installer update in 2.3.0

2.3.0

  • December 14, 2018
  • version update WP Dependency Installer
  • add parameter "optional": false as a workaround to fix issue #4

2.2.0

  • December 12, 2018
  • rewrite of function that removes settings of the Classic Editor plugin

2.1.1

  • 25. Oktober 2018
  • Tippfehler behoben, der das Issue #3 adressiert.

2.1.0

  • 28. August 2018
  • Funktionen entfernt, die seit dem Release 0.0.4 des klassischen Editor-Plugins redundant geworden sind.
  • Liesmich-Dateien umgeschrieben

2.0.0

  • 16. Juli 2018
  • WP Dependency Installer hinzufügen, um die Installation und Aktivierung des Classic-Editor-Plugins zu erleichtern (Farbe des Admin-Hinweises auf blau geändert).
  • Anpassung der minimalen PHP-Version (auf 5.3) durch Hinzufügen des WP-Dependency-Installers

1.4.0

1.3.0

  • 8. Juli 2018
  • Veröffentlichung des Plugins im WordPress-Plugin-Verzeichnis, bereit für die Welt 🙂

1.2.0

  • Anfang Juli 2018
  • mehr Feature-/Funktion-/Code-Verbesserungen durch Pieter und Greg

1.1.0

1.0.0