Hello @nelchee,
Thanks for bringing this to our attention. It seems like the fix in version 3.8.2 has introduced a bit of a hiccup for your custom translations and labels. We definitely want to get this sorted for you, especially since it’s affecting how your form displays on your site.
Could you reach out to our Customer Success team? They’re well-equipped to dive deeper into this issue with you. Plus, by logging this problem, it’ll help us keep track of it and ensure we’re working on a solution that’ll benefit not just you, but all of our users facing similar challenges.
Here’s where you can get in touch with them for more personalized support: https://ninjaforms.com/contact/. Don’t hesitate to share all the details you’ve mentioned here; it’ll help speed up the process.
Looking forward to helping you resolve this!
Thread Starter
Nela
(@nelchee)
Hi Shaylee,
I was under the impression that this official WordPress.org support forum is where we are able to send in our issues, and that a support representative will forward anything submitted here to a relevant department. There’s really nothing else I have to add. You can easily recreate the scenario on your end with the information I provided.
I don’t need any personalized support, I would rather it be transparent and public so that other users can see it.
I’d also appreciate not marking topics “Resolved” when the issue has in fact not been resolved.
My issue persists either until the bug is fixed in the new version of the plugin, or if you state that this is now a “feature not a bug”, and HTML in translations is simply no longer allowed.
Hello Nela,
I understand your concern about the restrictions on using HTML in custom translations. To clarify, these restrictions are in place to enhance security and prevent cross-site scripting (XSS) attacks. XSS attacks can exploit the capability to inject HTML or JavaScript into fields, potentially compromising your website’s security.
While we recognize this might limit some customization options, our priority is to ensure the safety and integrity of your forms and the data they handle. If your translation requirements are purely textual without HTML, you should be able to apply custom translations without encountering the forbidden characters error.
If the issue persists or if there are specific translation needs that you feel are not being met due to these security measures, please let us know.
We’re committed to ensuring that Ninja Forms meets your needs effectively while maintaining a high standard of security.
Thank you for your understanding and cooperation.
For any additional assistance, please feel free to contact our Customer Success team. We offer free support for all users, so don’t hesitate to reach out!
