Problem: You want to auto-translate content as soon as it is created on your site, but the WPML auto-translate function is not triggered when properties are added from the frontpage. Solution: We recommend you go to the properties page and publish the pending posts. After doing this, the automatic translation should work correctly.
If this solution does not resolve your issue or seems outdated, please check the related 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 for further assistance. You can do so at WPML support forum.
Problem: You are trying to translate a specific string from the 'WooCommerce PayPal payment' plugin using WPML's 'String Translation', but the translation does not appear on the frontend after clearing the cache. Solution: If the string you are trying to translate is "Pay via PayPal" and it's not displaying in the frontend, we recommend following the workaround provided in our documentation. Please visit https://wpml.org/errata/woocommerce-paypal-payments-pay-via-paypal-translation-not-working/ and apply the suggested steps.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client was unable to display the sidebar widget on the translated shop page using Elementor and WPML after translating the page from French to English. Solution: We recommended the following steps to resolve the issue: 1. Variations: - Go to WooCommerce >> WooCommerce Multilingual >> Settings tab >> Troubleshooting link (bottom right) > Select the below options: - Sync products variations - Fix translated variations relationships - Click on the 'Start' button.
2. Template: - Go to Template > Saved Templates - Click on 'All' and locate the template: 'Elementor Archive des produits #8135' - Edit it using Elementor and make a minor change to the French template, (e.g., add an empty space and save it) - Go back to the template listing screen and edit the English translation of 'Elementor Archive des produits #8135' using the WPML Advanced Editor - Ensure the progress bar reaches 100% and save it.
We recommend testing this solution on the live site. If this solution does not resolve the 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. If the problem persists, we encourage you to open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where the conditional logic of a Ninja form stops working in the translated language, causing incorrect information to populate in the fields. Solution: We recommend checking if the issue persists in a minimal environment on your live site by following these steps: 1. Deactivate all plugins except those active on the sandbox. 2. Temporarily switch to a WordPress default theme, such as Twenty Twenty-One. 3. Make a minor edit to the form in the default language. 4. Update the form's translation. After testing, the issue is fixed after the third and fourth steps. Please ensure to back up your database before performing these tests.
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 the problem persists, please open a new support ticket with us for further assistance.
Problem: The client is planning to migrate their website to a new domain and wants to ensure that the WPML plugin continues to work seamlessly after the migration. Solution: If you're planning to migrate your website to a new domain, we recommend following these steps: 1. Ensure you create a full backup of your website before starting the migration. 2. After migrating, visit https://wpml.org/account/sites and remove the old key used on the initial domain. 3. Generate a new key for the new domain. 4. Go to your website's backend, navigate to Plugins > Add New > Commercial, and register WPML with the new key. You might need to click "Unregister" first. 5. You may receive a notification that WPML detected a new address for your site. Please refer to the following documentation for guidance on what to do next: Using Advanced Translation Editor when you move or use a copy of your site.
If this solution does not apply to your case, or if it 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 you need further assistance: WPML Support Forum.
Problem: You are unable to update WPML due to a 'Site key not matching' error, which indicates that WPML cannot connect to its server for updates and security checks. This might be due to network or security settings blocking communication with wpml.org. Solution: If you're experiencing this issue, we recommend you try the following steps: 1) Visit https://wpml.org/account/websites/ 2) If your site URL is already registered, delete it from the list. 3) Re-enter the site URL to generate a new site key. 4) Click on 'Show key' and copy the new site key. 5) Go to Plugins > Install > Commercial (Tab) on your WordPress site, and enter the new key to register WPML. If WPML is still registered, deregister it first.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client needed to increase the WordPress memory limit to at least 256 MB for WPML and was looking for recommendations on plugins to customize and enhance the appearance of emails. Solution: We advised the client to increase the WordPress memory limit by adding the following code to the
wp-config.php
file:
define ('WP_MEMORY_LIMIT', '256M');
This code should be placed just before the comment:
If this solution does not resolve your issue or 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 for further assistance.
Problem: The client was facing two issues on their website. First, the string 'Related post' was translated into Danish and Spanish but stopped working on the Spanish version. Second, a layout part translated into English was not visible when translated into Spanish, despite following the provided instructions. Solution: 1. We requested a copy of the client's website using the Duplicator plugin (https://wordpress.org/plugins/duplicator/) to troubleshoot the issues locally. 2. Upon reviewing the website copy, it was discovered that the theme was not registering the 'Related Posts' string correctly. We edited the file 'wp-content\themes\themify-ultra\includes\related-posts.php' by changing the text-domain from 'themify' to 'wpml-support-themify'. After rescanning the theme for strings, the issue was resolved, and the string displayed correctly.
If this solution does not resolve your issue, 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 problem persists, please open a new support ticket.
Problem: You are trying to locate the hreflang tags in your sitemap using WPML, WPML SEO, and Rank Math SEO, but cannot find them despite having checked the 'as early as possible' option in WPML -> SEO options -> Display alternative languages in the HEAD section. Solution: Hreflang tags will not appear in your sitemap but should be visible at the top of your page source due to your current settings. You can verify their presence by viewing the source of your page. For example, you might see entries like:
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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 unable to translate global buttons on a Divi theme page using WPML and does not see an option to do so. Solution: For the Supreme Tabs issue: 1. Go to your Pages tab and hover over the language column of the 'Proceso de Admisión' page, then click on 'Translate myself'. 2. Add all the missing translations. There were many fields missing, likely due to an issue with the automatic translation of the page. Translating these should resolve the problem.
For the second issue: 1. Send the 'History' page (in English) to the trash. You can change the language in the top bar to English and search for the 'History' page. 2. Go to the trash and permanently delete the page. 3. Access your Spanish Pages tab and hover over the language column of the 'Historia' page, then click on 'Translate myself'. 4. Add all the missing translations. There were many fields missing, likely due to an issue with the automatic translation of the page. Translating these should resolve the problem.
We apologize for the inconvenience, but it seems that the automatic translation service is having difficulties with some pages. Following the steps described should resolve the issue in these situations. Please let us know if this resolves your problem.
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: You are trying to add a site to your WPML account which shows as the third site, but you encounter an error stating that you are using an expired account and have used all of your installs. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Visit https://wpml.org/account/sites 2. Remove the current key. 3. Generate a new production key for that domain. 4. Copy the new key. 5. Go to your site's backend. 6. Navigate to Plugins > Add New > Commercial. 7. Unregister WPML first from the old key. 8. Re-register WPML with the new key. Additionally, please clear any existing local or server caching.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with WPML Translation Management where 'Jobs could not be loaded' due to wp-json being disabled for security reasons. Additionally, they encounter a message stating 'You can only edit translations assigned to you' and are considering downgrading WPML due to these issues. Solution: We recommend setting the Classic Translation Editor (CTE) as the default method for creating translations, which does not require the REST API and thus bypasses the issue with wp-json being disabled. Here are the steps: 1. Set CTE as the default translation method: https://wpml.org/documentation/translating-your-contents/translation-editor-options/ 2. Alternatively, use the WordPress Editor for creating translations and avoid using WPML > Translation Management and WPML > Translations for these contents. 3. To hide WPML's menu options 'Translation Management' and 'Translations', use the Admin Menu Editor plugin: https://wordpress.org/plugins/admin-menu-editor/ 4. If using the WordPress Editor, ensure that translators have the admin user role to create translations. If these solutions do not resolve your issue or seem 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: The client is unable to translate the hero text on their homepage when changing the site language, despite other elements on the page translating correctly. The hero text is created using the Mesmerize Companion plugin by Extend Themes. Solution: We discovered that the hero text section, customized via the theme customizer, does not appear in the String Translation options. To resolve this, the client needs to manually add the translation for this section. This can be done by navigating to the 'Translate texts in admin screens' option within the WPML settings. For a detailed guide on how to add translations, please refer to this screen recording: https://go.screenpal.com/watch/cZihFTV8pwu
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, we highly suggest 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: WPML Support Forum.
Problem: The client needed a way to translate the attributes of a shortcode but not its content. They were using a custom XML to register the attribute for translation but couldn't find a way to exclude the content from being translated. Solution: We recommended using a custom XML configuration to ignore the content of the shortcode while translating its attributes. Here is the XML configuration to achieve this:
We advised the client to apply this configuration and make minor changes to the primary language page to ensure the custom XML settings take effect.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues 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 here.
Problem: The client is experiencing a deprecated warning with
Deprecated: str_contains(): Passing null to parameter #1 ($haystack) of type string is deprecated
when using WPML with PHP 8.2. The issue seems related to a compatibility problem between LearnDash and WPML. Solution: We recommend reproducing the issue on a clean staging site with only WPML and LearnDash LMS activated. If the issue persists, follow these steps: 1. Backup your site. 2. Switch to a default WordPress theme temporarily. 3. Deactivate all unrelated plugins. 4. Check if the issue still exists. 5. Reactivate plugins in groups to identify the problematic one. 6. Switch back to your original theme. If you identify the plugin causing the issue, you can apply a temporary patch provided by the client. Additionally, our developers are aware of this issue with PHP 8.2 and are working on a fix expected in WPML version 4.7. Meanwhile, to avoid displaying errors to site visitors, disable debug mode by adding
define('WP_DEBUG_DISPLAY', false);
to your wp-config.php file. For more details on related issues, please visit this errata page.
If this solution does not resolve your issue or seems irrelevant, 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
