Problem: The client installed the WPML plugin and translated almost the entire website, but the menu remains in Italian when switching languages. The menu is created using the Divi Theme Builder and the Divi Menu Flex plugin, with each item linking to a Divi Layout used as a submenu. Solution: We checked the client's setup and restored the default WPML translation settings for the Divi Theme Builder as per the recommended defaults found here: https://github.com/OnTheGoSystems/wpml-config/blob/master/Divi/wpml-config.xml. After restoring the settings, we saved the default header template and translated it via WPML → Translation Dashboard, which corrected the menu appearance in the secondary language. However, since the client is using the DiviMenus plugin, a third-party solution, some elements were still not being translated or copied properly. This issue requires WPML compatibility within the plugin itself, typically involving adding proper XML configuration and implementing WPML hooks in the plugin code. We recommend contacting the plugin author and sharing the following documentation with them to achieve WPML compatibility: https://wpml.org/documentation/support/achieving-wpml-compatibility-for-your-themes-and-plugins/ and https://wpml.org/documentation/support/go-global-program/.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where the 'Join Us' button in the header is not translated into Portuguese despite being translated in the backend and in Elementor, or if your Member Directory page links are not visible in the Portuguese version and clicking on logos results in a 404 error page, here's what we recommend. Solution: For the 'Join Us' button translation issue, please ensure that your translations are correctly configured in both the backend and Elementor. If the issue persists, we might need to access your site to further investigate the configuration. Make sure you have a full backup of your site before proceeding. For the Member Directory page issue, the problem might be related to the shortcode used:
. This shortcode might not be filtering content by the current language in the frontend. We recommend contacting the authors of the shortcode to check the query behind it, particularly the suppress_filter attribute.
Please note that the solution provided 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.
Problem: The client wants to share automatic translation credits between their original site (https://www.alotofspirits.com) and a new site (https://alotofspirits.com) after a URL change, but they need a migration code to do so. Solution: 1. Log into the original site (https://www.alotofspirits.com). 2. Navigate to WPML → Translation Dashboard and select the Payments & Maintenance tab. 3. In the Automatic Translation Engine section, click on Connected sites. 4. Press the Copy Migration code button. 5. Return to the new site (https://alotofspirits.com) and paste the code into the migration wizard as requested.
If this solution does not apply to your case, or if it seems outdated, 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. For further assistance, please contact our support team at WPML support forum.
Problem: The client has a multilingual website and is concerned about not receiving much traffic from English-speaking countries. They are considering the use of Hreflang tags to improve their SEO but are unsure if this is the right approach. Solution: We explained that while we are not SEO specialists and cannot provide specific SEO advice, it is recommended to consult with an SEO specialist who can review the site and its goals comprehensively. We also mentioned that WPML is not an SEO plugin, but we do offer a WPML SEO plugin that helps other SEO plugins work effectively on multilingual sites. If the client decides to use an SEO plugin, we provided a link to a list of SEO plugins compatible with WPML: https://wpml.org/plugin-functionality/seo/
Please note that 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 you still need assistance, please open a new support ticket or visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: If you're wondering whether WPML is compatible with PHP 8.5, it's important to note that WPML might work with PHP 8.5 in some scenarios, but it has not been fully verified for this version. Solution: We recommend using PHP 8.2 with WPML as it is the version that has been fully tested and verified for compatibility. If you're experiencing issues with PHP 8.5, consider downgrading to PHP 8.2 or wait for future updates where full compatibility with PHP 8.5 might be ensured.
Please note that 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 for further assistance.
Problem: The client was experiencing issues with WPML where some internal links were missing parent page parts in the URL, and some links were broken due to incorrect CDATA/script-related URLs. Additionally, button labels were not translating correctly. Solution: 1. We performed a cleanup by clearing the WPML cache, removing ghost entries from translation tables, and syncing translation jobs. This can be done from WPML → Support → Troubleshooting. 2. We re-translated the affected pages, which did not consume additional translation credits as the translations were loaded from memory. 3. For the broken links caused by JavaScript code or custom HTML, we recommended removing such code from the page content or using a shortcode with custom code outside the page content. 4. For internal links, ensure they are inserted correctly in the WPML Translation Editor and complete the translation process. 5. For the button labels in Gutenberg, if they are not appearing in the WPML Translation Editor, it may be necessary to open a new ticket to investigate how the block is structured. 6. For persistent broken links, manually replace them in the WPML Translation Editor and save the translation.
If these steps do not resolve your issues or if the solution seems outdated or irrelevant 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You have translated your pages using Elementor, and they are marked as translated, but they display in English instead of the expected language. In the revisions, only English is visible, despite previously working correctly. Solution: This issue often arises from a mismatch between the method used for translation and the editor WPML expects to be used. Here are the steps to resolve this: 1. Open one of the affected pages in the default language. 2. In the right sidebar, locate the “Translation” section. 3. Check if it indicates that the page is translated via WPML Translation Editor. 4. If it does, switch to the WordPress editor so you can continue using Elementor for translations. For more details, visit Using Different Translation Editors for Different Pages. Note: Using both Elementor manually and the WPML editor can cause this type of issue.
If this solution does not apply to your case, or if it seems outdated, 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.
Problem: The client wanted to transfer 2000 credits from a development website to a production website but was unable to do so. Attempts to transfer the credits directly or retrieve them by deleting the site key were unsuccessful. Solution: We explained that the 2000 credits provided by WPML are complimentary and tied specifically to the site for which they were originally assigned. These credits cannot be transferred to another site or withdrawn back to the account. Therefore, the credits seen on the development site remain there and cannot be moved to the production site.
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: You are developing a website using the Ekko theme with WPBakery and encountering issues where page components are not available for translation in the Advanced Translation Editor. You have tried adding a custom XML configuration, but it did not resolve the issue. Solution: Each custom page builder widget requires a proper configuration to be translatable with the WPML Translation Editor. This configuration is typically the responsibility of the theme or plugin author. Since your theme is marketed as WPML-compatible, we recommend contacting KeyDesign to report the issue (https://keydesign-themes.com/). Additionally, you can create a custom XML configuration yourself and save it at WPML > Settings > Custom XML Configuration. For guidance on maintaining compatibility with WPML, you can refer to our WPML Developer Guide (https://wpml.org/documentation/support/maintaining-wpbakery-page-builder-compatibility-with-wpml/). If you need further assistance, feel free to contact us, and we can help you create configurations for one or two widgets.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues (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 for further assistance.
