Comments on: Amazing hack for fixing the code changing habits of the WordPress editor

By: Andrew

Andrew — Thu, 13 Jan 2011 02:38:47 +0000

Try this 1 line of code out, it stops wordpress from automatically putting in p tags (might work for others to) simply put it above the_content(); function. Anyway here it is, should help stop wordpress from automatically messing up your code.

By: Modavate

Modavate — Thu, 18 Feb 2010 06:24:41 +0000

Thanks Ron!
The clear_both shortcode worked. I simply added a height to the style, so all I use is the [clear_both] with no DIVs. I also had to edit your apostrophes otherwise my site went blank.

By: Wordpress davon abhalten, automatisch Code zu ändern « Franz Neumeier's "Ceterum Censeo" Blog

Mon, 01 Feb 2010 08:27:24 +0000

[...] Rinaldi hat nun vor ein paar Tagen bei WPGarage in einem Kommentar eine Lösung präsentiert, die ich genial finde – einfach weil sie für meine Zwecke ohne [...]

By: ron

ron — Sun, 24 Jan 2010 03:35:24 +0000

I forget to mention that to use the shortcodes, they must be on a line by themselves. For example…
….. your markup and text here….

[clear_both]

…. More text here.

The thing to notice is the blank lines around the short code. This must also be done with the [div] shortcode. Without these blank links, you will get spurious
tags. Its weird. I guess the multiple blank lines create multiple sequential
tags, which then get stripped out all at once. I tell you if I wasn’t so vested in WP I’d find something else. Their overprotective practices are just screwy.

By: ron

ron — Sun, 24 Jan 2010 03:31:52 +0000

I have a solution to this problem. It took me all day to figure it out, and it is very hacky. I’m so pissed at WP for not having features to turn OFF their ‘autop’ function and allow html editing to be true html editing. Even if just for admin-status users, it would have saved ALL of us a bunch of time.
My solution is to use shortcodes. They are not stripped out, and they can be used to insert div tags after the stripping has taken place. Here is my code…

// The [clear_both] shortcode
function shortcode_clear_both() {
return ‘

’;
}
add_shortcode( ‘clear_both’, ‘shortcode_clear_both’ );

// The [div] shortcode
function shortcode_div( $atts, $content=null ) {
extract(shortcode_atts(array(
‘class’ => ”,
‘style’ => ”,
‘id’ => ”,
), $atts));
$ret = ‘ if (!empty($style)) $ret .= ‘ style=”‘.$style . ‘” ‘;
if (!empty($class)) $ret .= ‘ class=”‘.$class . ‘” ‘;
if (!empty($id)) $ret .= ‘ id=”‘.$id . ‘” ‘;
$ret .= ‘>’;
$ret .= $content . ‘’;
return $ret;
}
add_shortcode( ‘div’, ‘shortcode_div’ );

Hope this helps someone out there.

By: John

John — Tue, 09 Jun 2009 21:47:05 +0000

Yup – things like iframes and a

that let’s me reatart text properly under pictures are
still being stripped out – absolutely maddening – there MUST be a solution out there somewhere!

By: Maurice

Maurice — Fri, 05 Jun 2009 05:19:23 +0000

No, we still need a solution. WP 2.7.1 is STILL chewing up even basic HTML code and throwing it away. I will insert some IMG and tags and it will come back 3 saves later and throw them all away. Any solutions anyone?

By: Ryan

Ryan — Thu, 16 Apr 2009 10:45:12 +0000

@alan – AFAIK this hack no longer works because it is no longer needed. I don’t think DIV tags are converted to P tags in WordPress anymore.

By: Alan

Alan — Tue, 14 Apr 2009 14:54:55 +0000

This hack no longer works in wordpress 2.7.1.

Does anyone have a work around for that version?

By: Plugins and hacks for improving the WordPress TinyMCE editor | Wordpress Garage

Mon, 09 Feb 2009 15:02:45 +0000

[...] few days ago I wrote about a way to make the WordPress TinyMCE text editor stop stripping div tags. The original code that I wrote didn’t work, but I subsequently found a solution that I [...]