How do I prevent specific form from string translation

Hi @fyyfabian,

The Everest form is translation-ready, and it will translate the strings according to the translation plugin feature. It is currently impossible to translate strings according to the form because the Polylang plugin string translation will work on all the forms.

After translating the strings, you can use both forms, but you need to choose the specific language page. When you use the Swedish language page with a Swedish form, it will display the translated Swedish string. If you have added the Swedish form to your English language page, then the translation of the strings does not work.

Would you please try the recommended suggestion once? If it does not work, please provide us with a screenshot of the string translation and the Swedish form link.

Thanks!

So it’s not possible to not have string translations on any form. I only want string translation for the header on the front page. The rest of my site I would prefer to be free from string translation. Isn’t that possible? Isn’t there any additional CSS code or something I can use?

Hi FyyFabian,

Yes, it is not possible to translate specific forms using the translation plugin. As we have mentioned, the optional and functional values will be translated from the string translation feature provided by the translation plugin, so you can not separate the specific form in string translation.

The translation is not part of the design, so the CSS code can not be used. We recommend you use the string translation feature and place the Everest form shortcode on the associative language page to work correctly.

Regrads!

Hi Amrit! Thanks, but I don’t think you understand my question (or I don’t :)) But I don’t want any forms translated at all. I have created two separate forms instead, one in English and one in Swedish, and I want to exclude them from string translation. Isn’t that possible?

Kind regards
Fabian

Hi Fabian,

Sorry if we are not clear in the previous response,

String translation can not complete automatically. You need to do it manually from the translation plugin settings(that means the string translation is excluded by default). When you create the two different language forms, it requires the string translation.

For example, if you have set any field required, then the user does not fill that field, then it displays the message “This field is required” if you want to show this message in a different language, you need to translate this string to your respective language.

If we are still not getting what exactly you want to exclude from the translation, please provide us both form links and the screenshot of the strings you want to exclude from the translation.

PS: The temporary solution for excluding translation is to delete the language file folder from the Everest form plugin.

Regards!

Thanks! We’re getting there. I don’t want anything translated at all. No string translation associated with the forms at all, so to speak. When I delete the Everest form strings in Polylang they just pop back up again.

If I understand correctly, I should find the language folder in Everest forms, and delete that language folder, am I right?

Kind regards
Fabian

Hi Fabian,

Thank you for writing back,

Yes, please open the Everest Form plugin folder using FTP or Cpanel. You will find the language folder. If you delete that folder, it will stop the translation, but the update of the plugin always restores this folder, so we have mentioned this solution is temporary.

Regards!

Thanks!

So there is no permanent solution to this? Any other option to exclude the forms from string translation?

Kind regards
Fabian

Currently, it is not possible because we need to make the product translation ready. Polylang stores the translations in the database (as post type ‘polylang_mo’ in the ‘wp_posts’ table, to be precise). If you contact the Polylang support team, they can provide you with the exact location and instructions for the permanent solution.

Regards!

Thank you! I will contact Polylang for a permanent solution.

Kind regards
Fabian