Problem: The client is experiencing an error with the WPML String Translation plugin during the WooCommerce checkout process. The error persists even when the WPML Multilingual plugin is activated. Solution: We recommend ensuring that WooCommerce Multilingual is activated, as it is necessary for WooCommerce to function correctly with WPML. For guidance on activating and configuring this, please refer to our documentation: WooCommerce Multilingual setup guide. If the problem continues, it might be due to a missing file or incorrect setup. Checking the server for missing files or configuration issues that might be causing the error can resolve the issue. If these steps do not resolve the problem, or if the information provided here is outdated or does not directly address your specific situation, 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 issues with translating nested Custom Post Types (CPTs) such as 'quote' or 'contact-person' within a parent CPT post using ACF Pro and WPML. Even though these nested CPTs are translated, they do not always display in the translated version of the parent CPT. Solution: We recommended adding specific HTML to the Gutenberg block code to make the nested CPTs translatable. Here is the code that needs to be added:
<!-- wp:acf/contact {"name":"acf/contact","data":{"block_margin":"margin_default","_block_margin":"field_632ad768f82b2","block_margin2":"","_block_margin2":"field_66226c6c5c17f","composition":"select-contactperson","_composition":"field_662672b951a80","select-contactperson":2342,"_select-contactperson":"field_663cbb0667643"},"mode":"auto"} /--><br /><div class="abcd">here is the block content</div><br /><!-- end block settings wp:acf/contact -->
If this solution does not resolve the 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 our support forum.
Problem: The client wants to restart the translation of their website without translating the slugs. They are also concerned about whether they will be charged again for the translation and how to handle already translated slugs. Solution: To restart the translation process without affecting the slugs, we recommend performing a WPML reset. This can be done by following the steps outlined here: WPML Reset Guide. For managing slug translations, you can prevent slugs from being translated by following the guidance in this forum post: Stop Slug Translation. Additionally, to edit an already translated slug, use the quick edit options as detailed here: Change WordPress Page Slug and here for taxonomies: Change WordPress Tag and Category Slug.
If these solutions do not apply to your case, or if they seem outdated, please check the related known issues at WPML Known Issues. We also recommend confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, feel free to open a new support ticket at WPML Support Forum.
Problem: The client is experiencing issues where the English and Chinese versions of their listings are not connected, and images are not being copied to the Chinese version after using WPML All Import. Solution: We recommend using the same unique identifier for both the English and Chinese versions during the import process. This identifier should be set in both the import template and settings for each language. Here are the steps to follow: 1. Ensure that the unique identifier is correctly configured in your WPML All Import settings for both languages. More details can be found in the guide on importing multiple languages with WP All Import and WPML. 2. Delete any previously imported listings that were not connected correctly. 3. Re-import the listings for both languages using the new settings.
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 problems persist, please open a new support ticket.
Problem: The client is experiencing issues with translating select options in ACF when used with Gridbuilder and OCF on a multilingual site. Specifically, the select options are not being translated in Gridbuilder's cards, and only the fields that use the select option in OCF are affected. Solution: We recommend the following steps to resolve the issue: 1. Open your theme’s functions.php file. 2. Add the following code:
3. Visit the page with the facets in the original language to register the strings. 4. Go to WPML > String Translation page and translate the strings.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in 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's bilingual website (German and English) displays only the German PDFs on both language versions of a page, despite using the WPML Media Translation tool to add English PDFs. Solution: If you're experiencing this issue, it's likely because the PDF links on your page were created with Elementor. In this case, simply replacing the file in WPML -> Media Translation might not suffice. We recommend translating the PDF links directly within the page using WPML's Advanced Translation Editor. For detailed guidance on how to translate links using this tool, please visit Translating Links with Advanced Translation Editor.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, 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 WPML Support Forum.
Problem: The client is experiencing issues with images in an ACF field only displaying on English posts and not on Spanish posts, despite using the ACF WPML add-on. Solution: We found that the issue was due to the translation settings for the ACF Field Group. It is not recommended to set the translation preference for the 'acf-field-group' post type to Translatable as it creates separate field groups for each language, requiring manual configuration for each. To fix this, we set the ACF Field Group's translation preference to "Not Translatable" and deactivated the translated field group. We then set the translation preference for the `topic_featured_image` and `_topic_featured_image` meta fields to "Copy." After making a minor change and saving it via "Posts > Tag > Quick Edit," the featured image was successfully copied to the translated tag and displayed correctly on the frontend. For more details, please check this Errata.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client needs to use different images in FSE template parts based on the language, specifically for logos that include text in English and French versions. The media translation plugin works for content but not for FSE template parts. Solution: We recommend manually editing the translation of the templates. Here are the steps: 1. Edit your template in the default language. 2. Switch to the desired language using the language switcher in the admin bar. 3. Manually add a different media file for the logo in the template and update. Alternatively, you can: 1. Go to WPML->String Translation. 2. Search for the Logo URL. 3. Translate it by adding the URL to the image you want to use for the different language. However, these methods are workarounds. For a more consistent solution, follow the steps in our documentation on translating sites that use full site editing, which you can find here: Translating sites that use full site editing.
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 needs to translate the /food/ slug to /repas/ for a custom post type in the French version of their website. However, the slug translation is not appearing as expected, and the original slug is still visible in the URL. Solution: If you're experiencing this issue, we recommend following the guide to translate URL slugs for custom post types. You can find the guide here: Translate URL Slugs for Custom Post Types. If the problem persists after following the guide, please provide us with additional details on how you created the Custom Post Type.
Please note that this solution might be irrelevant if it's 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 continues, please open a new support ticket with us for further assistance at WPML Support Forum.
Problem: The client is experiencing an issue where the WooCommerce Gift Cards plugin sends notification emails in Greek regardless of the site language from which the gift card was purchased. Previously, a snippet was used to solve this, but it now causes a fatal error. Solution: We recommended updating the functions.php file with the following code:
We asked the client to verify if the last email is translated correctly by checking their WPML plugin log.
Please note that this solution might be outdated or not applicable to your specific case. If this solution does not resolve your issue, we highly recommend checking 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: The client was experiencing an issue where translations from Italian to Albanian were stuck in 'in progress' status, despite the translation progress bar showing 100%. This problem did not occur when translating from Italian to English. Solution: The client resolved the issue by taking the following steps: 1. Removed the WPB Popup for CF7 plugin, which was identified as the main cause of the problem, with alternative plugins. 2. Increased all the server limits in the php.ini file.
If you're experiencing similar issues, we recommend trying the above steps. However, if this solution does not apply to your case, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you 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 for further assistance.
Problem: You are experiencing an issue where the layout of the header on the translated page is incorrect, making the menu invisible, while the original Dutch page layout appears correct. Solution: We recommend deleting the problematic English page and re-translating the 'About Us' page from the original Dutch version. This approach resolved the issue in a similar case by removing the corrupted page that was causing the layout problems.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your current setup, 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 is experiencing issues with certain ACF fields not appearing in the translation editor or XLIFF exports, despite being configured with specific WPML custom field preferences. This problem is occurring in their staging environment. Solution: We recommended checking the ACF field configuration and ensuring that the 'Same fields across languages' setting is enabled in WPML. After adjusting this setting, the client should: 1. Go to WPML -> Translation Management. 2. Assign the post for translation to themselves. 3. Check if the ACF field content now appears in the XLIFF file. If the issue persists or the solution seems outdated or irrelevant, we highly recommend opening a new support ticket. Additionally, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client has installed the WPML CMS and string management plugins on a multisite and is facing issues with missing Translation Management pages. Additionally, attempting to translate a page results in the creation of a new blank page. Solution: We suspect that the issue might be due to using a "Multilingual Blog" subscription sitekey. We recommend generating a new sitekey from your account dashboard at https://wpml.org/account/sites/. After generating the new sitekey, unregister WPML from your site by visiting https://whisperingpin5.wpenginepowered.com/wp-admin/network/plugin-install.php?tab=commercial and clicking on the 'Unregister WPML from this site' link on the top left corner. Then, register the site with your new sitekey.
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 further assistance is needed, 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