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.
Problem: Some pages are not updating their translation status. Solution: First, ensure you are using the latest version of WPML and update if necessary, including any WPML addon plugins. Then, follow these steps: 1. Go to WP-Admin -> WPML -> Translation Management -> Jobs and cancel the job for the pages you're having issues with. 2. Navigate to WP-Admin -> WPML -> Translations and click on "Resign" for the problematic pages. 3. Edit the primary language page by making a small change to the title (e.g., adding a "+" sign). Then, attempt to edit the secondary language page. * Note: Please ensure you have a full backup of your website before making any updates or changes to prevent potential data loss.
If the solution provided here is not relevant due to being outdated or not applicable to your 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 with us.
Problem: The client was unable to save the homepage and encountered errors related to WPML and translation jobs.
Solution: We recommended the client to take the following steps: 1. Ensure a full backup of the website and database. 2. Deactivate all plugins except WPML and its addons to check for the issue. 3. Reactivate each plugin one by one, checking the issue after each activation to identify any conflicts. 4. If the issue persists, repeat the steps with a default WordPress theme.
The client resolved the issue by removing translation jobs that were still present, possibly due to removing a translator without canceling their jobs.
If you're experiencing similar issues, we recommend you follow the steps outlined above. However, if the solution does not apply to your case, or if it's 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 the problem persists, do not hesitate to open a new support ticket with us for further assistance.
Problem: The client reported that the menu language switcher was not showing on their website, even though they had added it as the last item in the menu and also as an Elementor widget. The switcher was only visible in the footer.
Solution: Upon investigation, we discovered that the Language Switcher was set to display on the wrong menu. We corrected this by selecting the appropriate menu called "Testing" in WPML -> Languages -> Menu language switcher, which resolved the problem.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us.
