Problem: The client needs to transfer credits between two sites using WPML and is facing difficulties in managing credits after duplicating the website, which leads to confusion about whether it is a copy of the site. Solution: If you're experiencing issues with transferring credits between your WPML sites, we recommend following the steps in our documentation on how to share credits and translations between different domains. You can find the guide here: Automatic Translation Subscription for Multiple Sites. If you're still unsure and need to move credits specifically to your new domain, please contact us directly, and we will assist you with the credits transfer.
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 experiencing issues where the homepage changes unexpectedly and products along with their images disappear when switching to English on your site. Additionally, there are problems with permalinks and site disruptions after attempting to integrate WPML. Solution: First, ensure that your staging site is a complete replica of your live site, including all categories and data. If your staging is incomplete, create a new one or provide a complete copy for further assistance. You can follow the instructions here: https://wpml.org/fr/faq/provide-supporters-copy-site/ Regarding the issue of credits and refunds, please contact our accounts department directly for further inquiries here: https://wpml.org/home/contact-us/contact-form/ To remove a domain from your account, navigate to Account > Sites and click the trash icon.
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: If you're experiencing critical errors when saving widgets with the WPML plugin activated, it might be due to inactive widgets in the Appearance -> Widgets section of your WordPress dashboard. These inactive widgets might be trying to use formerly registered ACF blocks that are no longer available.
Solution: We recommend deactivating the ACFML and String Translation plugins temporarily. After deactivating, try to expand the inactive widgets section and delete these widgets one by one. Once the inactive widgets are removed, you should be able to save the active widgets without encountering any critical errors. Please ensure to take a full backup of your site before making these changes.
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 problems persist, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to display the 'dashicons-admin-home' icon in the primary navigation of their WordPress site across subdirectories. Solution: We identified that the issue was due to dashicons not being loaded on the front-end because the site used different logins, and wp-admin wasn't loaded by default. To resolve this, we recommended loading dashicons on the front-end. You can add the following line to your theme's functions.php file:
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You want to put the translation switcher in a code module in the divibuilder (so you can have the switcher above the menu or in a custom location).
Solution: We recommend using the language switcher shortcode to add the switcher anywhere on your site. For detailed instructions on how to implement this, please visit Adding Language Switchers using PHP and Shortcodes.
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. Should you need further assistance, please do not hesitate to open a new support ticket.
Problem: You are experiencing a fatal error when trying to edit or add a translation in WPML, despite having updated PHP and WP memory limits and contacting your hosting provider to address issues in the wp-option table. Solution: First, ensure that your user profile under Users-> Profile includes an email and a nickname, and make sure to update this information. Next, navigate to WPML-> Translation Management -> Translators tab and verify that your profile is listed as a translator with the correct language pairs.
If this solution does not resolve your issue or seems outdated, we recommend checking for 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:
If you're experiencing an issue where entering http://www.example.com displays the Dutch version instead of the English version, it might be due to improper redirection settings between www and non-www versions of your site.
Solution:
We recommend contacting your hosting provider to check if they can configure the redirection settings properly for both domains. To ensure that the issue is not related to WPML, you can temporarily disable WPML and verify if both domains function correctly without it.
If this solution does not resolve your issue or seems irrelevant because 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the French translations for WooCommerce are not appearing correctly on their site. Despite setting the site to French, many strings remain in English. The client uses a custom Default locale (fr_DZ) which does not match the WooCommerce provided locale (fr_FR). Solution: 1. Change the file name of the translation file. Using the file manager in the WordPress installation, navigate to
/wp-content/languages/plugins
and rename the file
woocommerce-fr_FR.mo
to
woocommerce-fr_DZ.mo
. 2. Alternatively, in WPML -> Strings Translation, search for the field and manually translate it. 3. Adjust the "Default locale" setting in WPML. Go to WPML -> Languages -> Site Languages, click "Edit languages", and change the "Default locale" from fr_DZ to fr_FR, while keeping hreflang as fr_dz. This ensures the correct .mo file is used without affecting the site's front end or SEO.
It is crucial to make a full site backup (files and DB) before proceeding with these steps.
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: You are trying to complete the translation of your forms using WPML, but you are encountering an issue with Font Awesome glyph icons in HTML. Strings with glyph icons are not saved, and the translation is not 100% completed, leaving some English text on translated pages/forms. Solution: 1. Increase the PHP memory limit to at least 512M. You can do this by adding the following code to your
wp-config.php
file just above the line that says '/* That's all, stop editing! Happy blogging. */':
2. Enable the previous version of the Advanced translation editor. Go to the advanced translation editor, click the gear icon on the top right to access settings, enable the 'Previous version' option, provide feedback, and submit to reload the page. 3. Apply the fix for a known issue with Gravity Forms by following the steps outlined here: https://wpml.org/errata/gravity-forms-merge-tags-are-available-for-translation/
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: You are trying to set different permalink structures for posts in Dutch and English using WPML. Specifically, Dutch posts should use the permalink structure: /nieuwsitems/%postname%/, and English posts should use: /newsitems/%postname%/. Despite enabling 'Translate custom post and taxonomy base slugs' in WPML > Settings, setting the post type 'Posts' to Translatable - only show translated items, and configuring slug translations in WPML > String Translation, all posts, regardless of language, use /nieuwsitems/%postname%/ instead of the expected language-specific slugs.
Solution: We have found that WPML does not support translating custom permalink structures. It only supports translating custom slug translation when the custom type is registered. For more details, you can refer to our guide for developers here: Translating Slugs for Custom Post Type Archives.
As a workaround, consider using a Custom Post Type (CPT) instead of standard posts, as this allows for slug translation. Alternatively, you can create a category with the desired slug, assign it to all relevant posts, and update the permalink structure to include the category. This category slug can then be translated. For more guidance, check out these links:
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 WPML Support Forum.
Problem: The client wanted to display a message on the WooCommerce checkout page using 'Flux Checkout for WooCommerce' from Iconic. Although the message was created in German (DE) and translated into Greek (GR) and English (EN), it only displayed in German on the frontend. Solution: We recommended the following steps to ensure the translated messages display correctly: 1- Navigate to
4- Verify the changes on the frontend checkout page.
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: The client is experiencing intermittent 'Internal Server Error' messages when trying to access translated pages on a website with WPML and WCFM installed. The hosting company suggested that the issue might be related to a misconfiguration in the htaccess file. Solution: We recommended the following steps to resolve the issue: 1. Take a backup of the site for safety reasons. 2. Add the following code in the functions.php file of the theme:
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 issue persists, please open a new support ticket at WPML support forum.
Problem: You are using WPML with Elementor to manage a multilingual website and are facing challenges in synchronizing design updates across different language versions. Additionally, you are experiencing issues with the support chat system. Solution: To ensure that design changes made in the English version of your website are reflected in other languages, you should update the translations using the WPML Translation Editor after making any design changes. This step is crucial for syncing the design across different languages. If this does not resolve the issue, we recommend sending us the WPML debugging information for further analysis. You can find more information on how to provide this at https://wpml.org/faq/provide-debug-information-faster-support/.
Please note that this solution might be outdated or not applicable to your specific case. If the problem 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 you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client wants to translate author pages on their website using WPML. Solution: We recommend enabling the option to translate user roles with WPML String Translation. Here's how you can do it: 1. Go to WPML > String Translation. 2. Enable the translation for the user role you need, for example, "Editor". 3. Once enabled, all strings associated with users having this role will be translatable at WPML > String Translation. Additionally, ensure that the author has translated posts. If no posts by the author are translated, the author's archive may not be available in the second language.
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.
The client reported an issue where resumes are duplicated like jobs in the WP Job Manager Resumes plugin, and when deleted from the frontend, only the current resume is deleted, not the copies.
Solution:
We recommend following these steps after ensuring you have a full site backup:
Please note that this workaround will delete translations, irrespective of the "When deleting a post, delete translations as well" option.
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 the problem persists, please open a new support ticket at WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
