Title: Classic Visual Editor Options
Author: DVeb
Published: <strong>30 mai 2025</strong>
Last modified: 3 décembre 2025

---

Recherche d’extensions

![](https://ps.w.org/classic-visual-editor-options/assets/banner-772x250.png?rev
=3303475)

![](https://ps.w.org/classic-visual-editor-options/assets/icon-256x256.png?rev=3303446)

# Classic Visual Editor Options

 Par [DVeb](https://profiles.wordpress.org/supracorona/)

[Télécharger](https://downloads.wordpress.org/plugin/classic-visual-editor-options.1.0.2.zip)

 * [Détails](https://fr.wordpress.org/plugins/classic-visual-editor-options/#description)
 * [Avis](https://fr.wordpress.org/plugins/classic-visual-editor-options/#reviews)
 *  [Installation](https://fr.wordpress.org/plugins/classic-visual-editor-options/#installation)
 * [Développement](https://fr.wordpress.org/plugins/classic-visual-editor-options/#developers)

 [Support](https://wordpress.org/support/plugin/classic-visual-editor-options/)

## Description

💬
 _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

 1. A checkbox labeled **“Disable the visual editor when writing”** is added to each
    user’s profile page.
 2. When checked, the plugin disables visual editing features and saves the preference(`
    rich_editing = false`).
 3. 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/

## Captures d’écrans

 * [[
 * Legacy versions of WordPress where the checkbox was removed.
 * [[
 * The restored checkbox — default state (unchecked).
 * [[
 * The restored checkbox — active (checked), visual editor disabled.

## Installation

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

## FAQ

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

## Avis

![](https://secure.gravatar.com/avatar/2c9640283b2a646acb6bfd5c4d0cce9d0b9a7b409d69916edbbcdadf8069347b?
s=60&d=retro&r=g)

### 󠀁[Perfect!!](https://wordpress.org/support/topic/perfect-10869/)󠁿

 [Daffydd57](https://profiles.wordpress.org/daffydd57/) 6 novembre 2025 1 réponse

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!!!

![](https://secure.gravatar.com/avatar/18963c13fec955584ebe959bd1c96309ebc59af1cff18642a4c3d0fe0e23a04b?
s=60&d=retro&r=g)

### 󠀁[Great plugin!](https://wordpress.org/support/topic/great-plugin-40816/)󠁿

 [kimipooh](https://profiles.wordpress.org/kimipooh/) 5 septembre 2025 1 réponse

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.

![](https://secure.gravatar.com/avatar/45b54e7c4547933fcad612baa76f69ed4cf2e584d52da069826093ee3da48081?
s=60&d=retro&r=g)

### 󠀁[Brilliant plugin – Thank you!](https://wordpress.org/support/topic/brilliant-plugin-thank-you-6/)󠁿

 [mikemacd](https://profiles.wordpress.org/mikemacd/) 1 septembre 2025 4 réponses

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!

![](https://secure.gravatar.com/avatar/b62f04b967993a61e686339b25cf5a35dcebbfd5527828ad2453ca6941340f55?
s=60&d=retro&r=g)

### 󠀁[Thank you so much for CLASSIC VISUAL EDITOR OPTIONS PLUGIN!!!](https://wordpress.org/support/topic/thank-you-so-much-for-classic-visual-editor-options-plugin/)󠁿

 [vizons](https://profiles.wordpress.org/vizons/) 26 juin 2025 1 réponse

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!!!!!

 [ Lire les 4 avis ](https://wordpress.org/support/plugin/classic-visual-editor-options/reviews/)

## Contributeurs/contributrices & développeurs/développeuses

« Classic Visual Editor Options » est un logiciel libre. Les personnes suivantes
ont contribué à cette extension.

Contributeurs

 *   [ DVeb ](https://profiles.wordpress.org/supracorona/)

“Classic Visual Editor Options” a été traduit dans 1 locale. Remerciez [l’équipe de traduction](https://translate.wordpress.org/projects/wp-plugins/classic-visual-editor-options/contributors)
pour ses contributions.

[Traduisez « Classic Visual Editor Options » dans votre langue.](https://translate.wordpress.org/projects/wp-plugins/classic-visual-editor-options)

### Le développement vous intéresse ?

[Parcourir le code](https://plugins.trac.wordpress.org/browser/classic-visual-editor-options/),
consulter le [SVN dépôt](https://plugins.svn.wordpress.org/classic-visual-editor-options/),
ou s’inscrire au [journal de développement](https://plugins.trac.wordpress.org/log/classic-visual-editor-options/)
par [RSS](https://plugins.trac.wordpress.org/log/classic-visual-editor-options/?limit=100&mode=stop_on_copy&format=rss).

## Journal des modifications

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

## Méta

 *  Version **1.0.2**
 *  Dernière mise à jour **il y a 5 mois**
 *  Installations actives **900+**
 *  Version de WordPress ** 5.0 ou plus **
 *  Testé jusqu’à **6.9.4**
 *  Version de PHP ** 7.4 ou plus **
 *  Langues
 * [English (US)](https://wordpress.org/plugins/classic-visual-editor-options/) 
   et [Japanese](https://ja.wordpress.org/plugins/classic-visual-editor-options/).
 *  [Traduisez la dans votre langue](https://translate.wordpress.org/projects/wp-plugins/classic-visual-editor-options)
 * Étiquettes
 * [classic editor](https://fr.wordpress.org/plugins/tags/classic-editor/)[disable editor](https://fr.wordpress.org/plugins/tags/disable-editor/)
   [plain text](https://fr.wordpress.org/plugins/tags/plain-text/)[user profile](https://fr.wordpress.org/plugins/tags/user-profile/)
   [visual editor](https://fr.wordpress.org/plugins/tags/visual-editor/)
 *  [Vue avancée](https://fr.wordpress.org/plugins/classic-visual-editor-options/advanced/)

## Évaluations

 5 sur 5 étoiles.

 *  [  4 avis à 5 étoiles     ](https://wordpress.org/support/plugin/classic-visual-editor-options/reviews/?filter=5)
 *  [  0 avis à 4 étoile     ](https://wordpress.org/support/plugin/classic-visual-editor-options/reviews/?filter=4)
 *  [  0 avis à 3 étoile     ](https://wordpress.org/support/plugin/classic-visual-editor-options/reviews/?filter=3)
 *  [  0 avis à 2 étoile     ](https://wordpress.org/support/plugin/classic-visual-editor-options/reviews/?filter=2)
 *  [  0 avis à 1 étoile     ](https://wordpress.org/support/plugin/classic-visual-editor-options/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/classic-visual-editor-options/reviews/#new-post)

[Voir tous les avis](https://wordpress.org/support/plugin/classic-visual-editor-options/reviews/)

## Contributeurs

 *   [ DVeb ](https://profiles.wordpress.org/supracorona/)

## Support

Quelque chose à dire ? Besoin d’aide ?

 [Voir le forum de support](https://wordpress.org/support/plugin/classic-visual-editor-options/)