Problem: The client created a staging site using WPVivid and noticed that the translation settings for Forum/Topic/Reply defaulted to not translatable. They were curious why this happened and how to ensure these settings are retained during staging setups. Solution: We suspect that something might have gone wrong during the migration process, which should not normally occur if everything was correctly migrated. To avoid such issues in the future, we recommend using the Duplicator plugin for migrating your site. This plugin should handle the URL-replacing process effectively and migrate all data without issues. You can find the Duplicator plugin here: https://wordpress.org/plugins/duplicator/ For detailed documentation on how to use the Duplicator plugin, visit: https://snapcreek.com/duplicator/docs/ Here is a tutorial on how to use the Duplicator plugin: https://www.youtube.com/watch?v=3YDQ3Ey_2wY After migration, remember to register WPML on your new site and enter the new key. You can manage your sites and keys by logging into your WPML account and navigating to the "Sites" page at https://wpml.org/account/sites/
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 for further assistance.
Problem: If you're experiencing issues with translating custom block contents despite having wrapped them in localization tags, it might be because these are JavaScript strings. Solution: We recommend following our guide on adding gettext calls to JavaScript code, which you can find here: Translating JavaScript strings in WPML. However, be aware of a known issue where WPML might not currently translate JavaScript strings effectively. You can learn more about this problem here: Translating strings from JavaScript files issue. Additionally, strings like "Choose file" and "No file chosen" are dependent on the browser's language setting and may not be influenced by WPML.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.
Problem: The client is experiencing issues with the Advanced Translation Editor (ATE) in WPML, where clicking 'COMPLETE TRANSLATION' redirects to WordPress but does not finalize the translation. This issue does not occur with the Classic Translation Editor, which works as expected. Solution: We recommend the following steps to resolve the issue: 1. Edit the primary language page using the backend editor. 2. Proceed to edit the translations and attempt to complete the translation again. 3. If the issue persists, install a specific plugin from this link and update the ATE ID with the provided credentials.
4. Additionally, go to 'Troubleshooting' in WPML and click on 'Refresh License Data'.
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 at WPML support forum for further assistance.
Problem: The client's development site lost contact with WPML after detecting a new link and could not reconnect to the WPML account. The site was unable to continue without declaring it a copy due to a change in the IP address being recognized as the main link. Solution: We identified two separate entries for the client's URL in our system, each with different credit amounts. We merged these entries, consolidating the credits into a single account. This action restored the connection to WPML, allowing the client to see a total of 48,330 credits available. If you're experiencing similar issues with your development site losing contact with WPML or issues related to credit allocation, we recommend checking your account for multiple entries and contacting us for consolidation.
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 at WPML support forum.
Problem: The client needed to implement a custom language switcher in their header, similar to the one on the WPML site, featuring a single flag that displays other languages on hover. The default WPML language switcher was too wide and did not meet their design requirements. Solution: First, we advised the client to adjust the settings in WPML -> Languages -> Custom Language Switcher by selecting 'Dropdown' from the Language Switcher Style and unchecking the 'Native Language Name' and 'Language Name In The Current Language' options. For further customization, we provided a CSS snippet:
If this solution does not apply to your case, or if it becomes 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. Should you need further assistance, please open a new support ticket or consider contacting one of our certified partners at https://wpml.org/contractors/.
Problem: If you're experiencing issues with quotation marks appearing incorrectly in translations (e.g., inverted quotation marks in Arabic compared to English), despite looking correct in the Advanced Translation Editor (ATE), this summary is for you. Solution: 1. Edit the English page using Elementor and add the quotation marks as you wish them to appear. 2. Save the changes in Elementor. 3. Exit Elementor. 4. On the English editing screen, press the update button. 5. Check if the pencil icon next to the Arabic translation has changed to a circled arrow icon, indicating that the Arabic translation needs an update. 6. Update the Arabic translation using WPML's Translation Editor. This process should correct the display of quotation marks in your translations.
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 persists, please open a new support ticket.
Problem: You are trying to connect multiple domains (EE, LV, CZ, DE) for your multilingual site using WPML, which previously worked without issues. However, now the domains do not validate and fail to connect despite active SSL certificates. Solution: We have identified SSL issues with your domains. We recommend contacting your domain provider to check and resolve these SSL issues. If the problem persists after their intervention, please visit our support forum for further assistance. We also 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.
If this solution does not apply because it might be outdated or not relevant to your case, we highly recommend opening a new support ticket.
Problem: The client reinstalled their website and started translations anew. After modifying the English text, the Romanian translation remained unchanged. The client uninstalled the plugin, which deleted the templates along with the Romanian and Polish page duplicates. The plugin still indicated that the homepage was translated, but it was non-existent. Solution: We advised the client to first provide debug information by following the steps at https://wpml.org/faq/provide-debug-information-faster-support/. We then reviewed the Polish homepage translation and recommended clearing the cache, specifically suggesting the temporary disabling of the LiteSpeed cache plugin while working on the site. We also applied troubleshooting options available in WPML > Support > Troubleshooting to address the translation issues. We confirmed that there was no need for a site restoration or retranslation as the translations were stored in the translation memory.
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 trying to translate strings in the
admin_texts_wpseo_titles
section using WPML String Translation, but the translations are not appearing. Solution: 1. Navigate to WPML -> Strings Translation -> Translate texts in admin screens. 2. Search for the specific strings you need to translate. 3. If the strings are not already added to Strings Translation, add them. 4. Change their language from the default (English) to the desired language (e.g., Chinese) in Strings Translation. 5. Translate the strings as needed. 6. The translations should now appear correctly in the script. Repeat this process for any other strings you need to translate.
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: The client's website was translated into Japanese, but internal links on the translated pages were redirecting to the English version instead of the Japanese version. The links were initially set as relative paths.
Solution: 1. We recommended using full URLs for the team members' links instead of relative links to ensure they direct to the correct language version. 2. We suggested using WPML's string translation to manually find and translate the relative links. More information on string translation can be found here: this link. 3. We also advised checking the possibility of caching issues and recommended copying only the "/jp/team_member_name" from the Japanese version of the site to test if the issue persists.
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 problems continue, please open a new support ticket.
Problem: The client has translated two Elementor templates and single product extra content added through a WordPress widget, but they are not working. Solution: We added the following code to WPML-> Settings-> Custom XML tab to register the widget for translation:
After adding the code, we translated the widget strings via String Translation. We recommend checking the guide on registering admin strings for further details.
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.
Problem: If you're experiencing site crashes when switching languages, it might be due to a PHP fatal error related to incorrect string translation in your theme's WooCommerce catalog file. Solution: We recommend enabling WP debug to check the debug log for errors. If you find an error similar to 'Unknown format specifier "v"' in your WooCommerce catalog.php file, the issue may be resolved by re-translating the problematic string in the WPML String Translation. Ensure that all strings are correctly translated to prevent such issues.
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.
Problem: You are experiencing issues with the auto-translate feature on your website, which stopped working in April despite having enough credits. Solution: First, check if you are using the 'Translate Everything' mode in WPML->Settings. If it's already enabled and the auto-translate is still not functioning: 1. Edit the translation mode. 2. Switch to 'Translate what you choose'. 3. Switch back to 'Translate everything'. This sequence often resolves the issue.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check the related known issues and ensure you have the latest versions of themes and plugins installed. For further assistance, please visit our support forum.
Problem: The client wants to translate their website from Dutch to English using WPML and is seeking advice on the best translation option considering SEO and Google Ads. Solution: We recommend considering your priorities when choosing a translation method: 1. Translate Automatically: Saves time but may require review to ensure translations meet your brand’s standards. 2. Translate Myself: Offers full control over translations, ideal for tailoring content for SEO. 3. Duplicate Content: Useful for maintaining content structure, though it demands extra SEO optimization for English. A hybrid approach, starting with automatic translation and refining key pages manually, might also be effective. Don't forget to utilize the WPML SEO add-on for enhanced compatibility with SEO plugins. More details can be found here: https://wpml.org/documentation/related-projects/wpml-seo/
If this solution does not fully address 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. Should you need further assistance, please open a new support ticket or visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You are experiencing issues with automatic translations still occurring despite having disabled them in the settings, and this has resulted in the unintended use of translation credits. Solution: First, ensure that in WPML > Settings, you have selected the "translate what you choose" option. Next, navigate to WPML > Settings > Post Types Translation and verify that there is no "translate automatically" option selected for the post type in question. It's possible that the translation jobs were sent for automatic translation before these settings were adjusted, which might explain why translations are still being processed automatically. If you wish to reclaim the credits used, you can click to take back the credits if you do not want the automatic translation functionality.
If this solution does not resolve your issue or seems outdated, we 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. Should the problem persist, please open a new support ticket with us.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive