The client was experiencing issues with ACF fields not being translated in their products, displayed in white boxes within an Elementor Loop Grid. In the English version, these fields appeared as empty spaces. Additionally, the links within these fields did not translate correctly and targeted the original language URLs instead of the translated ones.
Solution:
We advised the client to set the 'acf_field_group' CPT to 'Not translated' in WPML > Settings > Post Types Translation, as having it set to 'translated' is not recommended. This change required re-translating the products where the ACF fields were missing.
For the links in the Elementor template, we identified a bug where the 'URL' field set to 'copy' by default was not being automatically converted.
As a temporary workaround, we suggested switching the field group to the 'Expert' mode and setting the 'URL' field translation preference to 'Translate'.
After updating the original post, the 'URL' field will appear in the translation job, allowing to manually convert the URL.
Problem: If you're experiencing repeated API errors stating 'No sitekey found for this website' when trying to translate a page or post, it indicates an issue with the sitekey in your WPML account. Solution: We recommend you try the following steps to resolve this issue: 1. Remove the old sitekey from your WPML account. 2. Navigate to Plugins → Add New and open the Commercial tab. Click on 'Unregister WPML from this site'. 3. Once the page reloads, click on 'Register WPML'. You will be prompted to enter a sitekey. Click on 'Get a key for this site'. 4. Complete the sitekey creation wizard in your WPML account and specify the site type as 'Production site'. 5. Copy the new key and paste it into the Commercial tab in the WordPress admin panel. Additionally, ensure that the REST API is enabled on your site, as it is crucial for WPML's operation. You can check the REST API dependencies here: https://wpml.org/documentation/support/rest-api-dependencies/
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket for further assistance.
Problem: The client is experiencing issues translating a template into five different languages. In some languages, the template appears in advanced mode, while in others, it remains in a simpler, previously used mode. Additionally, links that were translated in the simple mode are not translated in the advanced mode, and previous link translations are forgotten. Media images are also not translating, including previous translations. Solution: If you're experiencing similar issues with translating content in different modes, we recommend switching to the Advanced Translation Editor (ATE). It's important to note that any content previously translated using the Classic Translation Editor (CTE) will not automatically appear in the ATE. However, these translations should still be visible on the front-end of your site. You can manually open the translated pages on the front end and copy the content, including links, if necessary. This means that the content will need to be retranslated using the Advanced Translation Editor.
Please note that this solution might be outdated or not applicable to your specific 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.
Problem: The client received an email notification stating that their site has run out of translation credits and translations are paused, despite not using the automatic translation feature. They requested information on which pages the credits were used and by whom, and also asked to disable the automatic translation option. Solution: We confirmed that about 3500 automatic translation credits were used on a specific page, but we do not store information about which specific user triggered the translation job. To prevent future use of automatic translation, ensure that the 'Translate Everything Automatically' setting is turned OFF. Additionally, in the WPML Advanced Translation Editor, you can select 'Do not automatically translate when opening the editor' from the settings icon to avoid automatic translations when a page is opened in the editor. Since automatic translations are disabled and no credits are assigned to the site, there is no risk of credits being consumed accidentally.
If the solution provided here does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please feel free to open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with their WooCommerce store using WPML for automatic translations. Specifically, German product translations are mismatched, URLs are incorrect, and changes in the Dutch version do not automatically update the German and English versions. Additionally, menu structures are not synchronized across languages.
Solution: We advised the client to ensure that the WPML Translation Editor is enabled for automatic translations, as the products were set to use the WordPress editor, which requires manual translation input. This setting can be changed by selecting the WPML editor icons and applying it to the post type for the entire website. We also noted that the Permalink Manager plugin might be causing issues with translated URLs as it is not officially compatible with WPML. We recommended disabling or replacing this plugin. For detailed steps on setting up automatic translation correctly, please refer to this video: https://www.awesomescreenshot.com/video/50256133?key=633279713084c99ea425f50e0d22b565.
If this solution does not resolve your issues or seems outdated, 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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: You are unable to translate Avada Forms due to an error indicating that '2 items could not be completed due to an unexpected error. Please resend them for translation. If the problem persists, contact WPML support.' The error message specifies an issue with the uploaded XLIFF file, particularly with the target data. Solution: We have identified that during the translation process, the job is translating
<[email]>
into an empty string, which prevents WPML from saving the translation correctly. We recommend replacing
<[email]>
with https://pastebin.com/raw/E9fb9jLb. This change encodes the HTML characters and helps prevent the parsing issue causing the problem.
If this solution does not resolve your issue or seems irrelevant due to being 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 needed, please open a new support ticket at WPML support forum for further assistance.
