Support

July 19, 2018 at 7:54 am

Hi Christophe,

How are you today?

Whenever there’s an awful lot of unnecessary <br> tags in the generated markup, those are actually added by a condition caused by the theme or another plugin.

For example, let’s say the template has this:

<div class="container">
<h3>Some heading text</h3>
<p>Some regular text in a paragraph. And so on</p>
<img src="site.com/imageurl.jpeg" />
<p>More text</p>
</div>

Nothing crazy there right? Here’s what can happen though, if a custom filter function is applied to the WordPress the_content() filter:

<div class="container">
<br>
<h3>Some heading text</h3>
<br>
<p><p>Some regular text in a paragraph. And so on</p></p>
<br>
<p><img src="site.com/imageurl.jpeg" /></p>
<br>
<p><p>More text</p></p>
<br>
</div>
<br>

What happened in this case was whenever there was a new line, the filter function added some extra tags. It was probably intended to be applied only to a specific shortcode on the site where it might make sense to add the tags, but other shortcodes end up getting the same treatment.

So you could try to find the theme function or plugin that’s adding the extra stuff or you’ll run into the same issue with your custom templates.

If you must alter the markup, you can do your own templates as replacements. Depending on how the template is loaded you’ll use one of two methods:

1) If the template is loaded with locate_template() you can put a copy of the template into the active WordPress child theme and your template will load instead.

2) If the template is loaded with display_template() you’ll use the
FHEE__EEH_Template__display_template__template_path filter hook to change the path to point to the location of your own template.

Please be aware that there is JavaScript that interacts with the markup so if you remove/add change class names and IDs that could break those parts of the functionality.