Problem: The client is using WPML to create a Spanish version of their website and has encountered an issue where Spanish Memberships include English subscriptions. This prevents Spanish speakers from accessing content they purchased because the memberships do not recognize the Spanish subscriptions. Solution: We confirmed that the WooCommerce Memberships plugin is compatible with WPML. However, there are known issues that might be causing the problem described. We recommend checking the specific errata related to WooCommerce Memberships not assigning membership when purchasing a product in a secondary language. Here is the link to the errata: https://wpml.org/errata/woocommerce-memberships-does-not-assign-membership-when-purchasing-a-product-in-a-secondary-language/ Applying the suggested workaround from this errata may resolve the issue.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to register their site with WPML due to a site key not matching, despite previous successful registrations. Solution: We recommend checking if different URLs are being used for the home and main URLs. You should generate a WPML key for each URL version, as this might resolve the issue. If you're experiencing this, you can find a helpful screenshot in our support forum or directly view the image here.
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 is experiencing an issue where a section of their website is not displaying in English as expected, despite previously showing correctly. This problem is occurring on the page: https://www.rezisieriai.lt/en/about/. Additionally, there is a separate issue where a translated logo is not showing correctly on the same page. Solution: We have identified that the issue with the section not translating might be related to a bug in BeTheme, not WPML, as the problem persists even when WPML is disabled. We recommend checking with BeTheme support to resolve this issue in the default language first. If the problem continues to occur only in the translated version after fixing it with BeTheme, please contact us again. For the issue with the translated logo not displaying, please refer to the existing support ticket here: https://wpml.org/forums/topic/translated-logo-stopped-showing-in-1-page/
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 at WPML support forum.
Problem: You are experiencing an issue where many string translations have disappeared from your site. This problem occurred without any updates being made initially, but persisted even after updating and scanning for new translations. Solution: First, ensure that you update WooCommerce and WPML to the latest versions as a recent issue with WordPress 6.7 could be affecting your translations. You can learn more about this specific issue here: WPML Errata. Next, go to WPML > Theme and plugins localization and select the option to 'Automatically load the theme's .mo file using
load_textdomain
'. This adjustment has resolved the issue for other clients experiencing similar problems.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.
Problem: You are trying to display a translation for a global section on your website, but it is still showing in the original language. The translation for the global section is not appearing as expected, displaying in Lithuanian instead of English. Solution: 1. Ensure that you go to BeTheme → Theme Options → Global → Advanced and set the value of the Muffin Builder data storage to
"Serialized | Readable format"
, which is required by some plugins. 2. If you are using Templates, make sure that they are translated. 3. Set the following custom fields to "copy": - mfn_footer_template - mfn_header_template 4. Edit the original footer, save it, and apply the translation again. For more detailed guidance on translating custom fields, please visit: Translating Custom Fields Documentation
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 unable to translate widget titles on their website using WPML, despite having encountered and resolved a similar issue previously. Solution: 1) In WPML String Translation, scroll to the bottom and click on the Translate texts in admin screens link. Search for the widget title, add it for translation, and then translate it. 2) Alternatively, consider adding two widgets, one for each language (GR and EN), with their respective translated titles. This method is detailed in our documentation: Translating Widgets.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your case, 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 at WPML Support Forum.
Problem: The client is facing two issues: unable to use 60000 credits for automatic translation and encountering an error when switching from Greek to English related to the function
_load_textdomain_just_in_time
. The error indicates that the translation loading was triggered too early. Solution: 1) The error related to
_load_textdomain_just_in_time
is a known issue in WordPress and not specific to WPML. It can occur even if WPML is disabled. For more details, please visit WPML Errata. 2) To address the issue with using credits for automatic translation: - Navigate to WPML > Support > Troubleshooting. - Click on "Synchronize local job ids with ATE jobs" and "Synchronize translators and translation managers with ATE". - Resend the page for translation from WPML > Translation Management. - Go to WPML > Translation, take and translate the job.
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 WPML 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 at WPML Support Forum.
Problem: You are experiencing an issue where translated strings only display when the 'Look for strings while pages are rendered' option is enabled, following a recent WordPress update. Solution: If this issue occurred after updating to WordPress 6.7, we recommend you check the following documentation on missing translations on the front end: https://wpml.org/errata/missing-translations-on-front-end/. Downgrading WordPress to the prior version might be an option as workaround. If this does not apply to your case, please contact us for further investigation.
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, do not hesitate to open a new support ticket for personalized assistance.
Problem: The client is using WPML Multilingual CMS and Breadcrumb NavXT on their website. They reported that the 'Project Sectors' breadcrumb menu does not translate on project detail pages, and WPML String Translation does not detect the missing string. Solution: 1. We identified that the site has a custom option to select a page as a portfolio root, which required the translation of the page ID. 2. To resolve this, we translated the page ID in WPML > String Translation by finding both the original and Arabic page IDs. Then, we added the ID of the Arabic page as a translation of the original ID. 3. To find the page ID, follow this guide: https://wpdatatables.com/how-to-find-page-id-in-wordpress/ 4. Use the text search in WPML > String Translation to search for the ID. For more details on finding IDs that don't appear on the String Translation page, visit: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/#translate-admin-and-settings-strings 5. Additionally, in WPML > String Translation, click 'Translate texts in admin screen' at the bottom of the page and search for option strings like 'root' or 'page' to find such IDs.
If this solution does not resolve your issue or 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 visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client wants to change the URL structure to include the category slug, but only for the Norwegian language on their multilingual site. They are using WPML and currently have a different structure for Danish. Solution: We have determined that it is not possible to have different URL structures for each language when using WPML, as the content needs to be linked properly across languages. Additionally, attempting to force this change through code modifications is likely to cause issues and is not recommended.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we encourage you to open 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 visit our support forum at https://wpml.org/forums/.
Problem: The client is experiencing duplicated registration fields on the leads page in both English and Swedish after activating automatic translations. This issue persists even after deactivating and reactivating the WPML plugin. Solution: We investigated the issue and found that the duplication persists even after deactivating the WPML plugin. This suggests that the problem might not be directly related to WPML. We recommend checking the settings or configurations of other plugins that might be interacting with WPML, particularly the b2b king plugin, which was mentioned in relation to other issues like pricing discrepancies. If the problem continues, please visit our support forum and open a new ticket for further assistance. 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.
Problem: The client was unable to remove credits from their staging account at hostfullystag.wpengine.com and wanted to transfer them to a production account. They observed a discrepancy in credit amounts between the staging website and the WPML account. Solution: We moved the credits back to the client's main account to enable proper assignment to the desired production website. If you're experiencing a similar issue, we recommend checking your account for the updated credit balance.
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: If you're experiencing issues with missing language folders in the URLs for certain subcategories on your multilingual online store, such as missing /ru/ for Russian and /es/ for Spanish in subcategory URLs. Solution: We recommend first ensuring that you have a complete backup of your site. Then, try disabling all non-WPML plugins and switch to one of the default themes to check if the issue persists. This step helps identify if there's a conflict with other plugins or themes. Additionally, navigate to Settings -> Permalinks in your WordPress dashboard and save the permalink settings again, as this can sometimes resolve URL issues.
If these steps do not resolve the problem, or if the solution provided here becomes outdated or does not apply 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. Should the issue persist, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: The client is using WPML with WPForms to translate forms and integrate with ActiveCampaign. They need to receive the original English values of each field after form submission, regardless of the language the form is submitted in. However, they are encountering issues where translated values are sent instead of the original English values, causing problems with ActiveCampaign and other tools. Solution: We suggested checking if the input values that need to remain in English are appearing in the WPML Translation Editor when translating the form. If not, these values might be registered in WPML > String Translation. We recommended translating all option values in WPML > String Translation, and if the client wishes to keep the values the same in both languages, they should copy the original values. This approach should ensure that the original English values are sent to ActiveCampaign and other applications.
If this solution does not resolve the issue, we advised the client to test this setup and contact us for further assistance. We also recommended checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that they have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: After activating WPML and adding the Ukrainian language, the client experiences a 500 error on the frontend, accompanied by server logs indicating 'too many redirects'. Solution: We recommend reading the following article and following the instructions provided: Why is .htaccess getting overwritten with the language folder on my WPML website?
If this solution does not resolve your issue or seems irrelevant due to being 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 problem persists, please open a new support ticket with us for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
