Problem: You are transitioning to handling development internally and want to assign each country domain its own language without duplicating the site. You also need to automate country-specific legal and currency adaptations across 600 pages. Solution: If you're experiencing issues with assigning different languages to each country domain without duplicating content, we recommend upgrading from the WPML All Import to the newer WPML Export and Import plugin. This newer version supports various import methods that can facilitate managing translations and content adaptations more efficiently.
Please note that this solution might be outdated or not applicable to your specific case. 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 the issue persists, please open a new support ticket.
Problem: The client reported multiple issues related to WPML on their multilingual website, including untranslated category links, issues with the Amelia and Stylish Price List plugins, and pages that were not translated correctly. Solution: 1. For untranslated category links, we advised the client to navigate to WPML -> Settings -> Taxonomy Translation, set 'Categories (category)' to 'Translatable - only show translated items', and save the changes. This adjustment allows for the translation of categories, which can be done under WPML -> Taxonomy Translation. More details can be found in our guide: Translating Post Categories and Custom Taxonomies.
2. Regarding the Amelia Plugin, it is not officially compatible with WPML. We suggested checking the plugin author's advice for translating strings or considering an alternative plugin that is compatible with WPML. Compatible plugins can be explored here: Booking Functionality Plugins.
3. For the Stylish Price List plugin, which is also not compatible with WPML, we recommended using WPML's String Translation to search and translate the plugin's strings if available. If strings are not found, the client should refer to our guide on finding unlisted strings: Finding Strings that Don't Appear on the String Translation Page.
4. For the issue of pages not being translated, we requested more specific details about the pages that are stuck.
5. If the client wants to set up a multilingual website for international exposure, we suggested verifying the Language URL format settings, specifically considering 'A different domain per language'. More information is available here: How to Use WPML with Different Domains Per Language.
If these solutions do not resolve the issues or if they seem 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 further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: You are experiencing issues with ATE translations not completing, and those that do complete take many hours. The error log indicates an 'AMS Server Communication Api error missing resource: No sitekey found for this website.' Additionally, there is a concern about a base64-encoded data URI within an image source attribute that might not be intentional. Solution: First, ensure that your site is correctly registered with WPML and that your subscription for automatic translation credits is active, as these are prerequisites for the Advanced Translation Editor to function properly. If these are in order, the next step is to investigate the specific content causing the issue. In your case, there is an unusually large base64-encoded image URL within the content, which might be affecting the translation process. We recommend removing or replacing this image to see if it resolves the translation delays and errors. If the problem persists or if the solution provided here becomes outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket.
Problem: You are translating your website from Swedish to English using WPML and facing an issue where internal links are not being translated automatically in the WPML translation editor. This occurs even though English is set as 'hidden' in the settings, and you are using the WPML translation editor for Elementor pages, posts, custom post types, and templates. Solution: 1. Ensure that your WordPress Settings for the site URL include 'https' to match the frontend URLs. Go to WP Dashboard >> Settings >> General and replace both URLs to start with
https://
and then press 'Save Changes'. 2. Update the links in your Elementor Template to start with 'https' and then attempt to translate the links again. You might need to remove the old links and re-add them to ensure they are automatically translated. 3. Clear all types of caches (site, server, CDN) and then verify if the issue is resolved. Alternatively, try adding links on a new page and check if the automatic link translation works with the Advanced Translation Editor (ATE).
If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum at WPML Support Forum.
