We are sorry for the inconvenience caused. We are able to replicate the issue, the issue is because of sanitization as it adds /(slashes) if it finds ” or ` as it sees them as special characters, we’ve resolved the problem on our end. The fix will be available after testing on Monday.
Going to the next line should work, exactly how it works in any text editor by pressing the enter key, will it be possible for you to share an example of the template you are using, so we can test it on our end, as we are not able to replicate this new line issue. And we are sorry to say currently HTML is not supported, you can only use plan text.
Thanks for the screenshots, I tried the same template as yours and it is working as expected, please see the screenshot. I have tried it on multiple, Clients like Gmail, Zoho, and outlook and on all the clients it does have empty lines as we want.
So it seems like the something is stripping the empty lines after Loginizer sends the data to wp_mail to send the email. Would you please tell us if you have any SMTP plugin enabled? And would you try to test the same email, on some other email client.
Or you can try disabling all other plugins and then see if you face the same issue.
Would you please try the same template and send it using the Test option of GoSMTP and see if that strips the empty lines, it is to confirm if wp_mail is stripping the empty lines or not.
Thanks for testing that out, it seems like wp_mail strips that, would you please tell us which version of WordPress you are on? Will look if there is a work around, else will add an option to send a HTML email.
Please try deactivating other plugins and see if that fixes the issue you are facing. If it does works after deactivating other plugins then enable then one at a time, and check after enabling which plugin Loginizer error stops working, as it could be possible that some plugin is overwriting over Loginizer.
Thanks for trying it out. I looked into it and it looks like you are using shortcode to show the login form would you please confirm that, and if you are, then were you using it earlier too? When the errors where working?
Because we tested with Popularfx and Pagelayer enabled and it was working for us, so we want to try the exact way you have implemented the page, to be able to reproduce the issue.
