I’ve just released version 1.3.1 of the plugin, which should resolve the issue with special characters. Could you please test it and let me know if there are any further problems?
Thanks for your patience and willingness to help with testing!
Hi,
Just updated and tested the form. Special characters seem to be working fine. Thanks!
I noticed some CSS changes, I believe. I have to tweek it a little but it shouldn’t be a problem. The checkbox input field has a flex-direction: column; and needs to be a flex-direction: row; I think.
I’ll also take a look at the translation to Portuguese (pt_PT). I was surprised to see it has so many strings, and then I found out a lot of them are countries.
As a feature request, there should probably be a way to change the appearance of the sent email. For example, the checkbox input field I mentioned, the label gets repeated in the email, as label and content. I use it as a consent input. It looks like this:
Nome: Teste 2 ÁÃàáõéçÇÉÊ
Email: ****
Telefone: ****
Mensagem: Teste 2 ÁÃàáõéçÇÉÊ
Aceito a cedência de dados para esclarecimento de dúvidas: Aceito a cedência de dados para esclarecimento de dúvidas
---
This email was sent to notify you of a response made through the contact form on https://clac.pt.
Time: 2025-01-23 21:57:05
IP Address: *******
Form URL: /modalidades/atletismo/
Thanks for your work. Let me know if I can help in anything else.
Special characters seem to be working fine.
Great! Thanks for your help identifying and resolving this issue. Marking this thread as resolved.
I’ll also take a look at the translation to Portuguese (pt_PT). I was surprised to see it has so many strings, and then I found out a lot of them are countries.
I debated whether to make these countries translatable, as I’ve noticed that both translated and non-translated country names are used on various websites.
As a feature request, there should probably be a way to change the appearance of the sent email. For example, the checkbox input field I mentioned, the label gets repeated in the email, as label and content.
This is a good callout! What would you expect the value to be here? Would you expect the value to be “checked” or “unchecked” depending on the state? I’ve added a GitHub issue to track this bug.
Hi,
Would you expect the value to be “checked” or “unchecked” depending on the state?
Probably the checked/unchecked would have the widest use, I guess.
Thanks.