Home›Support›English Support›[Resolved] Translation of gravity form possible via po edit file in string translation?
[Resolved] Translation of gravity form possible via po edit file in string translation?
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is trying to manage translations for large Gravity Forms and is encountering issues where the forms are not appearing in the translation management editor. The client was previously advised to export, delete, and re-import the forms to make them appear again, but is looking for a more efficient solution. The client is considering using .po files for translation through String Translation but has received mixed advice on this approach.
Solution: First, we recommend trying to duplicate the form, as the new one should appear on the Translation Management board. If this does not resolve the issue, we suggest using the WPML Advanced Translation Editor (ATE) for translating Gravity Form entries. ATE provides several benefits: - Avoiding translating the same sentences multiple times. - Keeping translations on our server to prevent loss when translating content manually. - Access to features only available in ATE. For more information, please refer to our documentation on the Advanced Translation Editor and Gravity Forms Multilingual.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Tell us what you are trying to do? It looks like the translation of our gravity forms are broken. (They are not appearing in the translation management editor when sent to translation) I had a chat last week with one of your support team member who suggested to export the forms, delete them from the site and import them again. By that we can indeed send them to the translation management editor again. It's not an optimal solution however, as we have long forms which need to be translated in to three languages. I was wondering now whether it is possible to adjust the translations via exporting the strings of the form on a .po file in the string translation. Is that something you can recommend?
Thank you for contacting WPML support. While you are waiting for one of my colleagues to take this ticket and work on it, let me provide you with the first debugging steps and try to help with the issue quickly.
If you have used automatic translation or Advanced translation editor to translate these forms, the translations are saved in our translation memory.
You can easily send them again for automatic translation or re-translate and the translation should already be there in editor if you have translated them before.
Adding translation via WPML String translation for Gravity forms is not recommended and might cause issues.
thanks for your help. Unfortunately I can't find the chat I had last week in my support tickets with you. We don't want automatic translations, we use the classic editor. I can send you the credentials to log in to see yourself what the problem is. As you can see from the screenshot, after trying to send in the form to translate, they won't appear in the translation management view. Your colleagues conclusion was that the translations were corrupted. And that we should export the form, delete the form and import it again. But as I said, we rather not translate the whole form again. And on the .po files most of the translations are still present.
Thank you for contacting WPML support, I’m happy to help you with this issue.
Just want to clarify that, using the Advanced Translation Editor doesn't mean you have to use the automatic translation with credits. You can still translate the content manually.
The translation sentences are saved to the translation memory which is stored on our server and you won't need to translate the same sentences next time. Please read more about this feature in the documentation https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/
Regarding the main issue of this ticket with the form entry is not available on Translation Management board, I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to have a testing site where the issue is replicated. Your next reply is set to private to share the info.
❌ IMPORTANT: Please backup your database and website before proceeding ❌
You can use this plugin to create the backup: https://wordpress.org/plugins/duplicator/
✙ I would need your permission to de-activate and re-activate Plugins and the Theme to change configurations on the site if needed. This is also a reason the backup is critical.
I see the issue with the current form entries. If I create a new form and send it to translation, it is available in the Translation Management board properly.
There is a workaround to translate the form content, you can go to WPML > String Translation > Filter by the domain "gravity_form" and translate strings there.
Also, I'm trying to take a backup of your site and restore it on my local site to investigate the issue further.
Hi Long, thanks for your reply. What you are suggesting was actually my initial question: If it is possible or ok to translate the form through string translation with a po file.
I appreciate if you can investigate the problem further and give advice on my question regarding a po file translation for the form.
Thanks for your reply. Your suggestion seems to do the same thing than what was suggested in my last ticket (see my initial question at the top of this ticket): We will need to start from scratch with all the translations which we try to avoid if possible.
Thats why I asked whether we could export the .po file of the form in the string translations because there the translations are still visible. But it sounds like this is not recommended (initial response from Drazen).
I wonder whether it is possible to take these .po files and convert them to .xliff files which we then could import in the translation manager for the newly duplicated form. Is that something which could be feasible to do?
I understand your issue, but the difference here is, you won't need to re-create the form from scratch. Duplicating the form would keep all the content of the current form and you can translate the new-duplicate form with Advanced Translation Editor (ATE).
We recommend using ATE because the translation sentences are saved to the translation memory as I mentioned above. If you prefer translating the form using .po file in String Translation, you can keep using that way if it works for you.
Note: I've not tested this tool before to guarantee it works with WPML. If it doesn't work, I would recommend you contact one of our certified partners who will be more than happy to help you with this. In this link, you will find a list of our certified partners: https://wpml.org/contractors/
Thanks for your reply. I had a look at the duplicated form "Create User and Project (1)" in the ATE editor. However, I don't see any translations there as I would expect reading your text about translation memory.
What I now tried was the following: In the string translations I exported the .po file from the initial form, fixed a few errors in there, renamed it to suit the duplicated form and imported it for the new duplicated form. That works for the front end but I know expect to see the translations set in the string translations also in the ATE. However there the fields are still blank. How can I get the translations set in the string translations in the ATE editor?
Thanks for your help
kind regards
Nina
New threads created by Long Nguyen and linked to this one are listed below:
We can handle one issue per ticket only, if you see the main issue of this ticket with the Gravity form available in Translation Management is resolved, please mark it as Resolved.
I will split your new question with translation in ATE into a new ticket for better handling.
To be clear: My aim is to figure out for my clients what the best work flow is for them to manage the translations of their big forms in the easiest and safest way possible. It's a real shame they have to redo all the translations from their current forms as something seems broken there.
So I hoped to reduce their work load by working out whether doing the translations via .po file and string translations is a feasible way to go as some of the strings are still translated there. Regarding this issue I hear mixed messages from your support: Drazen replied in his first message "Adding translation via WPML String translation for Gravity forms is not recommended and might cause issues.", I take from your replies that it could be ok. As I want a future proofed solution I'm unsure if this is now a good workflow. Could you give us here a last advice on that topic?
Generally, you can use both ways to translate the Gravity Form entries: via String Translation or via WPML Advanced Translation Editor (ATE).
However, as my colleague said, we recommend using ATE for an easy and safe workflow. There are some benefits when using ATE:
- not translating the same sentences.
- keep the translation on our server and prevent losing the translation when translating content manually.
- and some features only available in ATE, please follow the documentation https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/ https://wpml.org/documentation/related-projects/gravity-forms-multilingual/
