Opis

💬
Dear and respected members of the WordPress community, especially those who still believe that „Code is Poetry” — believe it or not, there are people like me for whom this removed feature still matters.

This plugin restores the classic
“Visual Editor Options”
section to the user profile screen.

It’s a clean, dependable tweak — made for those who prefer writing in plain text, without distraction, without visual clutter.

No extra settings. No noise. Just the option that once was.

Perfect for:

writers who live in the HTML tab,
developers who avoid visual editors,
or anyone who simply misses that checkbox.

It works with both the Classic and Block editors,
and doesn’t require any additional plugins.

Just install, and enjoy the silence of plain text.

How It Works

A checkbox labeled “Disable the visual editor when writing” is added to each user’s profile page.
When checked, the plugin disables visual editing features and saves the preference (rich_editing = false).
Both TinyMCE and Gutenberg are bypassed — only the plain text editor is shown.

Additional behaviors (enabled by default):

Prevents loading of unnecessary editor scripts and styles for users who opt out.
Removes visual editor metaboxes when not needed.
Displays a dismissible admin notice if visual editing is disabled but the plugin is no longer active.

Compatibility

Works with both Classic and Block (Gutenberg) editors.
Compatible with the Genesis Framework and most modern themes.
Functions independently — does not require the Classic Editor plugin.
Honors native WordPress capabilities like user_can_richedit and use_block_editor_for_post.

Translations

This plugin is translation-ready.
Currently available in:

Japanese (thanks to @kimipooh)

If you would like to contribute a translation, please visit:
https://translate.wordpress.org/projects/wp-plugins/classic-visual-editor-options/

Zrzuty ekranu

Instalacja

Upload the plugin to /wp-content/plugins/ or install it directly via Plugins > Add New.
Activate the plugin.
Go to Users > Your Profile, check “Disable the visual editor when writing”, and save changes.
Done. The editor will now default to plain text for that user.

Najczęściej zadawane pytania

Does this really disable Gutenberg?: Yes — for users who disable the visual editor. The plugin uses native filters to bypass both Gutenberg and TinyMCE.
What about other users on the site?: Nothing changes for them unless they also choose to disable the visual editor in their profile.
Do I need the Classic Editor plugin installed?: No. This plugin works entirely on its own.
Is it safe to use with other editor-related plugins?: Yes — as long as those plugins respect WordPress coding standards and core filters.
Is this plugin actively maintained?: Yes — by a developer who still writes in HTML mode.

Recenzje

joxmiguel 2026-05-29 1 odpowiedź

Finally a plugin that works, thank you so much for this, really.

Daffydd57 2025-11-06 1 odpowiedź

Why the WP devs would think it was okay to remove the „Disable Visual Editor” option in a user’s profile is beyond idiotic. This plug in puts it back. That’s all it does – no other bloat or extra code – clean and simple. THANK YOU!!!

kimipooh 2025-09-05 1 odpowiedź

Thank you for providing such a great plugin!I translated the main part into Japanese \^^/;. When entering code in the classic editor, the forced substitution function would sometimes be activated in the visual editor, so this feature was very useful. I agree with Gutenbeng’s philosophy, but it’s a shame that the option for a simpler editor is disappearing.

mikemacd 2025-09-01 4 odpowiedzi

I would like to mirror what vizons said in his review. Like vizons, I am also not a fan of wysiwyg editors and I also like having full control over how I write. WordPress used to leave the edit-mode in either visual or text mode – which ever you were using last – so that if you were editing in text mode, the site stayed in text mode. Then they changed it so that if defaulted to opening visual mode on every edit, which is when I changed my user profile to have the visual mode disabled. Now they disabled that option which I only discovered today when adding a new user to a site. WordPress – why force me to edit in a mode I don’t like? Happily I found the Classic Visual Editor Options plugin in a comment from the author on Reddit thread. Super! Thank you SO much for producing this lightweight, problem-solving tool. It solves the problem perfectly!

vizons 2025-06-26 1 odpowiedź

I was completely distraught yesterday to find that every time I saved my post in classic editor that it kept saving it in visual mode. I use a Mac and write all my posts in textedit plain text mode so I can style it with css and then paste all of my writing/code into the classic editor. I was deeply depressed yesterday about the fact that the WordPress developer team decided to remove the text/code saving capability. The way they downgraded this option is completely backwards because for people like me who never had the „disable visual editor when writing” in user profile checked, it causes major issues when writing and saving in text/code mode. I never had that option checked before they completely removed it because the classic editor always worked the way I like to use it which is stay in text/code mode when writing and saving my posts. As you said in the post on your website about restoring the freedom of choice concerning the classic editor, they took away our freedom to use classic editor according to our preferences. I am NOT a fan of wysiwyg editors. I like having full control over what I create. Thank you many, many times over for creating this plugin. When I found it this morning, it was like the sun came out from a dark, dismal day!!!!!

Przeczytaj 5 recenzji

Kontrybutorzy i deweloperzy

„Classic Visual Editor Options” jest oprogramowaniem open source. Poniższe osoby miały wkład w rozwój wtyczki.

Supracorona

Wtyczka „Classic Visual Editor Options” została przetłumaczona na 1 język. Podziękuj tłumaczom za ich wkład.

Przetłumacz wtyczkę “Classic Visual Editor Options” na swój język.

Interesuje cię rozwój wtyczki?

Przeglądaj kod, sprawdź repozytorium SVN lub czytaj dziennik rozwoju przez RSS.

Rejestr zmian

1.0.5

Updated plugin author identity for consistency with the WordPress.org profile.
Updated screenshots using the WordPress 7.0 dashboard.

1.0.4

Updated „Tested up to” to WordPress 7.0 after successful compatibility testing.

1.0.3

Fixed explicit script version parameter for WordPress Plugin Check compliance.

1.0.2

Updated „Tested up to” to WordPress 6.9.
Prefixed a global variable to meet WordPress PHPCS standards.
Added a minor security hardening check for $_SERVER['PHP_SELF'].
General maintenance and compatibility updates.

1.0.1

Added Japanese translation credit (@kimipooh)
Readme updates

1.0.0

Initial release.
Plugin was originally submitted as “Restore Visual Editor Options.”
Renamed to Classic Visual Editor Options for clarity and naming consistency.

Excellent!!!

Perfect!!

Great plugin!

Brilliant plugin – Thank you!

Thank you so much for CLASSIC VISUAL EDITOR OPTIONS PLUGIN!!!

Opis

How It Works

Compatibility

Translations

Zrzuty ekranu

Instalacja

Najczęściej zadawane pytania

Does this really disable Gutenberg?

What about other users on the site?

Do I need the Classic Editor plugin installed?

Is it safe to use with other editor-related plugins?

Is this plugin actively maintained?