Problem: If you're experiencing issues with certain elements not appearing translated on your German page, such as 'stratégie' not showing as 'Strategie', despite using the advanced translator. Solution: We recommend you try the following steps: 1. Add the following XML in WPML >> Settings > Custom XML Configuration section:
2. Make a small change in the default language page to reload the translation. 3. Open the translated page in WPML Advanced Translation Editor and press the Complete Translation button. If the issue persists, try these additional steps: 1. Open the default language page in Edit mode. 2. Make a small change, such as adding a space or + sign in the accordion title where you are facing issues. 3. Save the page. 4. Remove the small change made in step 2. 5. Update the page again. 6. Try to translate the page again. If you still encounter problems, especially with strings containing the ampersand (&) symbol, replace "&" with "and" in the default language accordion title and check if that resolves the issue. Alternatively, consider using a WPML-compatible blocks plugin from this list: WPML-compatible blocks plugins.
If these solutions do not resolve your issue or if they seem outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is attempting to copy content from an ACF block to a translated page using the WPML editor. However, instead of seeing the translated content, all content is being copied from the default language. Solution: We tested by switching the theme to Twenty Twenty-Four and deactivating all third-party plugins, leaving only ACF and WPML active. Using WPML's Classic Translation Editor, the image and link were successfully copied to other languages. We recommend using WPML's Translation Editor to copy the fields to other languages. If you need to use the WordPress editor instead, please contact us for further assistance.
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 at WPML support forum.
Problem:
When trying to add a third language to the website, the client was experiencing an issue where they were being redirected to the German page instead of being able to view the Italian page, even when logged in. There were no redirection rules set that would cause this behavior.
Solution:
We recommended checking if the content for the Italian page had been translated and if the translation was published. If the content was not translated or the translation was still in 'draft' or 'under review' status, the redirection to the German page was expected behavior. We advised the client to ensure that the page is fully translated and that the translation status is set to 'published'.
If the solution provided here is not relevant to your case, perhaps because it's outdated or doesn't apply to your situation, we encourage you to open a new support ticket. We also 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 further assistance is needed, please contact us on the WPML support forum.
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.
Problem: The client is trying to use an ACF block with a gallery field set to 'Copy Once' with the expectation that images added in one language will be copied to other languages without manual intervention. However, the client found that a new image added in the German version of the site was not copied over to other languages. Solution: We tested the issue by creating a test page and adding images to the gallery field. After publishing the page and translating it into English using the WPML translation editor, the images were copied as expected. Upon adding a new image and updating the page and its translation, the new image appeared correctly in both languages. We advised the client that if they are using the WordPress editor to translate pages, they must add images to the translated languages after the initial translation. To ensure images are copied to translations without manual addition, we recommended changing the translation preference from 'Copy Once' to 'Copy'.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket with us.
