Remove unwanted BR linebreaks after Label tags

I had figured there was an autobr filter in WordPress, and was checking to see if there was any mention of it, when I discovered your post. Your filter worked for me with a slight modification.

$content = str_ireplace("</label><br />", "</label>", $content);

because the br tag was being placed after the closing label tag, rather than after the opening label tag.

Either way thanks for the post. I got the form to display properly again a slightly modified function.

I have a similar problem…

If I put a name anchor around a heading, WP adds P and BR tags to the whole mess for some reason.

For example, if I write the following:

<a name="some-name"><h2>Some Heading</h2></a>

WordPress (when using the TwentyTen theme, at least) outputs the following HTML:

<p><a name="some-name"><br/>
<h2>Some Heading</h2>
<p></a><br/>

This results in horrible gaps around my headings.

Anyways, I think this thread may offer me a band-aid for this problem. Thanks.

If I enter the following:

<a name="css-style-blocks"></a>
<h2>CSS Style Blocks</h2>

WordPress outputs…

<p><a name="css-style-blocks"></a></p>
<h2>CSS Style Blocks</h2>

…which doesn’t have the gap issue, but I’d rather have the anchor surrounding my heading.

Maybe this will provide a workaround for this issue. Thanks.

Actually I discovered I do not need to worry about matching the heading element itself. Also, my previous solution was not catching all cases. Below is slightly better code (it can be improved!)…which also may not catch all possible cases, but seems (so far) to catch the ones I need it to…

// Whenever I surround a heading tag with a name anchor
// WP adds unwanted P and BR tags, this function strips them out
add_filter('the_content', 'remove_bad_pbr_tags');
function remove_bad_pbr_tags($content) {

        // CORRECT OPENING ANCHOR TAG...

        // find any opening name anchor tags preceded by a <p> and followed by a <br /> and
        // replace them with just the name anchor itself
	$content = preg_replace('/<p><a name=[\"\'](.*)[\"\']><br\s*\/>\s*/', '<a name="$1">', $content);

        // CORRECT CLOSING ANCHOR TAG...

        // the closing anchor tag is followed by 2 or more new-lines in the WP editor...
        $content = preg_replace('/\s*<p><\/a><\/p>/', '</a>', $content);

        // the closing anchor tag is followed by a single new-line in the WP editor...
        $content = preg_replace('/\s*<p><\/a><br\s*\/>/', "</a>\n<p>", $content); // the double quotes are necessary in the second parameter for the \n to be considered a newline

        // the closing anchor tag is immediately followed by content (i.e., no new-lines) in the WP editor...
        $content = preg_replace('/\s*<p><\/a>[^<]/', "</a>\n<p>", $content); // the double quotes are necessary in the second parameter for the \n to be considered a newline
	return $content;
}

Very helpful tip, thank you everyone.

My version of this filter worked when I accounted for an invisible new line character (\n):

//	Strip unwanted <br /> tags from forms
add_filter('the_content', 'remove_bad_br_tags');
function remove_bad_br_tags($content) {
	$content = str_ireplace("<br />\n<input", "<input", $content);
	return $content;
}

neddy49 … I’m not itsbarry, but you should be able to add it to either functions.php file. However, I believe the best practice would be to add it to the functions.php in your child theme.

Tom