I searched for a while how to prevent the WP editor from changing my code, how to desactivate wpautop or wptexturize, how to remove the filters, etc, until I came to this post and finally “broke the code” for me. Read on.

So I found and tried WP-allow-tags because I just could not put in a simple script to verify a form in a post. But the plugin did not work for me, so I tried to modify it and create a new wpautop function.

WP then just disabled the plugin as I created a fatal error, but at the same time it gave me the line of code where there was a conflict (I could have found it by searching through the installation of course).

So I went to the wp-includes/formatting.php file and simply commented both function wpautop and wptexturize just leaving the proper return at the end. See below.

function wpautop($pee, $br = 1) {
/*
… lines of code …
*/
return $pee;
}

Same for wptexturize:

function wptexturize($text) {
/*
… lines of code …
return $output;
*/
return $text;
}

That for sure worked for me! No more changing of my HTML or other code in posts when saving. And I did not notice any negative effects so far.

I hope it does work for you too if you need it that way.

Best,
John

After hours and hours of running this around and around, I tracked down a problem that was driving me insane. The config file posted has a redirect to add the www to every incoming request. My existing blog database, however, has the blog home URL listed without the http://www. When I got everything up and running, every incoming request would head into an infinite redirect loop between domain.com and http://www.domain.com.

Thank you for dropping this all together in one place. Very useful.

I’ve posted the whole conf to my blog - http://www.motionstandingstill.com, but all I really did was add the following location section and made sure that the ‘root’ clause specified before this.

location ~* i.+\.(css|js|jpg|jpeg|gif|png)$
{
expires 7d;
}

Gleb