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.
The client is experiencing issues with inaccurate translations in a multilingual donation form, particularly in Chinese (Simplified and Traditional). The form supports English, Chinese, and French, but the translations for Chinese are not functioning correctly except for a few fields.
Solution:
We have identified that it is not possible to translate Give Donations forms like normal posts and pages using the WPML Translation Editor due to a compatibility issue. The Give WP team is also aware of this. To address this, you should:
1) Ensure you have the latest versions of WPML, Elementor, and Give WP installed. 2) Create a separate donation form for each language, specifically for Chinese Simplified or Traditional. 3) Test the new form by creating a simple page in the desired Chinese language and adding the form using the shortcode:
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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: You are using the 'Translate Independently' option for pages on your WordPress site and managing components with ACF Flexible Content. After exporting and importing XLIFF files for translation, you notice that updates to the layout in the English version cause unintended changes and removal of content in the French version, despite the pages being set to 'Translate Independently'. Solution: We have identified that this issue affects both the standard WordPress editor and WPML translation editors. Currently, there is no direct workaround when using the site editor. However, we recommend adjusting the field group translation settings for fields like repeaters. You should set these fields to 'Copy Once' or 'Don't Translate'. When you make changes in one language, you will need to manually apply the same edits to the corresponding posts in other language versions.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If necessary, we highly recommend opening a new support ticket for further assistance. You can do so at the WPML support forum.
Problem: If you're experiencing 404 errors with resumes when the Tax Exception plugin for WooCommerce is enabled, and the errors disappear when the plugin is disabled. Solution: We recommend trying to switch the language settings and then adjusting the permalink settings in your WordPress dashboard. After making these changes, save the settings again. This approach helped resolve similar issues in our tests, even with the Tax Exception plugin activated.
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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: You translated a page using WPML and noticed that the translation appears incomplete as indicated by the gear icon, even after marking it as 'complete'. Additionally, the German translation displayed is different from what was expected. Solution: We recommend deleting the translated page since it is technically just a normal WordPress page linked to the original through the 'trid' field. To do this, open the translated page via the language switcher in the top admin bar, delete the page, and empty the trash. This action should make the '+' button reappear for you to add a new translation. However, for a more thorough solution, we suggest deleting both the original and the translated pages and creating them anew. This ensures that no faulty data from the original is carried over to the new translation.
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 open a new support ticket.
Problem: The client created pricing forms using the WooCommerce plugin and AcoWebs WooCommerce Custom Product Addons plugin. The forms function correctly in the first language, but issues arise with displaying or hiding fields using the Global Attribute in other languages. Solution: We noticed that the missing fields do not have the same settings among languages in the conditional tab. We recommend checking the settings in each language to ensure consistency. Unfortunately, the plugin documentation does not mention the recommended method for translating the conditional tab, and the field in the translated add-on is greyed out, making it unchangeable. We advise contacting the plugin's support team to inquire about the custom field name, which will allow you to set it to either copy once or translate and change it to the translated version. For further guidance, you can refer to the plugin documentation here: Acowebs Plugin Documentation.
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. Should you need further assistance, please open a new support ticket at WPML Support Forum.
Problem: The client is experiencing a 404 error or a 'too many redirects' error when trying to access translated events on a website using WPML and WP Event Manager. Solution: 1. We recommend testing the website in a staging environment with only the WPML and WP Event Manager plugins activated to isolate the issue. 2. Ensure that the WPML plugin and add-ons are updated to the latest version, currently 4.6.15, to benefit from the latest bug fixes and improvements. Update instructions can be found at http://wpml.org/faq/install-wpml/. 3. Check if there are any custom redirections set that might be changing the URL structure, as this could be causing the redirect issues.
If these steps do not resolve the issue 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to translate a multi-page form from French into German using GravityForms and WPML, but some texts remain in French despite using the string translator and advanced translator. Solution: If you're experiencing this issue, we recommend saving the form again in GravityForms. After saving, the missing translation strings should appear in the advanced translation interface, allowing you to complete the translation process.
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 problem persists, please open a new support ticket at WPML support forum 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
