powermail

I forgot to say that this happens in Version 2.0.0!

I can confirm the deletion of linefeeds/paragraphs. This not only occurs with text entered in textarea, but also with the rest of the text that is entered in the bodytext for email to reciever and sender aswell as the submit page.

For our needs it was sufficient to Wrap {variable} with the Nl2brViewHelper in Resources/Private/Templates/Forms/PowermailAll.html

<f:format.nl2br>{variable}</f:format.nl2br>

Jonas Renggli wrote:

For our needs it was sufficient to Wrap {variable} with the Nl2brViewHelper in Resources/Private/Templates/Forms/PowermailAll.html [...]

Where we have to modify the code?
I tried it but it didn't work!?
I only could see the web response site.

I did not use the variable {powermail_all} but dedicated variables in a table. I guess I have to modify another template, do I!?

Hi

It seems that the issue "also with the rest of the text that is entered in the bodytext for email to reciever and sender aswell as the submit page" is still there...

Best.

Yes, it works only with the variable {powermail_all}. If you take one concrete (textarea-)field like {meassage} or {address} e.g. the linebreaks still disappear!?

That what I got from a {powermail_all} form:
Test
Zeile 2

frei
Gruß KK

and this from a powermail-form with the variable {nachricht} although I inserted line feeds:
Test!!! Ext. Powermail auf neustem Stand! Diese Zeilen sollten nun nicht mehr zusammen gestaucht sein sondern mit Absätzen. Gruß aus Jülich Kurt Kunig

Had the same issue. My workaround is to press Shift-Return in RTE which creates <br/> instead of <p></p>. These <br/> won't be stripped off.

I can confirm this. <p>'s are stripped away in the confirmation mail.

I understand that I can use the Nl2brViewHelper in the PowermailAll template, but how are you supposed to work around this issue when not relying on the {powermail_all} placeholder?

You can't use {message -> f:format.nl2br()} as it isn't resolved. At the core, this is the same issue as http://forge.typo3.org/issues/39476 The proposed solutions to that issue do not work or are not practical.