This thread is resolved. Here is a description of the problem and solution.
Problem: The client was unable to translate an updated Gravity Form despite having translation credits, encountering an error when attempting to review the translation. Solution: If you're experiencing this issue, we recommend that you ensure you are set as a local translator with the correct language pairs in your WPML settings. Here's how you can do it: 1. Navigate to WPML > Translation Management > Translators. 2. Verify that you are listed as a local translator and that the correct language pairs are assigned to you. For more detailed instructions, please refer to our documentation on setting up local translators and language pairs: https://wpml.org/documentation/translating-your-contents/how-to-set-up-local-translators-and-language-pairs/
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at WPML support forum for further assistance.
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.
I have tried to translate my updated Gravity form now that translation credits have finally been added to the account. However, I get the error in the screenshot. Same error if I click 'Review'.
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 first debugging steps or if I can perhaps help with the issue quickly.
I checked your debug info and noticed that your website doesn't have the minimum memory required for WPML to work. WPML requires a memory limit of at least 128MB while 256MB is recommended. See https://wpml.org/home/minimum-requirements/ for detailed information. You can set WP Memory Limit in your wp-config.php file by adding the following code:
We don't believe this is the issue, since most other items in the list can be reviewed and approved without error.
It is just the gravityforms (so far) that are not working.
They were translated when we first created them, however now we've made updates to the form, we need to re-translate.
Thank you for contacting WPML support, I’m happy to help you with this issue.
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.
(If this must be split off to a separate support query, please copy the site access details as above so I don't have to find/copy them all again)
I am trying to translate all these strings: hidden link
However for all strings I get the message "will be ignored, because translation is already waiting for translator."
That's because we tried sending them for translation previously, when the site had no credits.
How do I reset this and translate all these automatically?
Many thanks
New threads created by Long Nguyen and linked to this one are listed below:
I can review and approve the translation of Gravity Forms on your production site as well, check the attached screenshot.
Please go to WPML > Translation Management > Translators > Ensure you are a local translator and have the correct language pairs.
Many thanks - the missing link was that I needed to add myself as a translator with the correct language pairs.
Louise Fox confirmed that the issue was resolved on 2024-05-14 09:45:38.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.