Problem: You are trying to translate the links of CTA buttons to ensure users are directed to the correct language version (German), but the CTA button links are not included in the translation list, even though they are set to translatable. The buttons currently redirect to English pages instead of German. Solution: 1. Take a backup of your site first for safety reasons. 2. Navigate to WPML >> Settings page and press the Scan now and adjust links button. 3. Re-save the Permalinks from the Settings >> Permalinks page by pressing the Save Changes button. 4. Clear all sorts of site/server/CDN cache. If the issue persists, please follow these steps: 1. Open the translated page in Advanced Translation Editor. 2. Type
http
in the search input box. 3. Translate the URLs. 4. Press the Complete Translation button. For more details, refer to the documentation on how to translate links: https://wpml.org/faq/how-to-translate-links/
If this solution does not resolve your issue or seems outdated, we 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.
Problem: The client was unable to see the translated text on a button (CTA) on their multilingual site. The expected translation for 'See the international contacts' was not appearing in the secondary languages, and instead, the original English text was displayed. Solution: We recommended the client to: 1. Create a full backup of their site. 2. Update any outdated plugins or themes. 3. Flush any cache memory that might exist. 4. Re-save the permalinks. 5. Edit the page in the original language, make a small change to the button label, save the changes, and then update the translation. 6. Check if the issue was resolved after following these steps.
If you're experiencing a similar issue, we recommend you try the steps outlined above. Please note that the solution might be irrelevant due to it being outdated or not applicable to your case. If the problem persists, 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. Should you need further assistance, please open a new support ticket.
Problem: The client is experiencing errors when saving translations for some pages, such as 'About us', and receives a message indicating that something went wrong.
Solution: If you're encountering similar issues, we recommend checking the ATE error log located in WPML > Support > Advanced Translation Editor → Error log section. It's possible that the ATE server is having trouble transferring the translated XLIFF to your site. If you're using a firewall, ensure to whitelist the following domains:
wpml.org
cdn.wpml.org
api.wpml.org
api.toolset.com
cloudfront.net
Then, go to WPML > Support > Installer Support and click the "Check Now" button to confirm that everything is functioning correctly.
Next, perform the following steps:
Navigate to WPML > Support > Troubleshooting.
Click on the buttons to synchronize posts taxonomies for 'Pages', clear the cache in WPML, remove ghost entries from the translation tables, synchronize local job ids with ATE jobs, synchronize translators and translation managers with ATE, assign translation status to duplicated content, set language information, and fix post-type assignment for translations.
Make a small update to the default page and try to update the translation again using the ATE.
If the problem persists, please take a full-screen screenshot of the ATE Error log, ensuring all columns are visible, and share it with us for further assistance.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue remains unresolved, 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 necessary, do not hesitate to open a new support ticket for personalized assistance.
Problem: The client was unable to translate buttons created with Advanced Custom Fields (ACF) and had issues with URL slugs not being correctly translated or saved, particularly for the German language version of their site.
Solution: 1. To translate the button names, we advised the client to change the translation preference for the ACF fields from "Copy" to "Translate" by: - Going to "ACF → Field Group" and selecting the relevant field group. - Changing the Translation mode to "Expert" at the top of the page. - Setting the translation preference for the specific field to "Translate" and saving the changes. - Making a small edit to the page title in the default language and saving, then updating the translation.
2. For the German URL slugs, we recommended: - Switching to the German language in the Admin Dashboard using the language switcher. - Navigating to Pages > All Pages. - Using "Quick Edit" to update the slug for the German page and saving the changes.
3. If the client was manually adding German translations and then using the Translation Editor, we noted that the manual changes would be overwritten. We suggested always manually adding translations if they started that way.
If the solution provided is not relevant 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 you still need assistance, please open a new support ticket at our support forum.
Problem: The client was experiencing an issue where the layout of the translated page, which was built with custom fields, was broken and not all CSS styles were working.
Solution: We checked the site and found that the field groups did not have a translation mode set. We selected "Same fields across languages" in the About Us field group. Then, we updated the page in the default language and its translation. We advised the client to edit their field groups to select the translation mode and provided a guide for reference: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, we recommend opening a new support ticket. We also 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 contact us in the WPML support forum.
