Title: Code editor not being a code editor
Last modified: August 18, 2016

---

# Code editor not being a code editor

 *  [jloayza](https://wordpress.org/support/users/jloayza/)
 * (@jloayza)
 * [18 years, 7 months ago](https://wordpress.org/support/topic/code-editor-not-being-a-code-editor/)
 * I’ve been using WordPress for a year and half, not much, but enought to give 
   my personal evaluation. I think the whole application is great and the improvements
   are always fantastic.
 * Nevertheless, I find the code editor the only weak part of it. I’m not saying
   it’s a bad work, I could never say that. I mean that IMHO the code editor is 
   targetting to the wrong place. The main and only purpose of a code editor should
   be to be a code editor, and, as far as part of the code is not shown in the code
   editor (like paragraph tags), this one is not a code but a semi-code editor.
 * Again, IMHO the editor should be a tool for people with some or advanced knowledge
   in (x)html coding. Never another kind of user will dare to play in the code playgound,
   or at least it won’t be usual at all.
 * So, if only prepared people will use it ¿Why annoy them making them to think 
   in how a semi-code editor will interpret their code? Because the thing is that
   it do causes some annoying troubles with paragraphs, blockquotes and line breaks.
 * I understand it has to have a code debbuger, after all, to avoid unclosed tags,
   and so on, in order to not cause troubles not only in the code, but with in the
   wysiwyg editor. However. Is not any other way to do it? Because I have even had
   some troubles with the code editor that, writting my clean code, it has converted
   it in not valid code. Really.
 * In fact, after some small troubles during the last months, this post is motivated
   after my little nightmare today trying to insert [this very small portion](http://www.realidadaparte.es/ejemplos/wp_code_editor_problem.txt)
   of very valid code.
 * It took me like 5 minutes to finally manage to do it. And in a very unstable 
   way, as if I open the wysiwyg editor again and just click “save” (whithout doing
   anything in the middle) it mess it up again.
 * So, my choice, after my very long explanation, would be a code editor as is. 
   Where every tag is shown, and that it doesn’t touch anything as far as every 
   tag is opened and closed correctly, so valid in this way.

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [locomotion](https://wordpress.org/support/users/locomotion/)
 * (@locomotion)
 * [18 years, 6 months ago](https://wordpress.org/support/topic/code-editor-not-being-a-code-editor/#post-620966)
 * damn
    i couldntve said it any better
 * actually yhis is the only thing that makes me not use WP
 *  [hooperabus](https://wordpress.org/support/users/hooperabus/)
 * (@hooperabus)
 * [18 years, 6 months ago](https://wordpress.org/support/topic/code-editor-not-being-a-code-editor/#post-620975)
 * Great post, jloayza! I agree, as well! Especially on my web sites that use WordPress,
   but are not chronological blogs.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Code editor not being a code editor’ is closed to new replies.

 * In: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/)
 * 2 replies
 * 3 participants
 * Last reply from: [hooperabus](https://wordpress.org/support/users/hooperabus/)
 * Last activity: [18 years, 6 months ago](https://wordpress.org/support/topic/code-editor-not-being-a-code-editor/#post-620975)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics