First I didn’t notice any change, but then realized I had forgot to remove the disabling of autop in the wp-config.php ?? .
The fix in 5.7.1 seems to work fine in the rendered frontend, but not in the content of the email itself.
Here is what happens in my case. I’ll show what is defined in the my backend form and what comes out in the email content field in the receiving end.
My form is defined like this:
<table>
<tr><td>Navn</td><td>[Navn]</td></tr>
</table>
In version 5.6.4 the output in the email came out like this:
<table>
<tr>
<td>Navn</td>
<td>TEST Navn test 5.6.4</td>
</tr>
</table>
<table>
<tr>
<td>
Navn
</td>
<td>
TEST Navn test 5.7.1
</td>
</tr>
</table>
So extra p-tags, line feeds and indention spacing is still being added to the mail-content, because it consists of html code.
This is a problem because the forms are being processed by a fairly rigid conversion script in the receiving end. And I can’t edit that particular conversion script. Even the whitespace can present a problem in that process.
To declare all details: I have ticked off the “Use HTML content type” in the email definition in the backend.
I am aware that if I disable this function the autop is not happening. But it is not currently possible to do this as it will change a number of other things (multipart for one) in the email construct which will cause the conversion in the receiving end to break.
So I hope the changed behaviour in the email content can be avoided like it seems to have been avoided in the html frontend presentation of the form.
(Thanx for a tremendous form plugin!)
-
This reply was modified 1 year, 11 months ago by biberkopf.