Support

February 3, 2014 at 7:46 am

Hi Paul,

I used the code you posted and did run into issues, however these were not due to the shortcodes.

The reason the format is breaking is due to how WordPress handles the code once saved and/or when switching between Visual & Text mode.

With the code you posted the forum altered some small parts but after fixing the outcome was this http://d.pr/i/yLVU

This was due to the whitespace added to breakup the wording (when switching from Text to Visual then back again you’ll find any P tags are no longer there).

Removing all white-space resulted in the format (table) correctly outputting this: http://d.pr/i/wr2z

Then to space the wording use P tags rather than whitespace and BR tags. So you end up with this http://d.pr/f/FKr3

Output http://d.pr/i/JtJb

Unfortunately, if you switch between Visual and Text mode within WP those P tags will be once again lost, breaking the layout.

The best advice I can offer currently is to work locally on the templates, copy and paste them into the editor in Text mode, then save and test.

If you ever switch to Visual mode on the editor itself, remember not to save the email after doing so.

Hope that helps 🙂

February 5, 2014 at 12:04 pm

I did try it and it worked for me. (no tags added for line breaks). Does the code that you’re pasting in from Dreamweaver contain line breaks?

It may help to rule out if there is a theme function or another plugin that’s altering the wpautop filter (usually they’re shortcode functions in themes or plugins that are the culprit). A quick way to test this is by temporarily deactivating all plugins and switch to one of the twenty* themes, or try it out on a vanilla WP install.

February 6, 2014 at 7:49 am

Hi Paul,

I have one question about what you reported here:

> If I create a new page and paste my HTML in there, I don’t get the extra tags added.

Is that with the wpautop filter disabled or no? Also, are you posting this in while in the HTML view or the visual editor mode?

One more thing that you can do that will help us help you: Can you post the contents of your html formatted email into a pastebin and link to it here?

Thanks.

February 6, 2014 at 9:49 am

Hi Paul,

Thanks for posting the html code, and it helps me see what’s going on. It turns out that there are line breaks within the html tags in the html that you posted, and the WordPress wpautop function is adding more br tags for each of them. If you look at the source of the posts you tried testing on the front end (not within the editor), you’ll see br tags for each of the line breaks in the source. At least that’s what I’m seeing, here’s a screenshot of the source of a post that has the html pasted in.

So it turns out that this isn’t an Event Espresso function that’s adding the new lines, it’s a core WP function. The WP codex says that this is the default behavior:

Preserve line breaks. When set to true, any line breaks remaining after paragraph conversion are converted to HTML
. Line breaks within script and style sections are not affected.

http://codex.wordpress.org/Function_Reference/wpautop#Parameters

There are a couple ways to fix this:

1) If you can remove the new lines from the html that you’re copying from before pasting into a WP editor, that will fix the issue you’re seeing. Here’s a gist of the same html you sent, with most of the new lines removed:

https://gist.github.com/joshfeck/6f34b1897b205499eb4b

2) A simpler way would be to set the wpautop function so it doesn’t add the line breaks. If you look in /event-espresso/includes/functions/admin.php you’ll see this function on line 85:

function espresso_admin_format_content($content = '') {
	return wpautop(stripslashes_deep(html_entity_decode($content, ENT_QUOTES, "UTF-8")));
}

which you can change to:

function espresso_admin_format_content($content = '') {
	return wpautop(stripslashes_deep(html_entity_decode($content, ENT_QUOTES, "UTF-8")), $br=0);
}

What that will do is tell WordPress to not preserve the line breaks in the html.

What we can do in a future version of ee is add a filter there where the $br value is set so this can be changed without directly editing core files. But for now, making that small edit should get you going on your way.