Problem: The client was unable to save settings to designate a content type as not translatable on their multisite installation. The settings page did not allow the settings to save, resulting in no houses being displayed on the page because there were no Spanish versions of the content. Solution: We recommended the client to perform a full backup of their site. After ensuring the backup, we advised deleting all WPML plugins and then reinstalling them. This approach was necessary because there were many missing WPML files, which likely caused the issue with settings not being saved. Reinstalling the plugins resolved not only the initial problem but also fixed several other issues that the client had not yet reported.
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. Should these steps not provide a resolution, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to translate the JetPopup which includes a button and a tab widget. Although you have translated everything in the JetPopup post type, the English version of the popup does not display correctly. Solution: We have resolved this issue in the latest release of the JetPopup plugin. Please update to JetPopup version 2.0.7 to fix the problem with the English text not displaying properly.
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 you still need assistance, please open a new support ticket at our support forum.
Problem: You are trying to manage media files on your site after using WPML for translation and have noticed that the translated media files have become quite large. Solution: If you're experiencing issues with large media files after translation, it's important to understand that WPML Media Translation does not actually duplicate image files on your server. Instead, it creates new entries in the database for translated image captions, titles, meta text, and other details, all linked to the original image file. The original file remains stored only once on your installation. Therefore, if you delete entries from the media library, you're only removing these associated records, not the actual image files.
If this solution does not resolve your issue or seems irrelevant due to it 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 are using the Flatsome theme and WPML String Translation plugin. On the WooCommerce product page, after updating the content in the 'HTML before Add To Cart button' section in the original language (Polish), the previous content is still displayed in Polish, while the updated and translated string appears correctly in all other languages. Solution: We recommend going to WPML > Support > Troubleshooting. Click the Show custom MO Files Pre-generation dialog box button and then click the generate option. This should fix the problem and is only needed once. Please ensure you do not touch other buttons on that troubleshooting page unless you have a complete backup of your website.
If this solution does not resolve your issue or seems outdated, 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. We highly recommend opening a new support ticket if the problem persists. You can do so at WPML support forum.
Problem: If you're experiencing an error message '[Unproccesable_entity] The requested action could not be performed, semantically incorrect, or failed business validation' when attempting to purchase via PayPal on your website, and the issue stops when deactivating WooCommerce Multilingual & Multicurrencies, this might be due to a known issue. Solution: We recommend downgrading the PayPal plugin to version 2.9.0 as a temporary fix. This is a known issue related to currency handling in WooCommerce with PayPal. For more details, you can check the documentation here: https://wpml.org/errata/woocommerce-paypal-payments-error-cannot_mix_currencies/
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 are inquiring why WPML was using different records and how to configure the plugin so that people in Germany are automatically directed to the German version of your website. Solution: We currently do not have an option to automatically direct users based on their geographic location. However, you can use the browser language redirect feature to direct users with a German browser language to the German version of your site. Please be aware that using this feature might affect how Google indexes your site. For more details on setting this up and its implications, please visit the following links:
If this solution does not apply to your case, or if it 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 WPML support forum.
Problem: The client changed the theme configuration, including headers and homepage layout, and encountered issues with WPML translating the wrong language for headers and product descriptions. Solution: 1. Navigate to WPML > String translation. 2. Search for [theme_mods_wolmart-child] and delete all related string options that mention the header. 3. Go to the bottom of the same page and click on Translate texts in admin screens. 4. Search for your default language header post ID (46333). 5. Click to add it for translation and go back. 6. Select those strings and change their default language to Polish. 7. Translate and add the translated header Post ID 4633. For more detailed guidance, refer to the documentation on how to translate theme options.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client wants to change the language selector on their site from displaying a country flag to showing a globe icon, but they couldn't find relevant documentation. Solution: We recommend custom coding to achieve this change as it falls outside the standard support scope. For guidance, please refer to a similar case discussed in our forums: https://wpml.org/forums/topic/i-want-to-add-language-switcher-to-the-header-with-an-icon/. If you are not familiar with coding, we suggest hiring a front-end developer or a WPML contractor, which you can find here: https://wpml.org/contractors/.
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.
Problem: The client faced two issues with WPForms translations: 1. A specific sentence in the form locker was not appearing for translation. 2. A field value translated in the form preview reverted to English in the email notifications.
Solution: For the first issue, we suggested checking the WPML documentation on translating WPForms locker addon messages and making adjustments to the
wpml-config.xml
file. After updating the file, the missing string appeared, and the client was able to translate it into various languages. For the second issue, after re-editing the string with no success initially, adjustments were made to the
wpml-config.xml
file, which resolved the problem. The client confirmed that the translation was successful and planned final testing.
If you're experiencing similar issues, we recommend trying the steps mentioned above. However, if these solutions do not resolve your problem, or if they seem outdated, please visit our known issues page, verify you have the latest versions of themes and plugins, and consider opening a new support ticket for personalized assistance. You can do so here: WPML support forum.
Problem: If you're experiencing issues where field values disappear after setting a custom post type (CPT) to publish flexible content, it might be due to the translation settings of your ACF field groups.
Solution: We recommend checking the translation settings of your ACF field groups in WPML. Specifically, ensure that the 'acf-field-group' is set to 'Not Translatable' in WPML -> Settings -> Post Types Translation. Here's a step-by-step approach to resolve the issue: 1. Delete all language translations of the field group(s). 2. Set 'acf-field-group' to not translatable. 3. Add the field group in the default language (English, in this case). 4. Test these changes on a staging/test site after taking a full backup. Additionally, if you want to maintain the current settings, follow this workflow for adding posts: - Add the post first in German. - Then add the translation to another language (e.g., Slovak). - If adding another translation (e.g., Polish), first edit the post in German, then add the translation. Repeat these steps for other translations. For further guidance, please check the recommended custom fields translation preferences for ACF and WPML.
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 is trying to translate the title of a Toggle Block using the Getwid plugin on their site, but the translated title is not displaying on the front-end; instead, the original language title is shown. Solution: We recommend the following steps to address the issue: 1. Use the workaround suggested by the Getwid plugin developers. This involves manually editing the translated version of your page using Gutenberg. Change the title for your language directly in the Gutenberg editor for the translated page version. 2. If you are unable to resolve the issue using the above method, it may be due to a compatibility issue between the Getwid plugin and WPML. In such cases, we suggest contacting the support team of the Getwid plugin for further assistance.
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 with us for further assistance.
Problem: You are trying to set different logos for each language on your website using WPML, but the 'Save media translation' button is not working when you attempt to set the French logo. Solution: If you're experiencing this issue, we recommend the following steps: 1. Understand that the logo is sourced from a theme options page, which is treated as 'text in admin screens'. 2. Navigate to 'WPML > String Translation' and click on 'Translate texts in admin screens' at the bottom left. 3. On the next page, search for 'logo'. 4. Select the option [qode_options_proya]logo_image and click 'Add to String Translation'. 5. Return to the String Translation page to translate it. Note: If your theme uses variations like light, dark, or sticky logos, repeat this process for each variation.
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: The client updated their website with a full rebranding and content refresh, using WPML for automatic translation. However, the automatic translation service was pulling old content and charging for translating content that no longer exists on the site. Solution: We recommended checking WPML > Translation Management and filtering by the template post type, then sending the 'service' for translation to see the updated text. For the issue of old text still appearing, we suggested editing the original English page, checking the page ID, and then going to WPML -> Packages to delete the package of the page. After making a minor change (like adding an empty space) and saving, the updated content should appear correctly in translations. Additionally, to maintain the titles for translations, we advised going to WPML → Settings, selecting 'Copy slug from original language', making a small change to the main language page, and then editing and saving the translation.
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 experiencing issues with the WPML plugin on your site, specifically with custom pages in your child theme folder. The strings on these pages are not getting translated, and the CSS breaks after switching languages. Additionally, the store page does not appear in the Italian version. Solution: 1. We found that deleting the translation of the (wp-cli) string resolved the issue with the Italian pages not opening correctly. Please verify if the Italian pages now open as expected. 2. For the CSS issue, it appears that custom CSS was added for the English homepage using its ID, but the translated homepage ID was not included. Ensure to include the ID for the translated homepage in your custom CSS. 3. Ensure that you have installed all necessary plugins for full functionality. Your site is missing WPML SEO, WooCommerce Multilingual, and ACF Multilingual. You can download the latest versions of these plugins from here.
If this solution does not resolve your issues 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 issues persist, please open a new support ticket.
Problem: The client is using WPML and wants to tag SEO content in the exported files for translation, either as additional metadata or specifically for SEO. The exported files for translation only have a trans_unit for all content, and the client cannot identify SEO content separately. They inquired about configuring WPML to tag SEO content in the exported translation files and whether additional plugins could be used.
Solution: We advised the client that for SEO data to be translatable, they need to use compatible SEO plugins along with our addon plugin, WPML SEO. Once these are in place, SEO data/fields added to the page will be available for translation when translating the page. General SEO strings and other related content can be translated via WPML String Translation. We provided a documentation link for further guidance on using WordPress SEO with WPML: https://wpml.org/documentation/plugins-compatibility/using-wordpress-seo-with-wpml/.
If this solution does not fully address your issue, or if it seems 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
