Title: tboerman's Replies | WordPress.org

---

# tboerman

  [  ](https://wordpress.org/support/users/tboerman/)

 *   [Profile](https://wordpress.org/support/users/tboerman/)
 *   [Topics Started](https://wordpress.org/support/users/tboerman/topics/)
 *   [Replies Created](https://wordpress.org/support/users/tboerman/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/tboerman/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/tboerman/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/tboerman/engagements/)
 *   [Favorites](https://wordpress.org/support/users/tboerman/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Leaving untouched in Visual Editor](https://wordpress.org/support/topic/leaving-untouched-in-visual-editor/)
 *  Thread Starter [tboerman](https://wordpress.org/support/users/tboerman/)
 * (@tboerman)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/leaving-untouched-in-visual-editor/#post-2728907)
 * Yeah, I guess it’s harder than it looks or it would have been fixed long ago.
   Even plugins such as [Preserve Code Formatting](http://coffee2code.com/archives/2005/03/29/plugin-preserve-code-formatting/)
   do not support using the visual editor. I will stick with the HTML editor for
   now, thanks for the help!
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Leaving untouched in Visual Editor](https://wordpress.org/support/topic/leaving-untouched-in-visual-editor/)
 *  Thread Starter [tboerman](https://wordpress.org/support/users/tboerman/)
 * (@tboerman)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/leaving-untouched-in-visual-editor/#post-2728900)
 * Yeah, I guess that’s the bottom line. Still, how hard could it be for the the
   editor to just leave things in `<pre>` tags completely untouched when switching
   back and forth?
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Leaving untouched in Visual Editor](https://wordpress.org/support/topic/leaving-untouched-in-visual-editor/)
 *  Thread Starter [tboerman](https://wordpress.org/support/users/tboerman/)
 * (@tboerman)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/leaving-untouched-in-visual-editor/#post-2728892)
 * Thanks. Unfortunately that plugin requires you to define code snippets in the
   plugin settings before you can use them. Is there really no way to edit code 
   in-line? 🙁
 * I can understand why so many people are raging at WordPress over this, its just
   stupid! The WordPress authors don’t have much love for people who want to blog
   about coding, that is for sure.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Leaving untouched in Visual Editor](https://wordpress.org/support/topic/leaving-untouched-in-visual-editor/)
 *  Thread Starter [tboerman](https://wordpress.org/support/users/tboerman/)
 * (@tboerman)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/leaving-untouched-in-visual-editor/#post-2728827)
 * I’m using the WP-Syntax plugin to do highlighting, but this requires the use 
   of `<pre>` tags. Hence the question.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Leaving untouched in Visual Editor](https://wordpress.org/support/topic/leaving-untouched-in-visual-editor/)
 *  Thread Starter [tboerman](https://wordpress.org/support/users/tboerman/)
 * (@tboerman)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/leaving-untouched-in-visual-editor/#post-2728823)
 * > Short answer: Nope.
   > Longer answer: It’s a known issue with the TinyMCE Editor. Mos (if not all)
   > of the markup entered via the HTML tab will be stripped out by the Visual Editor.
   > If you simply can’t restrict yourself to the HTML tab, then you need to look
   > around for a suitable WYSIWYG editor plugin.
 * Hey,
 * I’m aware that this is a notorious problem/feature in WordPress. Setting `valid_elements`
   to “*[*]” with the Advanced TinyMCE Config plugin seemed to improve things, but
   it is still far from fixed.
 * It would be great if there was a way to tell the editor to leave the `<pre>` 
   contents **completely** untouched. Hopefully someone can point me at a plugin
   that can do this (“Save my Pre” didn’t do the trick).

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