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.
Problem: The client was having difficulty manually translating certain items in the WooCommerce checkout process and automated emails, as well as other elements like 'read more' under blog excerpts, after setting up a custom language based on Spanish for Papiamento. Solution: We recommended setting the default locale to Spanish (es_ES) to leverage existing Spanish translations and then fine-tuning them in WPML. Here are the steps we suggested: 1. Go to WPML → Languages → Edit Languages 2. Set es_ES as the Default Locale for Papiamento 3. Go to WPML → Theme and Plugins Localization and scan WooCommerce and other necessary themes/plugins 4. Translate the strings in WPML → String Translation If changing the default locale is not preferred, we advised scanning the theme and plugins for strings and then locating them in WPML → String Translation for manual translation. For more details, visit WPML String Translation documentation.
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 for further assistance.
Problem: You enabled automatic translation with TPC and need to review translations marked as "Draft - Pending review" in the translation queue. However, when you attempt to review, the translations do not appear. Solution: First, ensure that your server meets the minimum requirements for running WPML, which can be found here: https://wpml.org/home/minimum-requirements/. Increase the WordPress memory limit to at least 256 MB by adding the following code to your wp-config.php file:
define('WP_MEMORY_LIMIT', '256M');
Place this code just before the comment:
// That's all, stop editing! Happy blogging.
If your hosting provider restricts these settings, contact them to make the necessary changes. After adjusting the memory limit, re-enable LiteSpeed and try accessing a review again. If the problem persists, it might be due to other issues not covered by this solution. 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 these steps do not resolve the issue, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to update plugins and experienced issues with the 'scan plugin strings' button being unclickable. They needed to translate the cookie button text in the banner and faced toggling issues in string translation options from the homepage. Additionally, there was confusion about the account seeming expired despite having lifetime access. Solution: We recommended checking for a plugin conflict by: 1. Creating a backup of the website. 2. Switching to the default theme, 'TwentyTwenty', via 'WordPress Dashboard > Appearance > Themes'. 3. Deactivating all plugins except for WPML Multilingual CMS and WPML String Translation. 4. Going to 'WordPress Dashboard > Plugins > Add new > Commercial (tab)' and clicking the 'Check for Updates' button. 5. Updating WPML and its addons. For more information on automated updates, visit https://wpml.org/faq/install-wpml/#automated-updates. If automatic updates fail, we advised manually updating WPML and its addons by: 1. Ensuring the client is signed into wpml.org. 2. Downloading the latest versions from https://wpml.org/account/downloads/. 3. Installing them manually following the guide at https://wpml.org/faq/updating-wpml-manually/. We also addressed the account issue, confirming there was no effect on the subscription and it remains active.
Please note, 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 need to update your payment method for WPML. Solution: We recommend following the steps outlined in our guide to change your payment method. You can find the guide here: https://wpml.org/purchase/how-to-change-your-payment-method/
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.
Problem: The client needed assistance translating a header and footer created with Elementor/Theme Builder, which were not appearing in the WPML Translation Dashboard.
Solution: 1. We advised the client to check if the Elementor templates were set as translatable in WPML -> Settings -> Post type translation. If not, they were instructed to change the settings to make them translatable. 2. After adjusting the settings, the client was directed to go to WPML -> Translation Dashboard to see if the templates now appeared for translation. 3. For untranslated strings, such as menu items, the client was guided to go to the specific URL (https://dourodiscoveryandtours.com/wp-admin/nav-menus.php?action=edit&menu=52) and add translations by clicking on the plus symbols. 4. To ensure styles matched across languages, the client was instructed to paste specific CSS in Appearance -> Customize -> Additional CSS and to flush any cache.
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 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 with language switching on your WordPress site using WPML, where the English header and footer still appear on the Arabic version despite having translated versions, this might be due to the way these elements are assigned in your theme settings. Solution: We recommend checking if the header and footer are assigned via theme options using an Elementor template ID. If so, these need to be translated through WPML's String Translation. Here are the steps to follow: 1. Navigate to WPML → String Translation. 2. Click on 'Not seeing strings you are looking for?' to scan theme options. 3. Find the option where the footer or header template ID is stored. 4. Translate it by adding the ID of the translated (Arabic) template. For more details, visit Translating Theme Options.
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 issues persist, please open a new support ticket.
Problem: The client has created a mobile-only page and added flags using custom code, not related to WPML. They are unable to display a language switcher that shows all languages, as it only displays the current language. Solution: We recommended ensuring that the page is fully translated, as WPML does not display flags for languages that do not have translations. If the page is translated and the issue persists, the client should adjust the settings by navigating to WPML > Languages > Language switcher options > How to handle languages without translation. This adjustment should help in displaying all language options on the mobile page.
If this solution does not resolve the 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: You are trying to move 2,000 credits from your development site to your production site and are encountering issues. Additionally, you are seeing that your production site appears inactive despite being registered. Solution: The 2,000 credits on your development site are complimentary and cannot be transferred to another site. For purchased credits, you can freely move and use them across your WPML account and connected sites. To share credits between your development and production sites, the best approach is to connect both sites under the same organization or move credits within your WPML.org account. For more details on managing automatic translation subscriptions for multiple sites, please visit https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/.
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 assistance, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
