adding blank lines / lines between paragraphs in autoresponder email?

What is JotForm?

JotForm is a freeonline form builder which helps you create online forms without writing a single line of code.

At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.

We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.

Why do you not want to answer this thread?(Your answer will be sent to Jeanette and Aytekin)

robinowsley

Asked on May 24, 2011 at 07:41 PM

Is there a way to do this without going the HTML email route?

I just wanted to insert blank lines, otherwise known as old-fashioned "carriage returns" to autoresponse users of my form 2 paragraphs, instead of it all going in one massive chunk. But I don't really want to get into HTML emails, I'm really good with plaintext, it's a personal preference.

Your email sort of brought back the nostalgic days of the good old typewriter. Back to your question, do you mean you have tried using the Return key (or the Enter key of your keyboard) twice (or three times) and it still did not add the line breaks? That should work but please let us know if it doesn't do its job.

Thank you for using JotForm!

JOTFORM SUPPORT

JotForm Support

liyam

Answered on May 25, 2011 at 12:41 AM

Hello,

In addition to what Allan stated, in an HTML editor, if you want your content to go to a new line, just press shift + enter. This will enter to something similar to this:

1. information here2. information here3...

If you want to switch to plain text, it is quite unfortunate for now that it will not render new paragraph lines. Although simple new lines such as you want to accomplish can be done.

I will also forward a request to the development team and let them know about this issue.

Thanks and warm regards,

Liyam

robinowsley

Answered on May 25, 2011 at 12:17 PM

No, weirdly, I can add single line breaks, but not double. The text will go to the next line, but no double breaks, even though there are double breaks in what I entered into the form. They don't make it to the email. When the email arrives, it changes the double breaks back to single.

This would be a very good feature to add. It looks strange to have really long paragraphs, but I really prefer plain text emails over html.

JotForm Support

liyam

Answered on May 25, 2011 at 04:03 PM

I actually do believe that this is a bug rather than a lacking feature.

Let's wait for the developers to have them look into this and get this fixed.

Thanks,

-Liyam

mmatthews

Answered on July 26, 2011 at 11:54 AM

Has this issue been fixed? I'm trying to use HTML and text emails in the auto responder feature. The text version does not have a line break in the email when it is sent...it does have it on the preview screen in jotform. Please advise.

Thank you,

Melanie

robinowsley

Answered on July 26, 2011 at 12:19 PM

I just got an email someone updated this thread . . . but sadly, I guess the issue has still NOT been fixed.

Soooo . . . "having the developers look into something" doesn't typically mean it gets fixed within a couple of months? Or are they still looking at it?

In addition to mmathews now, I'd still be very interested in having this as a feature, that being, the ability to insert a double line break into an email in plain text rather than having to resort to HTML format JUST for that, if that matters to anyone? ??? Thanks.

JotForm Support

liyam

Answered on July 26, 2011 at 01:18 PM

Hello robinowsley and Melanie,

We apologize for this inconvenience.

I have increased the priority of the report ticket I submitted so that the Jotform developers will start working on it as soon as they can.

Thank you for your patience.

Warm regards,

Liyam

JotForm Support

NeilVicente

Answered on March 20, 2013 at 10:35 PM

@robinowsley

Sorry for the insanely late update, but I'd like to let you know that we have just released a fix for this bug.