Problem: The client needed to translate the submit button on their French version of the website but was seeing 'Submit' instead of 'Soumettre'. The issue persisted even after attempting initial solutions. Solution: We recommended the client to try the following steps: 1. Go to the site's backend, switch to French from the top black bar, navigate to Pages, find the relevant page, hover over it, and select 'Edit with Elementor'. Then, edit the form to change the button label and save the page. 2. If the button still doesn't translate, use WPML's String Translation to locate and translate the string. This might involve enabling the 'Look for strings while pages are rendered' option under WPML > String Translation, visiting the page where the string is displayed, and then searching for the string again in WPML. 3. Alternatively, check if the strings are included as admin text strings, which can be translated following the process described here. Related documentation can be found here.
Please note that the solution might be irrelevant due to being outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 here.
Problem: The client is experiencing an issue where the favicon icon does not appear on Google search results for the French version of their website. Solution: We have verified that the favicon appears correctly on the French version of the website. It is possible that Google may need more time to update its search results. We recommend waiting a few weeks to see if the issue resolves itself.
If the problem persists or if this solution becomes irrelevant due to updates or it does not apply 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, feel free to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: If you're experiencing issues with your language switcher not referring to translated pages and encountering a 'page not found' error, it might be due to the pages being in 'Draft' status instead of 'Published'. Solution: We recommend following these steps to resolve the issue: 1. Ensure that WPML and the Strings Translation plugins are activated. 2. Navigate to Pages -> All Pages and switch to the English version. 3. Select the pages that you want to publish. 4. Choose 'Edit' in the 'Bulk action' option and click Apply. 5. Change the status to 'Published' and then click the Update button.
This should correct the problem with the language switcher. 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client wanted to re-translate blog posts using WPML's automatic translation after manually translating them. However, the right column in the translation editor was pre-filled with the previous manual translations, even after deleting the manually translated posts. Solution: If you're experiencing this issue, it's necessary to clear the translation memory associated with your site to prevent old translations from appearing. We recommend you contact us directly to assist with clearing the translation memory for your specific site.
Please note that this solution might be 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 our support forum.
Problem: The client is unable to automatically translate the URL slug when using WPML. Despite having automatic translations enabled, the URL field remains empty in the translation editor and defaults to the English slug, which does not meet the client's needs as they often differ from the page title. Solution: 1. To address the issue of untranslated URL slugs, we recommend following the steps in our guide on translating page slugs. You can find the guide here: Translating Page Slugs. 2. If you prefer the URL slug to auto-translate based on the page title, select the 'Auto-generate from title (default)' option in WPML -> Settings -> Translated documents options -> Page URL. 3. For manual translation of the slug, choose the 'Translate' option in the same settings area. This will allow the slug to appear in the Translation Editor for manual adjustment. 4. If these settings do not resolve the issue, we have also provided a screencast with additional steps that might help. View the screencast here: WPML Slug Translation Screencast.
Please note that the solution provided might be outdated or not applicable to your specific case. 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. If the issue persists, please open a new support ticket.
function fails to retrieve the correct host name, rendering REST URLs generated in the CLI environment invalid. Solution: We tested the scenario using WPML version 4.5.15 with no other plugins active. We used the following code to simulate the environment and did not encounter the issue:
if (defined('WP_CLI') && WP_CLI) {<br /> class ExampleCommand extends \WP_CLI_Command {<br /> /**<br /> * @subcommand wpml-rest-api<br /> */<br /> public function wpmlRestApi() {<br /> echo get_rest_url(path: 'wp/v2') . "\n";<br /> }<br /> }<br /><br /> WP_CLI::add_command('example', ExampleCommand::class);<br />}
We recommend you provide more details or a screen recording of the issue to help us better understand and address the problem.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the issue persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: You are trying to translate some strings on your site using WPML, but some strings revert back to the default language after you turn off the 'Look for strings while pages are rendered' option. Solution: We recommend following these steps: 1. Navigate to WPML-> Support-> Troubleshooting. 2. Click on the "Show custom MO Files Pre-generation dialog box" button. 3. When the pop-up appears, click "Generate .mo files". After completing these steps, please wait for the process to end and then check the strings on the front end.
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 the problem persists, please do not hesitate to open a new support ticket at our support forum.
Problem: You are trying to delete ACF repeater fields in the English version of your site, but after deletion, these fields still exist in other languages. Additionally, when trying to save translations in the WPML Translation Editor, the segments are not saving. Solution: First, ensure that all Repeater Fields and Groups are set to "Copy" in the ACF configuration. This setting helps synchronize the deletion across all languages. For more details on setting up field configurations, visit Recommended Custom Fields Translation Preferences for ACF and WPML.
Next, check your server's minimum requirements. WPML requires a WordPress memory limit of at least 128M, but your PHP Memory Limit is currently set to 128M, which might be insufficient. We recommend increasing the WordPress memory limit to at least 256 MB. Contact your hosting provider to adjust the PHP MEMORY LIMIT on the server to at least 256M or higher.
If this solution does not resolve your issue or seems outdated, please check for 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 problems persist, we recommend opening a new support ticket at WPML support forum.
Problem: You are working on a development site and trying to activate the OTGS plugin after uploading it. The plugin appears as activated but isn't functioning. Solution: This behavior is expected. The OTGS installer plugin remains deactivated by default; it only needs to be installed to function. To use it, navigate to Plugins > Add New > Commercial. There, you will find a list of available plugins.
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 is experiencing unresolved issues with their website using WPML, specifically with ACF field groups and menu translations. Solution: For ACF field groups, we recommend setting the translation preference to "Same fields across languages" and then re-running the translations with the WPML Translation Editor. For further guidance, please refer to the documentation on translating sites built with ACF: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/ For translating menus, especially custom menu items, these should be translated at WPML > String Translation. More information can be found here: https://wpml.org/documentation/getting-started-guide/translating-menus/ If you're experiencing issues with the cart button, this might require a more detailed investigation. We suggest opening a new ticket specifically for this issue.
Please note that the solution provided 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the language switcher is not functioning on a specific page of their site, while it works correctly on all other pages. Solution: We suspect the issue might be due to database corruption. Here are the steps we recommend: 1. Duplicate the problematic page. 2. Send the duplicated page to translations to see if this resolves the issue. 3. Optionally, you can try to fix the issue directly in the database:
If these steps do not resolve the issue or if you are not comfortable making these changes yourself, please contact our support team for further assistance. 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. If the solution provided here becomes outdated or does not apply to your case, please open a new support ticket.
Problem: You are experiencing issues where the English version of your website does not match the Polish version after integrating the WPML plugin, resulting in a broken schema. Solution: First, verify if the product single pages are displaying correctly by checking a specific product page, for example, the Super Kid Mohair Sweater. If the pages are correct, the next step is to use the WPML String Translation to ensure all necessary strings are translated correctly. This can help in aligning the schema across different language versions of your site.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. It's also advisable to 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, please visit our support forum.
Problem: The client is experiencing higher than expected credit usage when using WPML / Translation Management for automatic translation of products, compared to using WooCommerce / WooCommerce Multilingual & Multicurrency. Solution: We explained that the number displayed in Translation Management is an approximate value and may not always be 100% accurate. We are currently working on improving this estimation tool, and an updated version will be available in future releases. To check the credit usage, we recommend navigating to WPML → Translation Management → Tools → Automatic Translations Usage Report.
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: You have translated your Avada menu and header layout using WPML, but the correct header layout is not displaying on the translated pages. Solution: We recommend checking the layout display settings for your translated pages. Specifically, ensure that the correct pages are set in the layout display settings to display the transparent header. This adjustment should resolve the issue of the incorrect header appearing on your translated pages.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Additionally, please check the related known issues and verify that you have installed the latest versions of themes and plugins. For further assistance, you can also visit our support forum.
Problem: The client was experiencing issues with translating a WooCommerce composite product into Italian using WPML. The translation process was not functioning correctly, sometimes affecting the default English product as well. Specifically, when scenarios were added to composite products, the component dropdown options were not displaying correctly in the Italian version, though they worked fine in English.
Solution: We advised the client to ensure that all plugins were up to date and to use the Advanced Translation Editor (ATE) for translating products. It was important to translate using ATE rather than the WordPress Editor to avoid issues with saving changes and to ensure the translation process was handled correctly by WPML. We also suggested translating the products step-by-step using ATE and checking if the issue persisted. If problems continued, we recommended deactivating the WPML plugins temporarily to verify if the issue was indeed related to WPML or if it was an issue with the WooCommerce Composite Products plugin.
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 here.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
