Problem: After migrating a site from a temporary Cloudways staging URL to a final domain, WPML is not recognizing the sitekey, and all translation jobs are failing. Errors include 'AMS API returned false' and 'HTTP 426: WPML has detected a change in your site's URL'. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Make a small change on a page in the default language. 2. Save the page. 3. Then click to translate it again. This should trigger a new translation job and refresh the connection.
If the solution provided here does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: The client is experiencing an issue where the language switcher on the author page only displays the primary language (Dutch) and does not show the option to switch to English, despite the English version of the author page being accessible directly via its URL. Solution: We recommend checking if the author of the posts on the author page has their posts translated into the secondary language (English). The language switcher will only appear if the author has blog posts and they are translated. If the posts are translated and the issue persists, you may need to implement custom coding to ensure the language switcher always appears. An example of how to handle this with custom code can be found in our support forum: https://wpml.org/de/forums/topic/empty-author-archive-langauge-switch/#post-14442559.
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 our support forum.
Problem: If you're experiencing issues with the Elementor Image Carousel not displaying images on translated pages, it might be due to the archive template translation not being fully completed. This issue is evident when the Image Carousel widget doesn't load on the translated version of the page. Solution: First, ensure that the Archive template for the post type in question is fully translated. Since the template was created with Elementor, we recommend following the guide on translating Elementor templates, which can be found here: Translating Elementor Templates. Next, open the translated template in the Elementor editor to check if the Image Carousel widget is present and the Dynamic Tag is correctly selected. If the template is correctly set up and images still do not appear, you may need to copy the images from the default page to the translation: 1. Navigate to "WPML > Settings". 2. Scroll to the Media Translation section. 3. Select the options as shown in this screenshot and click on the Start button. 4. After the process is completed, clear the caches from your site and browser. 5. Check the translated version of the 'Inspiration' page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at WPML 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 trying to translate the link text of the link field in the Advanced Translation Editor, but it's not showing up. The ACF Link fields are not visible in the editor. Solution: We recommend setting the field group to "Expert" mode and marking the content and button fields as translatable. This adjustment should make the fields appear in the Advanced Translation Editor. Additionally, check if there are multiple fields with the same slug, as this can cause a conflict. If so, rename one of the fields to resolve the issue.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so at the WPML support forum.
