Problem: The client created a variable product in WooCommerce and needs to translate the name of the default variation. After translating, the product appears empty in the frontend. Solution: 1. Ensure the WooCommerce Multilingual & Multi Currency plugin is installed and activated. You can download it from here. 2. Edit the variable product in the default language ensuring that the "WPML Translation Editor" is enabled. 3. Translate the secondary language product using the WPML Translation Editor. For detailed steps, refer to this documentation. 4. If the variation still does not show in the frontend, follow these troubleshooting steps: - Clear the cache in WPML. - Synchronize posts taxonomies. - Remove ghost entries from the translation tables. - More steps can be found in the WPML Support Troubleshooting page. 5. Consider creating global attributes and translate them either during the product translation or via WooCommerce >> WooCommerce Multilingual & Multicurrency > Attributes tab.
If these steps do not resolve the issue, 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 the problem persists, please open a new support ticket.
Problem: The client was unable to open the Elementor editor for a translated page/template, resulting in a 403 Forbidden error and an uncaught TypeError. Solution: The client said he had found a folder named /he/ on the server. Removing this folder solved the problem. If this solution is 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 issues persist, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the currency switcher does not affect the currencies displayed in sidebar widgets on the homepage, despite working correctly on product and category pages. Solution: We recommend deleting the
object-cache
and
advanced-cache
files from the wp-content folder on your staging site. This approach resolved a similar issue on our local test site, suggesting that cached data might be preventing the currency switcher from updating the sidebar widgets correctly.
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. Additionally, please feel free to open a new support ticket with us for further assistance at WPML support forum.
Problem: In the Spanish version of a multilingual webshop, the client is unable to set display conditions in Elementor for the Spanish category 'JUEGO TABLAS'. Despite the taxonomy hierarchy being synchronized, only Slovenian categories are available for selection. Solution: We discovered that the issue was due to the use of an outdated 'Products' widget in Elementor, which was deprecated since version 4.1.3. We recommended switching to the 'Products Grid' widget. After making this change, the client should verify if the translated archive displays correctly by checking the front end.
If this solution does not resolve the issue or seems outdated, 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 problems persist, please open a new support ticket.
Problem: You are experiencing errors after updating WPML and WPML String Translation, including 'open_basedir restriction in effect' warnings and 'Cannot modify header information - headers already sent'. The system attempts to access an incorrect path, leading to these issues. Solution: We recommend checking the specific errata page related to this issue on the WPML site. Please visit https://wpml.org/errata/php-warning-file_exists-open_basedir-restriction-in-effect-warning-possible-with-current-string-translation/ for a detailed explanation and potential fixes.
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 with us for further assistance.
Problem: The client is trying to correct some links in the footer of their website after translating the footer. They edited these links in the original Greek language, but the changes did not reflect in the English translation. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Make a small change in the footer to trigger the need for translation. 2. Navigate to WordPress Dashboard > WPML > Translation Management. 3. Send the footer for translation and select yourself as the translator. 4. Go to WordPress Dashboard > WPML > Translations. 5. Click the Translate button next to the footer in the table. 6. You will see the Advanced Translation Editor, which shows all the content of the original language on the left and the translated content on the right. 7. Try to find the links there and edit the translation as needed. If you cannot find it, use the search bar at the top to search for the link.
Please note that this solution might be irrelevant if 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where your credit balance is not updating after making a payment on your WPML plugin, it might be due to the type of credit system used on your site. Solution: We recommend checking if your site uses a pay-as-you-go credits model. In this model, the charges for credits already used are applied in the following month. Therefore, any payment you make will be for the credits that have already been consumed up to the date of the payment. For instance, if you made a payment, it would cover all the credits used until a specific future date (e.g., 2024-12-05), and your used credits would then reset to 0. This means that the payment will not immediately reflect as an increase in your current credit balance on the dashboard since it's intended to clear the consumed credits.
If this explanation does not seem to apply to your situation, or if you find the information possibly outdated or not relevant 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, if you need further assistance, please do not hesitate to open a new support ticket with us at WPML support forum.
Problem: The client is experiencing two main issues with a translated contact form. First, the dropdown options in the form are not fully displayed in the translated version. Second, the link to the privacy policy page is not correctly pointing to the translated version of the page. Solution: 1. For the dropdown options not displaying correctly, ensure that the options are correctly added and formatted in both the default and translated forms. You might need to update the default form to match the format shown in this demo, and then resend the form for translation. 2. For the incorrect privacy policy link, the link should be translated through the Translation Editor. In the Translation Editor, find the paragraph where the link is added, unlock the field with the lock icon, update it with the translated page link, and save the translation. If these steps do not resolve the issues or if the solution 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 the problem persists, please open a new support ticket.
Problem: The client has migrated their site multiple times and is facing issues with WPML's automatic translation, specifically a message stating insufficient credits despite having them. Solution: If you're experiencing issues with your WPML credits after migrating your site, we recommend the following steps: 1. Log in to your WPML.org account and go to the Sites page. 2. Delete the site key for your site by pressing the little trash icon. This action will return the assigned credits to your WPML.org account. More details can be found in this documentation: Why credits may be missing and how to fix it 3. Log in to your site and navigate to Plugins >> Add new Plugin > Commercial tab and click the 'Unregister WPML from this site' link if it exists. 4. Click the 'Register WPML' link. 5. Click the 'Get a key for this site' link. It will generate a new Key for your site, and you can also assign the credits using that popup. 6. Copy the key and paste it back into the input box and press the Register button.
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.
Problem: You are adding new tours to your website and translating them using WPML. Although the translations are visible in the WordPress admin panel, they do not appear on the site. On the Spanish page, some tours are listed in English, and clicking on them results in a 'The page is not found' error. Solution: We recommend following these steps to resolve the issue: 1. Check the documentation on .htaccess issues with WPML. 2. Disable all non-WPML plugins and switch to one of the default themes to see if the issue still persists. 3. Ensure you create a backup of your site (both files and the database) before making any updates or changes.
If these steps do not resolve your 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.
Problem: You are trying to translate WooCommerce products and pages, but it results in duplicates and re-assigns the default pages. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to Dashboard->Pages. 2. Quick edit the page without the translations and set the slug to something else and set it as draft. 3. Quick edit the correct page and set the slug to the correct one. 4. Open the correct page and try to make some changes to see if the pages duplicate again.
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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing an issue with Gravity Forms Multilingual version 1.8.0 and above, where the 'gform_review_page' filter did not display the review page as expected, only showing the submit button directly.
Solution: We recommended trying the solution from this erratum.
Please note that this solution might be outdated or not applicable to your specific case. If the issue 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: You are unable to update the WPML plugins and receive an ERROR message. This issue typically occurs when the site URL and the registered site URL do not match (e.g., with or without 'www'). Solution: 1. Log in to your WPML.org account and navigate to the Sites page. 2. Delete the existing site key. 3. Log in to your WordPress site, go to Dashboard >> Plugins >> Add new plugin > Commercial tab and click the Unregister WPML from this site link if it exists. 4. Click the Register WPML link. 5. Click the Get a key for this site link and follow the instructions to generate a new key. 6. Copy the new key, paste it into the input box on your site, and press the Register button. 7. Take a backup of your site. 8. Attempt to update the WPML plugins again.
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 the 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.
The client experienced issues with their website after using WPML to translate it. The translated webpages displayed without images, texts were overlapping, and the language switcher widget was not displaying properly. The root cause was identified as theme design issues exacerbated by the addition of the language switcher and longer text in menu translations.
Solution:
We provided a CSS fix to address the layout issues caused by the language switcher and menu translations. The client should add the following CSS in WPML->Languages->Language URL options->Additional CSS:
For the missing images, specifically the logo, the client should go to the Avada options, switch to the secondary language, and add the logo translations. Selecting a smaller size for the logo may be necessary if it appears too large.
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 problems persist, please open a new support ticket.
The client is unable to open or edit a Spanish page on their site hosted on Pantheon after implementing a fix for a file writing issue. They encounter a PHP fatal error related to 'array_key_exists()' and 'Elementor\Core\Schemes\Color' class not found, along with JavaScript errors in the browser.
Solution:
1. We recommended following the steps outlined in the WPML forum post to address the Elementor integration issue. For more details, visit WPML forum post.
2. We suggested going to WPML->Languages->Hidden Languages to unhide the language and check if the issue persists.
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 continues, 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
