dbm44

Just installed the latest plugin update from WordPress site, Version 5.163.1 and error message is still there when sending from contact form. Is the fix supposed to be in this version?

Thanks, having installed the fix on one website so far, it does appear to have solved the issue

Hi,

Is there any update? The problem is still occurring and is filling up the error logs

I can confirm that the latest version of the plugin has resolved this

@timersys

I just sent you a message direct from the contact form. Message was:-

This is a test message using Simple Basic Contact Form. First line.

Second line with space in the middle.
Third line without space.

Fourth line with space in the middle.

When I receive the message it shows as:-

This is a test message using Simple Basic Contact Form. First line. Second line with space in the middle. Third line without space. Fourth line with space in the middle.

Do you get the same?

The simple basic contact form also uses \n to signal line breaks.

It looks like whatever the change in 1.3.1.1 was that added formatting and sanitization if the email is not HTML, is responsible for stripping the line breaks

Hi @timersys,

No sorry, unfortunately I am not allowed to permit third party access to these servers.

What changes were made between 1.3.1 and 1.3.1.1 that would cause the caching plugins even when not active on the page to strip the line breaks?

Hi @timersys

Thanks again. OK so I have had a couple of hours to test various issues.

I have tested a couple of sites without any other plugins except for email templates and the contact form, and on their own it works OK.

I found that as soon as a caching plugin is activated, then the line breaks are removed from the contact form using email templates.

I have tried excluding the contact form page from the cache but this makes no difference, the line breaks are always removed.

The WP Rocket plugin and WP Fastest Cache both remove the line breaks from the contact form with email templates as soon as they are active.

This contact form issue only happens with 1.3.1.1. Version 1.3.1 with a caching plugin works OK.

The caching plugin has no effect on UpdraftPlus emails, these simply do not format in version 1.3.1.1 with and without the caching plugin active.

Can you now reproduce this issue with a caching plugin installed?

@timersys

Thanks for trying to fix this

Yes I have the latest version of the plugin, 1.3.1.1 and it is stripping the line breaks with simple basic contact form on multiple web sites on 2 different hosts.

I am also using the Mailgun plugin, but I have tested with and without this plugin and it makes no difference, the line breaks are removed.

I have just removed 1.3.1.1 and reinstalled 1.3.1 and it works OK, the line breaks are there in both simple basic contact form and UpdraftPlus.

So whatever is stripping the line breaks, was introduced with the 1.3.1.1 changes

It is not just UpDraftPlus that is affected though.

I have just noticed that emails on another site using the Simple Basic Contact Form plugin are also having their new lines stripped.

Again, this was not happening before the 1.3.1 update

@timersys

Yes I am using the premium version of UpDraftPlus. This sends a much more detailed email after the backup compared to the free version

Hi,

Here are the screenshots of the first couple of lines of the email, just below the header which shows OK. The footer also shows OK, just the content which does not

Old plugin which looks OK

New plugin version which strips all line breaks from the content

@alexandergull @safronik

Thanks guys. Just tested the latest version of plugin, Version 5.116.3 and the warning messages are now gone.

You can now mark this issues as resolved.

Thanks again for getting this sorted

And just noticed this topic has been marked as resolved.

IT IS NOT RESOLVED

Agreed, not fixed (by 5.116.2)

Multiple people have had this issue and it is still not fixed. I suspect many more people are also having this problem, they just don’t know it, because they have not tested this plugin with WP DEBUG on.

Asking people to create private tickets is not solving the problem, just hiding it.

Cleantalk as a (paid) service works well, but resolution of this issue has been very poor. A great deal of time has been spent testing supposed fixes that simply do not work