Okay so I might have found a workaround: building the notification email field by field, instead of using {all_fields}, appears to preserve line breaks. If that helps.
Hi @dwegowy,
While we had this issue in the past I tested the latest version and couldn’t replicate the problem anymore.
Can you tell me if you’re using latest release (1.15.2) or it was happening with some older release?
If you can still replicate this issue with the latest version we would like to investigate this further on our end.
In order to do this, could you go to Forminator > Forms and click on Gear icon next to your form to export it.
Upload the export file to any file sharing service like GDrive or Dropbox and share the download link here.
Cheers,
Predrag
Hi, I’m running Forminator 1.15.2 under WordPress 5.8 and it appears to do this, still, inserting that space character before the form field variable.
I tried creating a new form using Forminator’s ‘Contact’ template, then added the email form field to the reply-to field in Email Notifications, and the space is there. I exported this form for you:
https://www.dropbox.com/s/hbtpwzz1h81k93j/forminator-test-contact-form-export.txt?dl=0
Hi @dwegowy,
I’m afraid, I’m a bit lost with the issue you have raised. Just to be sure a text entered in the “text area” field appears in a single line, even after entering a new line, right?
I’m a bit confused regarding the reply-to field as they aren’t related to “Textarea”, so wanted to be clear if I’m missing out on anything.
However, I tested with your form and it worked out of the box without any issue:
Could you please check and advise if I’m missing out on anything? A screenshot would also be helpful.
Looking forward to your response.
Kind Regards,
Nithin
Indeed, the text area line breaks issue appears to have been fixed.
Forminator Version 1.15.2
Wordpress Version 5.8.1
N.B. I’m also using WP Mail SMTP Version 3.0.3 to control mail sending, on this site.
Hello @dwegowy !
Hope you’re having a good day!
I’ve tested this and can’t reproduce the issues you’ve mentioned:
– “inserting that space character before the form field variable”
– and no more issue with the new line characters being removed
Can you share some additional details on the issues you’re still having? A screenshot would be great.
Kind regards,
Pawel
OK yes it still appears to exhibit this behaviour. It could still cause trouble for some users if they don’t know to remove that space character.
Creating a new form, editing the Email Notifications > Advanced, choosing the form’s email field:
https://www.dropbox.com/s/yja659u2ksdqbap/1-add-field.jpg?dl=0
The field is inserted but there is a space character preceding it (highlighted), which seems to interfere with the reply-to header being included on form notification emails:
https://www.dropbox.com/s/dhd1rd8v3xtnb9k/2-space.jpg?dl=0
And I’m sorry these threads have become tangled. While the subject of this thread is the text area line breaks, these latter messages pertain to this thread:
https://wordpress.org/support/topic/forminator-reply-to-submitted-mail/
Hello @dwegowy !
Ah, now it’s clear 🙂
Okay, in this case, please continue the discussion about the space and please share the screenshots and the description in that other ticket so we can keep the threads related to one issue at a time – it will make it easier to find the tickets and also for us to solve them.
Kind regards,
Pawel
Hi, this issue (line breaks in form user text area not being preserved in notification email) seems to have returned in Forminator v1.15.7 (WordPress v5.8.2).
Hi @dwegowy
Sorry to hear it returned, I testes the most recent version and I was able to replicate the issue.
We are going to report to our developers and I hope we can fix it on an any upcoming update.
Best Regards
Patrick Freitas
Can confirm this is still occuring in .9 too
Hi @mrbleuu
I am afraid I tested in the .9 and it still happening.
Best Regards
Patrick Freitas
Hi @mrbleuu
I did a check and I see there is a fix coming for 1.15.11,
Best Regards
Patrick Freitas
Hi there,
I got the same issue, may I get a estimated release date for 1.15.11 or is there a temp solution for this issue? I have a client waiting for getting the problem resolved for a while already.
Thanks
