WordPress Visual Editor – Do you Use It?

September 21st, 2007

One of the very first tasks I always perform on every new WordPress installation I do is to go into my user profile and turn off the visual WYSIWYG editor. I prefer to handle all my formatting markup myself because it gives me more control over the final product. The other day, Mark suggested that most ‘professional’ bloggers also prefer not to use the visual editor.

So, the question I throw out to you, the reader, is this – which do you prefer to use, the visual editor or the basic editor, and why?

Extra credit: Do you use any formatting plugins for faster, easier, on-the-fly markup? If you use one of these plugins, why do you use that specific markup plugin? For instance, I use TextileWrapper on my own blog because I like how easy it is to add just a single character or two to a line or phrase to get the formatting I want. I originally used Text Control – and I still prefer – but it broke on a WordPress upgrade awhile back and is no longer being supported by the author, forcing me to find an alternative. TextileWrapper is an excellent plugin in its own right and continues to function well through each upgrade.




  1. jo says:

    no, it’s awful.

  2. Dzamir (1 comments.) says:

    I always use the “code only” version of the editor.

  3. lambic (1 comments.) says:

    I switched to the Visual editor after upgrading to 2.1. Before that it was awful but it has improved to the point where I hardly ever have to switch to the code view

  4. allaboutduncan (1 comments.) says:

    No visual editor for me. Like to be able to control all the code myself. For help in composing posts, I do use Texter to automatically generate code I reuse often with only a few keystrokes.

  5. Mark (1 comments.) says:

    Turned off visual editor right away. I hate how it’s trying to “fix” my html… it butchers it every time instead!

  6. Enrique (1 comments.) says:

    I use the basic editor, most of the time the visual one ruins my posts alignnment. I’m not sure if it’s a common issue, atleast on firefox.

  7. Jonathan (83 comments.) says:

    I’m with you guys on this one. I use the “code” editor, the visual editor is pretty bad and is certainly not something I like to deal with. I use the code view simply because often I will add custom classes to images or lists or videos, and I don’t want those getting in the way with the visual editor.

  8. Aja Lapus (4 comments.) says:

    That’s the first thing I do as well. I do not know if these are still issues for the current release, but the visual editor chokes on some HTML attributes I enter manually, and it adds unnecessary <p> elements that break my markup completely.

    And, since I usually add code in my posts, I think I’m better off seeing everything under the hood instead of what’s just on the surface.

  9. Jason Litka (3 comments.) says:

    I don’t know if I’d call myself “professional”, but yes, I do use the default editor. I can only think of one occasion over the past 50 posts where I needed to use the code view and that was only to look, not to edit.

  10. Danny (2 comments.) says:

    I don’t like the visual editor. The only time I use it is when I paste something that has html formatting already, as it preserves that.

    I have not upgraded to a WordPress version that allows me to toggle simply between the editors, and I probably should. As it is now, it’s a minor hassle to go from one to the other on that once-a-week occasion when I want to paste into the visual editor.

  11. Steven Hodson (3 comments.) says:

    I don’t use the editor at all. I prefer to use a stand alone blog editor such as Windows Live Writer or ecto for Windows

  12. jez (56 comments.) says:

    I dont use it, it evilizes the code to coin a term there.

  13. Liquid Egg Product (2 comments.) says:

    I hate the visual editor. Part of it is the start up and response time. The bigger part is the greater control–I tend to stick in span tags with css styles, and find it quicker and easier to type it myself. Not even sure if it’s possible to do floating elements with the visual editor.

  14. Erik Pöhler (5 comments.) says:

    This Screenshot says it all, no? XStandard “for Open Source Partner-CMS” in the WP-Backend

    also see my slides on integration at Webmonday. Maybe i should do a Screencast illustrating my pluins features…

  15. Sarah (5 comments.) says:

    I don’t use the editor at all. I immediately turn it off. It’s annoying.

  16. Erik Pöhler (2 comments.) says:

    For some reason the link is gone. So again:

  17. redwall_hp (40 comments.) says:

    I use the WYSIWTH editor, because It’s a lot quicker for me to hit ctrl-i than to type <i>…</i>.

  18. courtney (1 comments.) says:

    NOPE! lol

  19. Erik Pöhler (5 comments.) says:

    Ahh, and this is what my profile-page looks like: for easy switching of WYSIWYG-Editors.

  20. Mark Ghosh (386 comments.) says:

    I wish the code editor would work with the Ctrl buttons, that would be my perfect WYSWYG!

  21. Ian Stewart (1 comments.) says:

    When the bulk of your blog writing is going to be a series of paragraphs with one or two links, being snobby about using only the code editor is, frankly, weird.

    I use both, defaulting to the visual editor.

  22. Jim Stitzel (27 comments.) says:

    I wish the code editor would work with the Ctrl buttons, that would be my perfect WYSWYG!

    I can’t argue with that idea. That would almost provide me enough motivation to give up Textile, depending on how such a thing was implemented.

    When the bulk of your blog writing is going to be a series of paragraphs with one or two links, being snobby about using only the code editor is, frankly, weird.

    For me personally, it’s less about ‘snobby’ and more about the fact that I do a LOT of on-the-fly markup with Textile that the visual editor doesn’t really support.

  23. Ike (13 comments.) says:

    Wow. Why all the hate? Control freaks with beehives in their bonnets.

    I help set up WordPress sites and blogs for friends. I don’t want them to have to muck around with code – they needed my help BECAUSE they don’t want to learn HTML.

    As such, I use the visual editor. Not because I can’t hand code, but because I want to intuitively walk them through any questions they might have. And given the training I am providing for them for a specific project, I don’t want to start doing things they can’t do outside of the comfort zone.

    I certainly hope code-jockeys don’t start waving an informal poll like this as “proof” that the visual editor needs to be trashed. Improved? Yes.

  24. helge (1 comments.) says:

    no, it destroys most codes that i paste into the HTML box.

  25. Mark Ghosh (386 comments.) says:

    Ike and Ian, this IS an informal question and NOT a suggestion that the visual editor be removed or replaced. It is more of an exploration of how people use the visual editor and how one’s blogging can be improved via enhancements to the present editor.

  26. Jim Stitzel (27 comments.) says:

    I should add that, yes, use the basic editor is about control, but I think what’s actually more important for me than that, even, is workflow. I type a lot faster than I point-and-click, so I can links and formatting – even in raw HTML – two or three times faster than I can mouse-click it into existence. That’s reason enough for me to use the basic.

    Of course, not everyone is code savvy, so I would never recommend that the visual editor be trashed. There’s obviously folks who prefer the visual over the basic. But an overhaul of the visual would definitely go far, in my opinion.

  27. Michael (3 comments.) says:

    Ever since I noticed the superfluous HTML produced by Mambo’s (another CMS) editor, I have preferred editing the code by myself. It gives you the flexibility of adding elements that the editor doesn’t support, and lets you precisely control the output.

  28. Baris Unver (17 comments.) says:

    I use and love the rich editor TinyMCE (except its efforts to tidy up the HTML) (it fudges the code sometimes), but I don’t think it should be a core element of WordPress. I’d prefer it to be a plugin.

  29. sam (1 comments.) says:

    I use FCKEdit for basic writing, but I always go into the “source” edit to make sure all of the coding is correct – otherwise I end up with lots of extra paragraph breaks and stuff.

  30. Schadenfreude (1 comments.) says:

    I use the Advanced TinyMCE editor. It’s got all of the bells and whistles that I need. I very rarely have to switch to the code view.

  31. Rob in Denver (1 comments.) says:

    Can’t stand the visual editor. It’s slow and clunky and almost always does something I don’t want it to do… like strip out an image.

    I, too, like the flexibility and control the code editor provides.

  32. Erik Pöhler (5 comments.) says:

    Well, i see… most bloggers seem to be code savvy folks. But why should i train others, that simply want to publish? Give em a _working_ WYSIWYG and be happy not to worry about improperly nested elements, relative URLs in your Feeds (invalid), images without size-attributes, etc. etc. etc.

    A good WYSIWYG-Editor gets more important as your authors (in fact: they really love to) use copy & paste when they publish their MS Word documents.

    @Baris Unver (#28): You’re speaking the truth, here. I totally agree with that one. TinkerMCE imho is a bit too deeply merged into the core files.

  33. Demi Fantasy (2 comments.) says:

    I use the visual editor because I can edit faster and I can switch to the “Code tab” whenever I want to edit some HTML.

    Hence, since I am using TinyMCE plugin, when I want to color up some of my writing, I don’t have to remember the color’s HTML code. That makes things easier!

  34. Jesse Harris (10 comments.) says:

    I’ve been using the EditorMonkey implementation of TinyMCE since I started using WordPress and have been rather impressed with it. It simplifies writing posts quickly and has a great file upload interface. Even though it’s been abandoned for many months, I’ve been happy to continue using it with the 2.1 branch. For those rare times when I need to do the markup on my own, there’s still a source editor that allows me to do my own touch-up.

    About the only beef I have with TinyMCE is that I can’t insert PHP code into a post without turning it off. Aside from that, using manual markup is like always growing your own vegetables when you feel like a salad: the results might be better, but not enough to justify the extra effort.

  35. tim finin (1 comments.) says:

    I always use the basic editor. If it could be more like emacs I’d like it even better.

  36. John (1 comments.) says:

    I tried using the visual editor but it makes a mess of the code too often for me to trust it.

    With the visual editor turned on it is possible to toggle between WYSIWYG and code, which is nice, but the WYSIWYG component still frells things.

  37. kelly (1 comments.) says:

    I don’t use the editor. I have plugins that require the editor to be off anyways, I don’t really have any other reason.

  38. Cody (21 comments.) says:

    I always use the WYSIWYG editor partly because I’m too lazy to turn it off and also because I rarely, if ever, put in any extra markup in my posts. If I need to do that, I switch to the code view and add it in. Luckily for me, the CTRL shortcuts work with me, so I can add in italics and bolding as easily as I could in a word processor, with few mouse clicks at all. I’ve never had any major problems, and I type a lot quicker when I don’t have to use angle brackets (or whatever are).

  39. Patrix (6 comments.) says:

    Redundant question to ask simply because the answers are predictable. Geek and techies will like to say they don’t use the visual editor but ‘ordinary’ bloggers will say they love it. Of course, it is another fact that the latter outnumber the former by a wide margin.

  40. KimHoon (1 comments.) says:

    Always code editor.

  41. mmeida (4 comments.) says:

    No, I use neither the publisher nor formatting plugins.

  42. Anders Dahnielson (2 comments.) says:

    The first thing I do on every installation/upgrade is to completely remove the TinyMCE files. I can’t really see a need for it, since the necessary markup in blog post is usual very simple and should be simple (mostly links, some em and an occasional strong here and there). Instead I’m using a modified quicktag.js file for all my markup needs.

  43. GaMerZ (24 comments.) says:

    I use code editor, I also prefer to have control over what I am typing including HTML codes

  44. Scurvy Jake (1 comments.) says:

    I can’t stand the visual editor, it drives me nuts. I don’t use any other editing plugins, either. They always end up doing something weird to my code, or not providing the markup options I want to use.

  45. Jess Planck (2 comments.) says:

    Of course I use it, since I developed that silly WP Super Edit Plugin for it.

    It does boil down to the end user ALWAYS, and I was very happy when the “Visual / Code” toggle was introduced. I have clients / users that have the full range of skill levels, so having a “pluggable” Visual editor is quite necessary for doing some very slick integration.

    One interesting thing I always noticed is that folks with HTML skills hate it, but some of those highly skilled folks could probably help to make it better. For instance… There are wpautop and other javascript functions that can and do wreck some of the HTML, BUT they are in a file that is NOT pluggable. I’m still checking that one out.

  46. jem says:

    Nope, never it just messes things up. I use Markdown instead, much easier

  47. KJToo (1 comments.) says:

    I find that the Visual Editor interferes with how I’m used to writing blog entries (manual marking up the text as I go). Rather than just abandoning the idea of a visual editor, I briefly installed the TinyMCE plug-in, but that didn’t do it for me, either, so I just went back to doing all of my own markup. That’s not to say the visual editor is a bad idea; I’m just not ready to use it.

  48. Tommi (1 comments.) says:

    I use the visual editor, because sometimes it feels faster than typing the html codes. However, I have noticed that I also do some fine tuning with the code editor for every post. May be I should try out and turn off the visual editor.

  49. Marc (1 comments.) says:

    I don’t use the visual editor. It was slow and clunky, then when I wanted to do something non-standard, it was a huge pain. I’ve been much happier since I gave it up.

  50. Nicole (2 comments.) says:

    I think the visual editor was fine for basic text posts (no images or code) before there was a change in version.. well, I don’t remember what version it was. In any case, at some point, the visual editor seemed to get a lot slower and more clunky, and I stopped using it entirely after that. So whereas before I only switched to the code version when I had to put in an image with a special class or write code, now its the way I keep it constantly.

  51. Jaypee (20 comments.) says:

    Disabling the Visual or WYSIWYG editor is also one of the first things I do when I do a fresh install of WordPress. Like most of you guys, I prefer to have more control over html codes and markups.

  52. Kevin (1 comments.) says:

    personally I never use the built-in editor (code or WYSIWYG). I only use Qumana for posting.

  53. Richard Catto (34 comments.) says:

    I use Dean’s FCKEditor For WordPress. It creates some markup that I don’t like, though, and I always check the source before publication.

  54. adam (39 comments.) says:

    i’ve been using the visual editor non-stop since 2.1 (i tried using the version in 2.0, but it didn’t work as well as the version).
    I can write valid HTML all day, but that doesn’t mean i want to use html . And i’m not about to learn textile just to type posts.

  55. Stedi says:

    Fifty fifty

  56. Mike (4 comments.) says:

    I don’t like the WYSIWYG editor, and I spend enough time editing posts on team blogs by people who do use it to make me resent it quite heartily.

  57. Flo (1 comments.) says:

    I don’t use the visual editor because it didn’t bring me much benefit and caused trouble repeatedly. I don’t use any formatting plugins, but it sounds like it might be a topic worth investigating…

  58. Martin says:

    I use w.blogger for all my porting needs :)

  59. sputnik (1 comments.) says:

    Nope, don’t use it.

  60. John P. (3 comments.) says:

    I write html on my static web site all the time but I do use the visual editor for writing posts. 95% of the time, all I’m doing is simple writing with links. The visual editor is fine for that. The other 5% of the time when I’m using images, I’ll go to the code editor so I can use basic inline CSS to format for feeds. However, going back and forth is not without it’s problems with all the para tags that wind up in the translation.

  61. Todd (2 comments.) says:

    I’m not a pro and I’m too lazy to learn all the necessary code that I use to make my blog fancy. I only manipulate manually when something doesn’t look good to me, no matter how messy the code gets. This has caused some issues for some of my users, but they are mostly on PC and since I am a snob, I don’t fix it — I’m hoping to motivate them to become a Mac adopter.

  62. Ian Stewart (4 comments.) says:

    Sorry, I guess that came out wrong, Mark. Just chalk me up for defaulting to the Visual Editor. :)

  63. Michelle (1 comments.) says:

    I turn it off because I use a customized quicktags file that takes into account the plugins I use such as fancy pull quotes and fuzzy colorpicker.

  64. pilgrim (2 comments.) says:

    I use the code editor, as a rule. I did try the tinyMCE “super edit” plugin for a while, but it didn’t include a button for the CITE tag, which apart from image inserts is the code I most frequently drop into a post, so back I came to the code editor.

    Prompted by Anders’ comment above (#40) however, I’ll be looking into creating a CITE button of my very own…

  65. Jack (1 comments.) says:

    Once you get into the HTML thinking mind, a Visual Editor seems useless. I admin that it does help with linking pages and images, but its not really needed.

  66. Nemo de Monet (5 comments.) says:

    If the visual editor were in some way easily configurable – not necessarily to the extent that, say, SpamKarma is – to suit my personal preferences and needs, I might use it. As it is, I see it as a one-size-fits-none “feature” I can, and do, quite happily live without.

  67. Michael (1 comments.) says:

    Don’t use it. It’s especially annoying on a Mac.

  68. Donovan (1 comments.) says:

    Until I recently upgraded from 2.01 to 2.2.3, I had it turned off. Now, I use it primarily and rarely use the code view. The main problem I have is that the visual editor doesn’t like it when I drop YouTube code in to put in an embedded video. I have to put it in on the code view and save it. If I reopen it, then the visual editor messes is up a bit.

    So all in all, the current visual editor is just fine for my needs most of the time.

  69. Chuck @ Detroit Times (6 comments.) says:

    Nope, I use Window’s Live Writer, which is in Beta 3 Now. I blog from a client, because it’s easier and I don’t have to go to WordPress’s GUI every damn time I wanna post. I also use scribefire, which is a Firefox Plug in, as well. However, I am glad the Visual editor is there, helps at times, It just could be a wee bit better. :)

  70. ShaolinTiger (2 comments.) says:

    I always turn the visual editor off, I can’t stand it.

    I use BBCode plugin for quick XHTML inserts, that’s all.

    Most people who install WordPress ask me how to turn the visual editor off too.

  71. GoodThings2Life says:

    I not only use the Visual Editor, I go into the plugin and force the “Advanced” toolbar to be enabled and I disable the WordPress option to “fix” code. That allows me all the options I want while still maintaining the ability to do coding when I want and need to.

  72. Matt (23 comments.) says:

    I first started blogging on sites that I wasn’t using notepad on (way back in 98). I had no visual editor then – why would I need one now?

  73. Emu (1 comments.) says:

    No. When I setup my blog and start writing post WYSIWYG editor broke some of links that I wrote by hand. I spent some time to browse WordPress code to find, how to turn it off. Finally I found appropriate setting in database and turn it off. Then I found that there is an option for that :).

    I use BBCodeExtra Firefox extension to help me with markup.

    Regards Emu

    P.S. Sorry for my bad english

  74. Matt (23 comments.) says:

    Wow. That’s what I get for trying to speak my mind when I JUST woke up.

    *fix* (sorry for the double post – please delete other comment if necessary)

    I first started blogging on sites that I wasn’t using a visual editor on, but just plain ol notepad. (way back in 98). I had no visual editor then – why would I need one now?

  75. cimddwc (3 comments.) says:

    The visual editor messes up the code too much for my taste, too – I just use the regular code editor.

  76. Emily says:

    I absolutely despise the visual editor and turn it off first thing in my own installations of WP. I agree with everything people above have said: slow, clunky, “fixes” your code incorrectly. But I’m definitely a control freak, so using something like that is just against my nature.

    However, I do WP installations for clients all the time and I always leave the visual editor on for them. I can definitely understand that beginners or people unfamiliar with HTML (or are just lazy) would find it easier and faster to use. Plus, a lot of my clients come over from Blogger, which has a similar editor, so people like to use what is familiar. They just prefer it and it’s not worth it trying to explain why they shouldn’t use it.

  77. publicperv says:

    I think this is question of habit, but i enjoy coding myself.. :)

  78. Skunk Monkey (1 comments.) says:

    As a coder, I have always hated visual editors. The code they produce is often non-compliant and totally unreadable.

    Of course, if you have no clue about HTML, the visual editor is your only choice, short of learning to code.

  79. Matt (1 comments.) says:

    You can turn the visual editor off? Wow, I wish I had known this, I hated it after the upgrade. How do I do so?

  80. Jim Stitzel (27 comments.) says:

    Just go to your user profile and take the check out of the box at the top.

  81. nathan (5 comments.) says:

    It is way too annoying for me.

    BUT, non-coders seem to like it much, much better!

  82. Bill Larson (1 comments.) says:

    When you have multiple authors of varying abilities the visual editor is a good option.

  83. Aarne (1 comments.) says:

    I always use rich-editor. I also really hate that “code” button is removed from toolbar. So I after upgrade first thing I do is to hack a tiny_mce_config.php to re-enable it. That way I have rich editor with real HTML editing possibilities.

  84. ws (1 comments.) says:

    No, I’ve never used it and I don’t intend to. It’s slow, buggy, and gets caught up on complex HTML.

    The main problem with using one of the formatting plugins that keeps the markup intact is: what if you stop using it in the future?

  85. Chigüire (1 comments.) says:

    Wow, I didn’t know so many people hated the visual editor. I use it daily, although I use more the Ctrl key shortcuts, they work like charm.

    I frequently go to the code tab, but that’s because I have a couple of classes which float images, so I add the classes manually. I also upload all my images and then use the Insert function in the upload box.

    The only complaint I have is that the editor doesn’t grasp very well when I want to close a paragraph (i.e. when I center a ). There is an opportunity for a better visual editor to take over, but I’m actually happy to write with the default one.

  86. Mark (1 comments.) says:

    I use the Wysiwyg-editor but switch back and forth between the views a lot. I also use the advanced editor (alt+v) because I sometimes paste from Word or from an email and that actually works. I post a lot of stuff, that I get from others since my professional site is more like a webportal than a blog. I also use the Wysiwyg to put target=”_blank” and titles on the links which is way easier and quicker than in code-view.

    There’s room for improvement in the Wysiwyg but it’s getting better and more useful.

  87. aaron (2 comments.) says:

    I only use the visual editor to change the font size or color, because it’s quicker. Other than that, I stick with the code.

  88. Paul Kaiser (1 comments.) says:

    I use the visual editor along with the code editor. While personally I prefer to hand-code, the website at work needs to allow secretaries to be able to post without learning any HTML.

    The visual editor allows them to “Paste From Word” (UGH!) even, although I try to get them to “Paste as Plaintext” and then use basic markup where necessary.

    I do not allow them to put images in the post. I use the “post-image” plugin so that they can just upload photos to the post and the images will automatically be displayed with the post (wherever *I* tell the theme to show them.

  89. auschick (1 comments.) says:

    i use rich text because the visual editor screws up video embedding and tends to randomly strip out code

  90. Matt B. (13 comments.) says:

    The visual editor truly sucks. There’s nothing like writing the code yourself.

  91. Fish (4 comments.) says:

    I use ScribeFire [was Performancing] – not brilliant, but does the job. I’ve not used the WYSIWYG for a year; it always, *always*, every bleedin’ time, screwed up my paragraphs – especially since I’m still addicted to my [hr /] tags. I guess I should see if the visual editor has improved since, but it’s become a habit just to open the scribefire box.

  92. Vixx (2 comments.) says:

    Nope. Like you, it’s always the first thing I de-select with a new install.

    And I use markdown for pages where I wish to have total control of the code.

  93. Brian (2 comments.) says:

    Nope/never – just write the HTML out

  94. Kahi (1 comments.) says:

    One more option! :-) I don’t use any of the three options you mention in article, Jim. My choice is (at first sight) very similar to well known Textile, but I think it’s more sophisticated, it’s called Texy!. (In download section is a WP plugin as well.)

  95. nchenga says:

    i don’t like using the visual editor. First thing i change on a new WP install.

  96. Heliologue (2 comments.) says:

    Don’t personally use it. There’s enough special cases where I can’t really use the WYSIWYG. And I hate its formatting, anyway.

  97. Network Geek (1 comments.) says:

    Well, I’ve done entire websites in text editors, but I’m not sure if that qualifies me as a “coder” to the non-WYSIWYG editor snobs. And, I’ve had a blog for more than seven years now, two for more than five, but I don’t think I’d qualify as a “professional blogger”, either.

    Personally, I use the WYSIWYG editor for 98% of what I do, including images, but will often use the code view to make minor changes, like cleaning up copied text or adding a CSS class to images.

  98. Sparrowhawk says:

    The visual editor is the first option I de-select. It often produces non-compliant code.

  99. Vyoma (1 comments.) says:

    I do use the WYSIWYG editor in WP. But I usually review and tweak the code before hitting the Publish utton.

  100. rightwingprof (2 comments.) says:

    I hate it. On the rare occasions I need WYSIWYG, that’s why I have Dreamweaver — like when I embed a lot of table code. And speaking of tables, when I upgraded, I forgot to turn off the visual editor. I edited an article with two tables in it (but I did not touch the table code), and it trashed the tables.

  101. Tom (1 comments.) says:

    The visual editor always seems to corrupt innocent posts. Think of the posts!

  102. Cody (21 comments.) says:

    I can’t be the only one who’s never had the visual editor mess up my posts. I even put in images and links and have never had a problem.

  103. Titanas (5 comments.) says:

    Basic editor only. Lite on javascript and fast.

  104. Assenoff (1 comments.) says:

    Most of the time the WYSIWYG editor is enough for me. However, sometimes manual fine tuning of the code is needed.

  105. zapata says:

    me neither… it’s a pain… specially the paragraphing and the line spaces go off than what you intended it to be.

  106. David G. Johnson (1 comments.) says:

    I use the visual editor all the time, in fact I much prefer TinyMCE over FCKEditor — which is so frequently used in various CMS tools.

    Since I frequently set clients up (read: noobs) with WordPress, TinyMCE keeps them out of trouble.

    That being said, it isn’t uncommon for me personally to circumvent it when I have particular formatting needs. All in all, I’m glad it’s there.

  107. Mark (5 comments.) says:

    Nope. Don’t use it. But WordPress’s editor is not worse than most – they are mostly all awful.

  108. Webomatica (2 comments.) says:

    After a while I think I’ve figured out what the visual editor is useful for and for what it will break things.

    Useful: Insert images, lists, block quotes, links, basic formatting

    Breaks: Embedding code (YouTube or Flash videos) – have to do it in code view and if you toggle to the editor it will likely munge the embed code, breaking the blog. Likes to insert p tags whenever there’s a carriage return. Likes to replace div tags with p tags. If you have a complicated list forget it. Have to go into code view to insert adsense instances.

  109. mariano (3 comments.) says:

    no.. i truly hate it :P

  110. Doug Smith (2 comments.) says:

    I also turn off the visual editor first thing after an install . . . even on installs for newbies. I found that it is easier to teach them a little basic HTML than to figure out what the problem is when the visual editor messing things up.

    I often use the “AddQuicktag” plugin to create a few buttons to help new users with formatting. For example, an H3 header.

    The one thing that might sway me towards a GUI editor (besides it writing decent code) is if it could pick up some style definitions from the theme and create buttons to apply custom classes to a few elements.

  111. redwall_hp (40 comments.) says:

    In case you were wondering, WYSIWTH means What You See Is What The Heck.

    I like the visual editor okay, but it needs to stop mangling the code I write in the code tab. Forget pasting YouTube embeds, and JavaScript? Yeah, right. It needs to be fixed.

  112. Puck (1 comments.) says:

    I’m a top-notch HTML coder but I still use the WYSIWYG editor by default. I sometimes switch to “Code” view to add in a few things (like “lightbox” rel tags) but the majority is done in WYSIWYG simply because it’s… well, simple.

    I don’t understand the hate either. Other than text, bold, italics, and images what the heck code are you people consistently putting in your blogs that demand such low-level formatting tools be the default?

  113. AJK says:

    I use the visual editor most of the time, with some fine tuning using the code. I also use the “ST Visualize Advanced Features” plugin.

  114. Gregory Pittman (1 comments.) says:

    I never use the visual editor. I edit the quicktags file using Alex King’s JS Quicktags. The only problem with that is every time I upgrade my WordPress install I have to go find where I’ve saved the latest version of the file so I can reinstall it.

  115. Mosey says:

    I definitely use it! Whilst I am proficient with HTML (and can touchtype… don’t mean to sound arrogant at all but to put into context) why would I want to waste my time typing basic ‘bold’ and ‘italic’ (simple Ctrl-B) when it’s better spent writing content? :D The visual editor is not perfect by any length (I never ever edit tables with it) so the advanced editor is useful.
    I’m sure there are also many people who don’t know HTML and just want to post news.

  116. Jason (75 comments.) says:

    I use both the visual editor and the code editor. When I’m embedding and formatting pictures, the visual editor tends to mangle things terribly. Aside from that, the visual editor gets the job done.

    That said, it would be nice if the visual editor worked properly in Opera. I have to use a different browser whenever I post an entry.

  117. Jack Yan (2 comments.) says:

    I use both. I do detest the way WordPress second-guesses my coding when I switch to the visual editor, but I’d rather have the option than not have it since I often do cross-posts (given that my original post is marked up correctly).

  118. Fernando (1 comments.) says:

    I usually use the Visual editor, but afterward make a revision of code in order to prevent any errors. In some cases I write also with ecto for Mac.

    Best regards from Madrid, Spain.

  119. christine (3 comments.) says:

    I employ a lot of images and embeds on my site. The Visual Mangler is a nightmare to use and I switch it off immediately upon installation.

    Isn’t it terribly ironic that a “visual” application ends up treating the images you want post like crap? Hahaha!

  120. gestroud says:

    grr… I hate the basic editor. My HTML-coding days are long gone. That said, the visual editor still has some issues that I hope will be sorted out one day. :-)

  121. Red (1 comments.) says:

    its better to use code….visual ed is for the ones on the go

  122. Joel "Jaykul" Bennett (1 comments.) says:

    Well, I suppose it goes without question that I don’t use the visual editor (seeing as I’m the guy that keeps updating TextileWrapper so it keeps working), but I never really gave it a shot.

    I like the fact that I can write my posts anywhere (like in Notepad, or in a text editor on my Palm) and post them later … and I like the fact that I control the output and yet I can still show people the post outside my blog — that is, I can run the un-converted textile by people.

    My 2¢: although I think the world needs a good visual editor to enable no-technical blogging I don’t hold out much hope for a great one in HTML+Javascript considering how imperfect WYSIWYG editors are even in projects like FrontPage, NVU, and Windows Live Writer (which I usually recommend over the built in rich editor)

  123. dan (1 comments.) says:

    No I don’t, I much prefer the code view, some of the things we do require the code view (embed amazon ads). Any chance of working out a way to turn it off? Please? :-)

  124. Corbin H. Links (1 comments.) says:

    Hello Jim:

    My answer would be that we use both – but approximately 75% basic. Our current posting method involves using Windows Live Writer to post a draft, then using either visual editor (if the translation was clean,) or the basic editor if the code was munged and there are a lot of corrections to do. Our posts tend to be several pages in length and include tables and graphics, so the pure basic editor doesn’t cut it for anything other than tuning.

    For those interested in a hybrid approach, we have found that WordPress 2.2 when combined with the latest Live Writer and its ability to preview locally with the full WordPress theme works pretty well for larger posts — including tables.

    On a side note, many thanks to you and the WordPress team for all your fine work! We rely heavily on WordPress in our business, and appreciate all the updates and great features you bring to the user community.

    Best regards,

    Corbin H. Links, President
    Links Business Group LLC

  125. Robby (1 comments.) says:

    I’m the web editor (not designer) as a profession so yeah I COMPLETELY see the need some people might have for editing the direct code to their blogs…

    However, my blog is a personal one for myself and my family and it seems to me the only strength in a blog is for ease of use. My family doesn’t do web coding and although I could produce a family website that has the frills and brilliance of a full website, updating it would require either creating flash wordpad templates or editing the code directly, and it seems to me its much easier to just use the visual editor, for myself, and for my wife because in the end, you’re just writing text, not designing the latest/coolest website.

    It works for our needs and its easier than dipping into code.

  126. n-blue (9 comments.) says:

    More to use basic for full control and code the things by hand. WYSIWYG broke lot of things. Btw, I also use WIndows Live Writer for comfortable and web browser independence.

  127. Oliver (1 comments.) says:

    For me personally I’ll use the visual editor sometimes, and sometimes I won’t. I have set wordpress up for a couple of family members, and I know they probably wouldn’t be able to post anything without the visual editor.

  128. Shahzad khan (1 comments.) says:

    I actually prefer Windows Live Writer, and thats how I blog !


  129. ben (5 comments.) says:

    I started giving it another chance when 2.2 came out. I don’t mind it, but I do think the older method is probably the preferable one. It’s not a “hardcore” issue with me, I just like the performance of the plain text editor better.

  130. OmegaMan (1 comments.) says:

    God no…I am a .Net developer who posts code samples. The visual editor strips tags for some bizarre reason and between wordpress and the editor don’t seem to like the \ escape character. I have to double them to get them to show. I won’t go into the wonky so called smart quote issue… I have been using Windows Live Writer to compose and publish to my blog. I also use a code snippet addin to the writer to post the code samples. I have both links on my blog’s blog roll for those that are interested.

  131. Mike Bergman (1 comments.) says:

    I use both, and very aggressively. (Anyone who has happened to see my blog will recognize I’m not very typical; my posts are very long, with many links and references, embedded tables and many images.)

    I took on updating and distributing the Advanced TinyMCE plug-in because I wanted some of those complicated image and table management features.

    That being said, I tend to draft all of my pieces in Nvu XHTML initially (it has its own problems, but I’ve come to learn its quirks). I also will almost always use straight HTML code view for final changes and adjustments while in WP.

    The real problem for complicated stuff is the poor state of rich text editors for HTML, especially regarding div stuff. And, it will only get worse with more class information due to RDFa, microformats, etc.

    But, hey, I also remember many hand edits of WordPerfect codes; boy, those were the days before Word screwed up everything!

  132. Viper007Bond (91 comments.) says:

    Wouldn’t even dream of it. I know better than a script does when it comes to HTML.

    One of the very first tasks I always perform on every new WordPress installation I do is to go into my user profile and turn off the visual WYSIWYG editor.

    Or even better, delete the /wp-includes/js/tinymce/ folder from your PC before you even upload it to your site. WordPress will fail gracefully if TinyMCE isn’t installed.

  133. kukukuan (1 comments.) says:

    I also remove “autop” filter.

  134. Eggo (1 comments.) says:

    I can’t stand the visual, it’s a lot easier to get things right when I’m controlling purely with code.

  135. Azmeen (14 comments.) says:

    Basic editor for me. But I accept the fact that the visual editors will be much more useful for those who don’t know (or don’t care about learning) XHTML.

  136. BoltClock (24 comments.) says:

    The visual editor wastes about 30 seconds of my time trying to get itself to load right before I’m able to click the Code tab. And sometimes my post HTML gets messed up by it. The uppercase attribute bug is still present for Opera 9.

  137. redwall_hp (40 comments.) says:

    I’m more than proficient at XHTML (I’ve been doing it for 5+ years, and I don’t *need* the visual editor). However, as a writer it makes things a lot quicker for me, despite some irritations. When I’m putting together lists, for example, it’s a lot faster to use the visual mode.

  138. James (1 comments.) says:

    I turn off the visual rich text editor as well for the same reasons cited in the post. I also use Alex King’s WP Unformatted to further disable auto formatting when I post code snippets.

    It would be really nice if turning off the rich text editor turned off ALL automatic formatting. It’s really aggravating when WP converts my intentional div in to a paragraph.

  139. Jason King (1 comments.) says:

    I prefer to use the code editor but my clients are mostly staff and volunteers working for small charities and they aren’t all that web-savvy. They need the visual editor: they want to use something that looks like email or Word, with options they instantly recognise.

    My #1 wish would be for a button in the visual editor to select normal paragraphs, headings and subheadings (p, H1, H2, H3 etc). Because one doesn’t exist my clients tend to use the Bold button instead and this spoils the semantic layout.

    One problem that often crops up is when clients copy from Word or another website and paste into the editor, bringing the original’s formatting with it. I’d like to see an option to strips all tags from pasted text.

  140. Kristoffer (2 comments.) says:

    I almost always use the WYSIWYG editor. There are times when I prefer the code editor, such as when I need some custom XHTML in my post.

    But generally I use the visual editor.

  141. Kirk M (67 comments.) says:

    I use both in accordance with my needs at the time but more to the point, I use a local blog editor (Windows Live Writer, newest version-uses XHTML finally) for my primary blog writing. Then I use both versions of the WP editor to add tags and any other small changes I need although I don’t use the rich text editor for any serious writing.

    With that said, I believe that all of us “more experienced” bloggers who have been at it for the last 3-5 years need to understand that the future WP bloggers who decide to “do-it-themselves” will begin an exodus away from hand coding and more to the convenience of having the editor do it for you whether it is WP’s TinyMCE or one of the popular local blog writers. Personally, I’m happy to use both. It’s finally coming down to a matter of convenience.

  142. Ken McGuire (1 comments.) says:

    Formatting issues, paragraph issues – bleugh. Like yourself, the first thing I’ll do is disable the visual editor and when setting up blogs for anyone, unless they’re really stuck, I’ll do exactly the same.

  143. Matt says:

    I use WYSIWYG Pro ( Makes previewing a breeze and works well with all plugins I’ve tried. Plus I can use it on other sites I manage, which is a big plus.

  144. Matt says:

    Oh – and WYSIWYG Pro also has tabs at the bottom which allows me to go back and forth very easily and quickly between the Visual Editor and the actual HTML editor.

  145. tycho garren (1 comments.) says:

    I use plain text with markdown extra… It’s the way to do these things :)

  146. Cavalary (3 comments.) says:

    Certainly not, want to have control over all the code myself so I hate it.

  147. Patches and Hacks (1 comments.) says:

    I have the visual editor as default but I have to go into code editor a lot of times. Anyway I think most non technical bloggers would want the visual editor enabled by default.

  148. Pietro (1 comments.) says:

    No, I use just the code version of the editor.

  149. Chrystalline (5 comments.) says:

    I’ve found that if I type in the visual editor, I end up with bizarre, extra-long lines that stretch my page width. If I type my posts in Notepad and copy/paste (actually, I’ve been doing that since 2003, when I first started blogging with LJ – too many lost posts while in the middle of typing), the visual editor will preserve my paragraph breaks, but it won’t handle my html (links and bold/italics). If I paste directly to the code editor, it loses my line and paragraph breaks and gives me fits when I try to put them back. I haven’t found a solution I really like yet, but I’ve been pasting the text into the visual editor and switching to code to add the html.

  150. Charles Heineke (1 comments.) says:

    I use BlogJet 2.0 (, a WYSIWYG editor for WordPress. It gives me the speed and ease of WYSIWYG but also allows me to edit the html code if I need to. I don’t waste my time doing coding when I can use the far faster WYSIWYG mode for most of my work. Your choice, of course.

  151. Dave Starr --- ROI Guy (4 comments.) says:

    using -either_ the Code or Visual WordPress built-in editor formats is sort of like those goofy little “doughnut’ spare tires car maker’s “stiff” owners with … or like walking from Portland Maine to Portland Oregon … you can do it, but you have to be a little insane to try it.

    I’m surprised that so many “pro” bloggers still use it … I guess it’s a case of what they learned first they stick with … but your blogging productivity would be so, so improved with an intelligent tool like Windows Live Writer that you would be amazed. Windows Live Writer has a better “code” editing page that WP’s code editing and the rest of the features are infinitely better too … and, like WP, it’s totally free.

  152. Vivek Jishtu (1 comments.) says:

    No visual editor only code mode for me

  153. Tobbe (1 comments.) says:

    Yeah, I always disable the wysiwyg editor the first thing I do too.

  154. Deano (1 comments.) says:

    I’m a coder and can write the HTML manually but always use the visual editor. When I’m blogging I’m usually trying to get a opinion piece across so I want it to be as intuitive as possible. In the same way I couldn’t go back to a non WYSIWYG word processor (like the good ol’ days :o ).
    I only use the code view when I want to my blog piece to have some formatting that I can’t do from the visual editor.

  155. Max Pagels (1 comments.) says:

    I personally don’t use the WYSIWYG editor in WordPress because it tends to apply HTML tags in the wrong order and/or unnecessarily.

  156. salamonka (1 comments.) says:

    I use Dean’s FCKEditor For WordPress, it works very well

  157. antyki (1 comments.) says:

    I use plain text with markdown extra too,

  158. Beaufortonian (1 comments.) says:

    I use visual editor because I have 14 authors that contribute to the blog. If they were faced with having to code they would be intimidated and gone. As much as the intricaies of coding are interesting, the closer a blog post format can look like a word processor the better, at least for my potential authors whom I encourage to partcipate.

  159. Avrila (8 comments.) says:

    I use the WYSIWYG editor and I’d describe myself as understanding HTML code tolerably well (got started at about 13 on a Geocities free site back when they only had text editors; my first introduction to using HTML for more than sizes and colors was “huh, there aren’t linebreaks between my paragraphs”, and when I found EditPlus I thought it couldn’t get any better than that…ah, those were the days). I do switch to code view if I’m doing something that WYSIWYG breaks, or if I’ve done a lot of adjustments on a post and I want to make sure the code’s still clean. But for general posts, it’s fine.

  160. dzver (2 comments.) says:

    I don’t even know how to use it, WYSWYG seems so useless if you know basics of HTML and CSS.

  161. Mrs. DSN (1 comments.) says:

    I started to learn HTML and CSS because the visual editor frustrated me. Now I use the basic editor.

  162. Marisa (5 comments.) says:

    I’ve never used the visual editor. But then, I’ve never used a WYSIWYG html editor ever. I’ve always preferred to hand code so I could have better control. Haven’t used anything like TextileWrapper, either but I might look into that.

  163. tom (3 comments.) says:

    I used to use the code editor all the time, because the WYSIWYG editor wasn’t WYSIWYG and if I did use it, I would have to switch over to the code view anyway to set classes or inline styles, etc.
    Now I use the WYSIWYG editor all the time, using the TinyMCE table, style and xhtml plugins (why they aren’t shipped with the WordPress is beyond me).
    Warning: Shameless plug. I also use the Real WYSIWYG Plugin which makes the editing window look like the post. Tres cool, even if I do say so myself. The fact that Real WYSIWYG is even possible, shows how much TinyMCE rocks.

  164. Nathan (1 comments.) says:

    I don’t use the visual editor for the same reasons.

  165. weefselkweekje (1 comments.) says:

    Basic editor all the way. In fact I turned off the visual editor for all my guest editors as well, because it turned out they were having all sorts of trouble with it and ended up messing up my site’s layout.

  166. Anand (1 comments.) says:

    For myself I always turn the WYSIWYG editor off because it messed up my code. For my clients I always turn the WYSIWYG editor on.

  167. Dave (1 comments.) says:

    Aye, I use the basic editor too. The WYSIWYG editor tends to produce sloppy-looking code. I like to keep it strict.

    It’s good for newbs though. People who don’t want to dabble with HTML. But it can encourage sloppiness and laziness. I also disabled automatically correcting XHTML too. Some plug-ins don’t like that either.

  168. Shahab (8 comments.) says:

    Its crap .. I usually use Post2Blog or WBloggar ..

  169. Dennis D (1 comments.) says:

    I tried using the visual editor, but I quickly abandoned it because it really didn’t seem to work right. It seemed to produce unpredictable results — might be because I’m on a Mac or because of the browser, I don’t know…

    I use the Markdown plug-in and disabled the visual editor. Using Markdown allows me to write most things without too much effort (don’t have to worry about paragraph tags, etc.) but I can always drop into HTML when necessary.

    I do wish the visual editor had been more satisfactory, because the WordPress blog I implemented was actually for my stepdaughter who knows no HTML and I think the visual editor would be useful to her. But, I’m more confident in the output generated by the Markdown plugin.

    One other thing: my wife is using Movable Type for a blog and I noticed their editor had several setting available in a pulldown menu above the editor box. They had something akin to the WordPress visual editor, I think, and also a plain HTML option, but in addition Textile and Markdown were available as options. I think it would be a great idea for WordPress to make those choices explicitly available in this way.

  170. Catsudon (2 comments.) says:

    Nope. This is probably the only WP feature I absolutely have no use for.

  171. Danny S. (1 comments.) says:

    I usually start with the visual editor because it’s easier to see my content without the code. Then I switch to code view to fine tune everything…and fix what the visual editor did wrong…those extra (/p) tags are a pain. I love having the option of Visual and Code tabs at the top of the new editor.

  172. Adam Kayce : Monk At Work (3 comments.) says:

    I started trying all the textile/ecto/qumara options, and found that using the built-in editor was easiest. I also use the Image Manager and ST Visualize plugins, but I’m going to check out the others mentioned here…

  173. Milorad says:

    Linux vs Windows… Britney Spears vs Maroon 5… they each suck and they each have their place. Posts like this are just about people wanting to express how cool they are because they can write some markup.

    In reality, if you were a “professional” blogger, you’d be more concerned with words than with markup anyway. How often do you really need post-specific markup? – an abundance of specific markup which can be screwed up by the WYSIWYG editor is really more of a reflection on your posting than it is on the usability of the editor.

    I’m also inclined to suggest that “professional” writers are more likely to have experience with word processors than with hand-coding HTML, so I believe your use of the term is somewhat misleading unless you’re referring to profesional bloggers as being webmasters, not writiers. Certainly the former is more common, but the latter would be more accurate.

  174. Charity (4 comments.) says:

    I prefer the visual editor, but as of late, it’s been wreaking havoc with URLs I’ve linked to, so I started using the code only editor. I don’t have any formatting plugins that I use, I just code my formats in by hand if I need to. LOL

  175. Stephen Rider (10 comments.) says:

    I use the code editor, but on rare occasions want the visual. Personally I would LOVE it if I could set it so that I was using the two-tabbed editor, but it defaulted to the CODE tab.

    As it is, I generally leave the visual editor turned off in preferences.

  176. Stephen Rider (10 comments.) says:

    Forgot… I use the AddQuicktag plugin, which is great for adding simple buttons to the toolbar in the code editor.

  177. Andrew James (1 comments.) says:

    Count me in for the CODE ONLY side. I hate that editor. It screws up what I want the page to look like every time.

  178. Diwaker (1 comments.) says:

    No visual editor for me either. I use (my own!) plugin WP-Dokuwiki ( which lets me write my posts in Dokuwiki syntax.

  179. Alex (1 comments.) says:

    I can’t stand the visual editor. It just feels so… restrictive. Basic (which it actually isn’t) editor all the way. :)

  180. tabrez (8 comments.) says:

    I use the basic text editor because WYSIWYG generates very badly formatted HTML and it then becomes a pain to edit the HTML directly.

    Even the basic HTML editor doesn’t give full access to raw HTML(‘s and ‘s are automatically added) which kind of annoys sometimes.

    I use IG syntax highlighter plugin to syntax colour the programming code.

  181. Sam (1 comments.) says:

    I don’t use the WYSIWYG Editor (and have to switch it off altogether) because it simply breaks the code very often (for instance when including youtube HTML code snippets)…

  182. adam (1 comments.) says:

    Yeah, I never use the visual editor. It’s good for people who don’t know basic html though. I’m glad it’s installed so n00bs don’t keep pestering me.

  183. Daniel J. Summers (1 comments.) says:

    I usually use the visual editor (TinyMCE) on my personal blogs – I occasionally switch to “Code” view to put classes on a few tags, or insert an HTML entity. On my tech blog (linked off my name below), I pretty much use the basic editor. Of course, since I post code there quite a bit, I’m sure that’s normal. I’ve even had to go into that one and tell WordPress not to try to correct invalid nested XHTML. (I’ve also integrated TinyMCE into another web site I’ve developed – the users love it, because they can make it look “pretty”, and it displays back “pretty” as well!)

    I use wp-syntax and Code Markup to highlight code on my tech blog.

  184. Sudar (4 comments.) says:

    First I use the Visual Editor for formatting and then later view the HTML generated to make small changes. I enable the View HTML button using this trick (

  185. bubazoo (1 comments.) says:

    I use both also, with the default being the visual. The only reason being, I just don’t care to take the time to put in a bunch of formatting just to make a post. I like to “quickly” post, not sit there and edit and reedit and reedit, you might as well design a whole page if your going to do all that.

    I just think the visual editor needs some work, like more options to be able to block text on one side, a picture on the other. doing that is not always an easy task while still keeping xhtml formatting intact, especially when plugin writers break xhtml formatting as it is. I mean, normally I just write stuff in and thats it. the only time I ever have to format is when adding a picture alongside text, only because you gotta format it so the picture doesn’t display too big and the text will align next to a photo, thats about the only time I ever format anyway, so if they can fix that in the visual editor I’d be happy.

  186. Ron K Jeffries (1 comments.) says:

    I can not stand the WordPress visual editor. Guess I’ll try Textile Wrapper.

  187. Tim (1 comments.) says:

    Mostly the basic editor, it’s easier for dealing with photos etc. but I do have a flip over to the Visual when I can’t be arsed to type in a load of code. I think they are both good but the basic is preferable.

  188. Dirk (5 comments.) says:

    Nope. It’s kinda good, but i like to do my own code.

  189. Jabapyth (1 comments.) says:

    I never use the WYSIWYG: it doesn’t give me enough control over my posts.

  190. sisifodichoso (1 comments.) says:

    I never use the visual editor. I always use etiquetags a bigger version of quicktags, with more tags and nicer buttons ;-)

  191. John (1 comments.) says:

    I have used WordPress as a WYSIWYG for a while. I have been working with the text editor disabled so I only edit the HTML. On another site I was working on recently, I set up WordPress as a CMS. The problem is someone else who doesn’t know HTML needs to edit the site. If they enable the WYSIWYG editor, it really messes up my HTML code. I would be fine if I could get it to float the images properly around the text but after saving and editing the page, it strips out various or tags which messes everything up. Are there any plugins to remedy this?

  192. Matt Dawson (1 comments.) says:

    I’m using Windows Live Writer, but am finding the xHTML it generates to be flawed and requires repair in the WordPress text editor afterwards. e.g. leaving paragraph close tags where no opening tag exists. I’ve followed your advice and have disabled the WordPress visual editor (which I didn’t use and kept on converting div tags to paragraph tags – annoying) and will see if that makes my posting experience any easier.

  193. luggage says:

    I’m a fairly basic guy and so I stick to the visual editor. Why not? I don’t really add much fanciness to my posts because I don’t need to. Simple is better. The WYSIWG editor is fine for most normal people, and I’m one of them. Even though I can do some HTML, I don’t ever feel as if I really need to. Besides, pushing buttons is more fun! I think, anyway. Although they can improve it, the WordPress WYSIWG editor is certainly one of the better ones around by a long shot. I’ve had to endure some real monsters before…

  194. Lars Tong Strömberg (14 comments.) says:

    I use them both, but mostly the visual editor.

  195. Norma (1 comments.) says:

    I primarily use the html editor, but occasionally use the visual editor. Mostly, I find the visual editor annoying because I’ll forget I’m using it, and type something in anchor text, only to find that it didn’t work properly because of the visual editor.


  196. Mike Jacoubowsky (1 comments.) says:

    I use both visual and code-based editors. I’ll often do a first run using the visual editor, and then clean it up using the code editor. The code editor is not without its issues though; often it won’t properly place photos (for example, I’ll try to insert a photo between 2nd & 3rd paragraphs, but it will often place it at the top).

    I’m new to wordpress, so I’m probably overlooking the obvious.

  197. Jon Donley (2 comments.) says:

    Absolutely us it, for one simple reason – I make a good living building websites for real-world companies, exclusively WordPress CMS. One of my selling points is that when I hand them the keys, they can update their sites themselves . . . AS EASILY AS USING WORD. This is a crucial deal-maker.

    In development, course, I work in source-code, but always with an eye out for compatibility with the client interface. And one can’t very well have operational awareness of that with the WYSIWYG switched off.

    I do have pals who think I’m betraying the dev community by “enabling” clients, instead of following the “maintain the mystery and keep prices astronomical” mode. I find, however that enabling customers to do it themselves tends to open their eyes to the more-complex things that DO need expert coding and customization . . . and that’s the basis for continuing business.

    I do tend to hand people Dean’s Fcked Editor instead of the built-in version, however. And I add plugins to reign in WP’s tendency to be a Code Nanny.

  198. pinbalwyz (1 comments.) says:

    I *DO* use the visual editor. I feel the WordPress developers have done a pretty fair (not to say ‘perfect’) job of it. The visual editor injects formatting errors (especially when involving included images) but I’ve discovered some easy workarounds, e.g. the ubiquitous ‘.’ to help manage text alignment adjacent to an image.

    Like others, I sometimes must use the ‘code’ tab for controlling html features directly. It’s very nice to have BOTH tabs (visual & html code) available…a bit like Dreamweaver does. Blogspot doesn’t do any better at formatting in visual mode editing than WordPress…worse, actually. Overall, I’m quite pleased with the formatting options available in WordPress. I do, however, wish font size was an available feature in visual edits.

  199. Nicholas Teo@Feng Shui since 1988 (37 comments.) says:

    I use both editor, I am not good at HTML and need to use the visual one for writing and the html one for touch up.


  1. […] Weblog Tools Collection asks the question “do we use the WordPress visual editor?” […]

  2. […] Stitzel does not use the WordPress visual editor. Me neither. And looking by the response in the comments, it seems a lot many do not use it. I use […]

  3. […] posts have recently come up in my feed reader, from Jim Stitzel and Abhijit Nagouda, confirming something I have thought all along- people hate the WordPress […]

  4. […] ???????? ?Weblog Tools Collection???????WordPress?????? – ???? […]

  5. […] please see this post, thanks. (I hadn’t used the visual editor in, oh, years. My mother was asking about the fact that it “evilizes” the code (hee!) and so I thought I’d fiddle with it for a minute or three) […]

  6. […] WYSIWYG functionality: volstrekt overbodig. Weblog Tools Collection heeft dit vorige week al voldoende […]

  7. […] ?Weblog Tools Collection???????WordPress?????? – ????? […]

  8. […] to this is the question: ‘WordPress Visual Editor – Do you Use It?‘ I do not, switching to the basic editor wherever […]

  9. […] ??????? ???????? ????? ??? ?? ??????? ?? ?? ?? ?????. Jim Stitzel ?? TextileWrapper ??????? ?????? ? ????? ??? ????????? […]

  10. […] ??????? ???????? ????? ??? ?? ??????? ?? ?? ?? ?????. Jim Stitzel ?? TextileWrapper ??????? ?????? ? ????? ??? ????????? […]

  11. […] off the visual editor in WordPress:  (via Weblog Tools Collection and More than scratch the surface)  In WordPress’s admin interface, switch to the users […]

Obviously Powered by WordPress. © 2003-2013

page counter