tboerman
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Leaving untouched in Visual EditorYeah, I guess it’s harder than it looks or it would have been fixed long ago. Even plugins such as 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
In reply to: Leaving untouched in Visual EditorYeah, 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
In reply to: Leaving untouched in Visual EditorThanks. 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
In reply to: Leaving untouched in Visual EditorI’m using the WP-Syntax plugin to do highlighting, but this requires the use of
<pre>tags. Hence the question.Forum: Fixing WordPress
In reply to: Leaving untouched in Visual EditorShort 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_elementsto “*[*]” 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).