Problem: The client was facing an issue where the header and footer created with Elementor and Ultimate Addons for Elementor were not displaying for non-default languages, despite having completed translations for these elements. Solution: We identified that the "Display Rules" were missing on the translated templates. To resolve this, we: 1. Navigated to WPML > Settings > Custom Fields translation. 2. Set the following fields to "Copy":
ehf_target_include_locations
ehf_target_exclude_locations
ehf_target_user_roles
ehf_template_type
display-on-canvas-template
3. Updated the translations for the templates, which resolved the issue. For more detailed guidance, please refer to our documentation on Translating Custom Fields.
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.
Problem: The client's menu is not displayed. Solution: If you're experiencing this issue and your site is using Elementor Pro, we recommend checking if the header was created using Elementor. If so, ensure that the header is translated. You can find guidance on how to do this in our documentation on Elementor compatibility with WPML.
If this solution does not apply to your case, or if it 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 you still need help, 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: 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 has a Lifetime account with WPML Multilingual CMS and finds the current setup too complex, with unnecessary features and files. They are looking for a way to simplify their WPML setup or downgrade to a Multilingual Blog without purchasing a new subscription. Solution: We explained that the Lifetime account type cannot be downgraded as it is no longer available for purchase and does not require yearly renewal. To simplify the WPML setup, we recommended deactivating all additional WPML plugins, keeping only the core plugin active. This approach simulates the Multilingual Blog setup. We also provided a link to our documentation for the standard translation workflow for the Multilingual Blog version: https://wpml.org/documentation/translate-website-with-wpml-blog/
If this solution does not fully address your issue or if it 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.
Problem: The client was unable to attach a WPML language switcher to the 'main' menu on their development website, which was built using Elementor. WPML did not recognize the menu, and the client preferred the language switcher to be integrated directly within the menu rather than as a separate element. Solution: 1. We advised the client to ensure that the menu is translated, as WPML requires menus to be translated to assign a language switcher to them. Detailed steps for translating menus can be found here: https://wpml.org/documentation/getting-started-guide/translating-menus/ 2. After translating the menu, the client can add a language switcher to it via WPML -> Languages. 3. We also recommended increasing the WordPress memory limit to at least 128MB, as per WPML's minimum requirements. This can be done by adding the following code to the wp-config.php file:
This code should be placed above the line /* That's all, stop editing! Happy blogging. */. The client can verify the WordPress memory limit in WPML -> Support.
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.
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: The client's primary website language is English, and they have secondary languages including Italian, French, and German. A customer left a product review in Italian, which the client translated using WPML string translations for display in other languages. Despite following the necessary steps and clearing the cache, the translated reviews are not visible on the live frontend page in languages other than Italian. Solution: We identified that WPML registers a review for each product separately. In this case, the review translation was created for the translated product rather than the original. We adjusted the language settings for the string to Italian and updated the translations. If you're experiencing a similar issue, we recommend checking that the review translations are linked to the correct product IDs and that the language settings are accurately configured.
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 problem persists, please open a new support ticket.
Problem: If you're using Elementor on your multilingual site and need to translate pages without automatic synchronization or translation warnings when editing, you might find this issue familiar. Solution: We recommend the following steps to manage your translations manually: 1. On the original page, select the
WordPress Editor
option. 2. In the pop-up that appears, choose where you want to use the Editor. It's advisable to select only that post to test initially. 3. Check the
Duplicate
box and click on the
+
sign to add a translation. 4. Click to Duplicate. 5. Click the pencil icon to edit the translation.
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 this does not resolve your issue, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that the delivery time for many translated products was not set and was not copied from the source language. Even after manually setting the delivery time in the translated products, it would not save and remained empty. Additionally, the backend showed the correct translated delivery time, but the frontend displayed the delivery time in the source language. Solution: We identified that the custom field '_default_delivery_time' was set to 'Do not translate'. We recommended setting this field to 'Copy' and then updating the translations. This setting can be found under WPML > Settings > Custom Fields, by clicking on 'Show system fields'. After making this change, the delivery times should display correctly in both the backend and frontend. If the issue persists, we advised the client to provide an exact example of what they were trying to translate.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, do not hesitate to open a new support ticket for further assistance.
