Problem: The client was experiencing an issue where pagination on a custom post type 'News' did not function correctly in Lithuanian on their WordPress site using WPML, despite working in English. The issue persisted even after switching permalink settings and updating plugins. Solution: We recommended updating the ACF plugin to the latest version as a first step. If the issue persisted, we suggested replicating the problem on a clean WordPress installation to isolate the issue. We set up a sandbox environment for this purpose. Additionally, we updated WPML and related plugins to their latest versions and adjusted settings related to slug translations. If these steps did not resolve the issue, we advised creating a custom PHP template for the archive that replicates the Beaver Builder design and using different slugs for the page and the custom post type.
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: You are working on a site where English is the default language, and you have created a custom British English version by duplicating the English pages. However, when editing the British English translation through the WPML translation window, you notice that numerous image elements marked as 'HTML attribute' appear, which do not show in the translation window for other languages. The British English page is not currently synced to the original English page. Solution: If you have been editing the British English pages directly in Beaver Builder, it is crucial to continue using this editor to maintain consistency. Mixing translation methods, such as editing some translations in Beaver Builder and others in the WPML Advanced Translation Editor (ATE), can lead to lost changes or inconsistencies. Therefore, we recommend choosing one translation method and sticking with it to ensure all elements are correctly synchronized and displayed.
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 for further assistance.
Problem: You are trying to use WPML's Menu Sync to automatically create menu items that link back to the default language when a translated version doesn't exist. However, Menu Sync only generates menu items for content that already exists in the target language and does not create links for untranslated content. Solution: Menu Sync is designed to only generate items for content that exists in the target language and does not support automatically linking to fallback (default language) content when a translation doesn’t exist. To include menu items that link to untranslated content, you will need to manually add these links to your menus. Currently, there is no automated solution within WPML to include fallback links in translated menus. For more details on translating menus with custom links, visit Translating Menus with Custom 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is trying to use WPML's Advanced Translation Editor and Automatic Translations for translating content from English to French, but not from English to Canadian English. They are concerned that the Advanced Translation Editor might automatically translate English (Canada), which is mapped to the default language of the site and should not be auto-translated according to WPML documentation. Solution: We advised the client to manually control the translation process to avoid automatic translation for English (Canada). This can be achieved by: 1. Activating the option in WPML -> Settings to control which content is sent for automatic translation. 2. Using the WPML -> Translation Management to filter content by the original language (English) and manually sending it for automatic translation in French. For English (Canada), since automatic translation is not supported due to its mapping to the default site language, it is not necessary to map it for automatic translation unless desired by the client.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket.
Problem: You are trying to assign automatic translation credits to your site, but the domain is not appearing in the list of sites to which you can assign credits, despite being included in the list of registered sites. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Delete the site key from your WPML.org account. 2. Navigate to your site's dashboard, go to Plugins -> Add New -> Commercial tab. 3. Unregister WPML. 4. Create a new key for this site in your WPML.org account. 5. Register WPML on your site. 6. Check if the site now appears in the list of sites to which you can assign automatic translation credits.
This solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.
