Problem: The client reported that three items (two pages and one post) that were translated are not showing up on the Spanish version of their site. Although marked as translated, the content was not visible when switching to the Spanish version. Solution: We suggested that the client checks the trash section of their website to see if the missing pages and post were accidentally placed there. If found in the trash, we advised the client to restore them and then check if the issue with the missing translations is resolved.
If you're experiencing a similar issue, we recommend checking your trash for any pages or posts that might have been mistakenly deleted. If you find the translated items there, simply restore them to resolve the issue.
Please note that this solution might not apply to your case, or it could be outdated. If after trying this step you still encounter problems, 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 issue persists, please do not hesitate to open a new support ticket with us.
Problem: The client was experiencing a critical error when trying to translate a product in WordPress using WPML. He did a reset and got a new error in the dashboard.
Solution:
1. We recommended performing another reset as was no translations done and before reactivating WPML or configuring it, to deactivate all plugins and switch to the default theme. 2. If the error continued, we advised checking the guide on missing database tables at https://wpml.org/errata/missing-_icl_strings-_icl_string_translations-data-tables/. It's important to back up the database before making any changes. 3. We asked the client to verify if the
_icl_strings
table existed in their database and if so, to try closing the error message. 4. We suggested checking for the problematic string in WPML → String Translation and deleting it from there. 5. If the issue was still unresolved, we recommended deactivating all plugins except for WPML, WooCommerce Multilingual & Multicurrency, and WooCommerce, and then attempting to close the message again.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your 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 with us for further assistance.
Problem: The client is experiencing an issue where the Advanced Translation Editor (ATE) does not load in any browser, including Mozilla Firefox and Chrome, on two different sites. Solution: We recommend clearing the cache on both the server and the browser to resolve the issue.
Please note that the solution provided might be outdated or not applicable to your case. If the issue continues, 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 you still need assistance, do not hesitate to open a new support ticket in the WPML support forum.
Problem: If you're experiencing issues with automatic translation not working with Slider Revolution, Solution: We recommend following our guide to translate your slides manually. Here is the step-by-step documentation:
Keep in mind that this solution might be irrelevant if it's 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 issue persists, please don't hesitate to open a new support ticket. You can reach us through the WPML support forum.
Problem: The client is trying to publish a webpage with slightly different text content in the translation.
Solution: If it needs a different structure for the translation, you can switch to the WordPress Editor to complete the translation without using the WPML translation editor. It's important to note that the two editors are not synchronized, so if the you switch to the WordPress Editor, you will need to retranslate the page. More information can be found here: Using different translation editors for different pages.
Please be aware that this solution might be irrelevant if it's outdated or not applicable to your case. If so, we encourage you to open 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. If you need further assistance, please visit our support forum: WPML support forum.
Problem: The client was experiencing an issue where the permalink slug for a custom post type was not translating correctly, leading to a 404 error on the translated version of the page.
Solution: We discovered that the problem was caused by the Redis Object Cache plugin. Once we deactivated this plugin, the permalinks started working correctly. If you're experiencing a similar issue with permalinks not translating on your custom post types, we recommend trying to deactivate the Redis Object Cache plugin to see if that resolves the issue.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If deactivating the Redis Object Cache plugin does not solve your problem, or if you encounter any other issues, 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 issue persists, please do not hesitate to open a new support ticket with us.
Problem: The client needed to translate a custom tab added to the WooCommerce product data, which was not appearing in the WPML String Translation interface.
Solution: 1. We advised the client to ensure that the strings are wrapped in the gettext function. For example, replace:
'Refund and Returns Policy'
with:
__('Refund and Returns Policy', 'themedomain')
2. We instructed the client to go to WPML >> String Translation and enable the 'Look for strings while pages are rendered' option in the Auto register strings for translation section. 3. The client should then visit the page on the front end where the string appears. 4. After that, revisit the WPML >> String Translation page and search for the string. 5. Translate the string as needed. 6. Finally, uncheck the auto-registration option to maintain site speed.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket. You can do so by visiting the WPML support forum.
Problem: The client is experiencing an issue where a 'Button Group' flexible content block is not displaying on the homepage after cloning their live site to a staging environment. This issue occurred after upgrading to ACFML2 and making changes to ACF field groups. The problem persists despite trying various settings, and the block reappears only when the ACFML plugin is disabled.
Solution: We recommend the following steps: 1. Create a fresh staging site from the live site. 2. Update WordPress Core, WPML CMS, String Translation, ACF, and ACFML to the latest versions, specifically ACFML (2.1.0). 3. Change the button field name to
button_group_repeater
. 4. Keep the clone field as Seamless. 5. Check if the issue is resolved.
Please note that the solution provided might be outdated or not applicable to your 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, do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: The client is trying to translate an English webpage into German, Polish, French, and other languages but encounters an error 'XLIFF Server Communication' stating 'The xliff file could not be read.' The translation process seems to be stuck, showing excessively long completion times, and the client is unsure how to terminate the process or resolve the issue.
Solution: 1. Navigate to WPML -> Translation Management -> Translation Jobs and cancel any in-progress translation jobs. If there are no jobs in progress, proceed to the next steps. 2. Edit the default page by making a small change and updating the page. 3. Go back to WPML -> Translation Management and send the edited page to the translation basket. Ensure to tick the checkbox, scroll down, and click 'translate' to see the translation basket tab. 4. In the translation basket, send the page to yourself as a translator. 5. Visit WPML -> Translations, take the job, and translate the page. After saving the translation at 100%, check if the correct content is displayed.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your specific case. If the issue persists, 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. Should you need further assistance, please do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client encountered an issue where many categories on their English site displayed titles in Portuguese, which affected their SEO as these incorrect titles appeared in Google and Bing search results. The client resolved the issue for individual pages by saving each category again but was looking for a way to fix all titles at once without checking each one manually. Solution: We have not previously encountered this specific issue and it is not listed in our known issues. We cannot provide a preventive measure due to the unknown cause of the issue. We recommend keeping all plugins and themes up to date for the latest security and bug fixes. To address the client's third question, we suggest trying to update the pages in the original language using bulk mode, and emphasize the importance of backing up the database before making any changes.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking our related 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.
Problem: The client is experiencing database errors related to collation issues in their WordPress error log, which mention WPML.
Solution: We recommend ensuring that all database tables and their columns have a consistent collation. Specifically, change any tables or columns with the collation "latin1_swedish_ci" to a unicode-aware collation such as "utf8mb4_unicode_ci" or "utf8mb4_unicode_520_ci". For WPML tables, use the "Fix WPML table collation" option available under WPML → Support → Troubleshooting. WPML Troubleshooting Options
If you're not comfortable making these changes yourself, you can ask your hosting provider for assistance. It's crucial to back up your database before making any changes. You can find more information on changing collation in the database here: Stack Overflow: Change Character Set and Collation
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 necessary, do not hesitate to open a new support ticket with us.
Problem: The client is experiencing an error message in the WordPress dashboard and under WPML indicating an issue with loading configuration files. Solution: We recommend checking if cURL support is enabled and ensuring it is running on version 7.34.0 or higher. This issue is often related to the lack of cURL support or an outdated version of the library. For more details, please refer to our documentation on this error: WPML could not load configuration files. If you are still facing this issue after confirming cURL support, we suggest 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.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, please do not hesitate to contact us by opening a new support ticket in our forum: WPML support forum.
Problem: The client has automatically translated their GravityForms using WPML and now needs to make slight changes to the translations. Solution: We recommend that the client sends the form again for translation and updates the translation in the WPML editor. This can be done by navigating to WPML -> Translation Management. For detailed instructions, please check the following documentation:
If this solution does not apply to your case, or if it seems outdated, we encourage you to open 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: https://wpml.org/forums/forum/english-support/.
Problem: The client is experiencing issues with WPML on PHP versions 8.1 and 8.2, encountering deprecated warnings. Solution: We recommend using PHP versions 7.4 through 8.0, as WPML is fully compatible with these. While WPML does function with PHP 8.1 and 8.2, deprecated warnings may occur. Our development team is actively working to address these warnings. Additionally, since WordPress only offers beta support for PHP 8.2 and 8.3, full compatibility with these versions will be ensured once WordPress extends its full support to them.
Please note that this solution might not be relevant if it's outdated or not applicable to your specific case. If the issue persists, 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. Should you need further assistance, please don't hesitate to open a new support ticket. You can reach out to us through the WPML support forum.
Problem: The client has reached the first threshold of the safety limit charges and needs to know how to pay the invoice to continue generating automatic translations. Solution: If you're experiencing this issue, we recommend you try the following steps to pay for your translations and continue your work: 1. Navigate to your pages or posts and select one with substantial untranslated content. 2. Click the "+" button to add a translation for that content. 3. If a message appears indicating "not enough credits," you will find a link to "Get more credits." 4. Click on this link, and you will be redirected to the payment options where you can proceed with the payment.
Please note that the solution provided might be outdated or not applicable to your case. If after following these steps you still need assistance, 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 issue persists, 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
