Problem: If you're experiencing issues with transferring credits to wpml.org and receive the message 'unable to withdraw credits on wpml.org, please contact technical support', we recommend following these steps. Solution: 1. Visit the list of registered sites page at https://wpml.org/account/sites/ 2. Delete the current sitekey for your site. 3. Create a new sitekey for your site. 4. Navigate to the admin area > Plugins > Add New > Commercial tab > Un-register and re-register the site with the new sitekey. After completing step 2, your credits should be returned to your WPML.org account. If this does not resolve the issue, try transferring the credits from your site to WPML.org again.
If this solution does not apply to your situation, 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is working on a site using WPML's Advanced Translation Editor (ATE) and is facing difficulties managing long pages without certain functionalities. Specifically, they need a filter to display only non-translated strings and a 'validate all' button for strings marked in yellow/orange that require validation. Solution: We have acknowledged the client's request for these functionalities and have forwarded it to our development team for consideration in future updates. If you're experiencing similar issues, we recommend checking our known issues page and ensuring you have the latest versions of themes and plugins installed. If the problem persists or the solution provided here is outdated or not applicable to your case, please open a new support ticket with us for further assistance. Contact WPML support
Problem: The client wanted to know if using page revision rollback would restore both the original page content and the past translation states. Solution: We explained that rolling back a page to a previous revision in WordPress does restore the original content to an earlier state. However, this process does not automatically restore the translations to their past versions. The translations remain as they were before the rollback, potentially leading to them being out of sync with the original content. To ensure that both the original page and its translations reflect the same content, manual updates to the translations might be necessary after rolling back the original page. Unfortunately, WordPress does not have a built-in feature to roll back translations along with the original page revisions.
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 experiencing an issue where the Divi Theme Builder content overrides all languages when you change one language. This problem persists even after following previous solutions.
Solution: 1. Check if your Divi templates/layouts are corrupted. If so, consider creating a new product template. 2. Translate the new templates using WPML -> Translation Management. 3. Deactivate outdated plugins and update the Divi theme to avoid conflicts. 4. Test the issue in a test site with only essential plugins and the Divi theme activated. Follow these steps: - Keep WC and WCML inactive initially. - Reproduce the issue with standard post types and theme builder templates. - Activate WC and WCML, create test products, translate them, and check if the issue persists. 5. If the problem is specific to your site or certain post types, it might be due to database corruption. Try using a new template in a controlled environment as described.
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.
Problem: The client needs to change the original language displayed in the WPML Advanced Translation Editor for a translator who does not speak the original language of the content. The content was initially in French, and the translator needs to see English on the left side instead of French when translating to Arabic. Solution: We explained that it is not possible to change the language displayed on the left side in the Advanced Translation Editor. This side always shows the default language in which the page was initially created. If you're experiencing this issue and need the translator to view a different source language, unfortunately, this cannot be adjusted for translations already done. For new translations, ensure the translator's settings are correctly set to translate from the desired source language.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is attempting to manually change a link URL using the Advanced Translation Editor (ATE) but is unsure if the process described in the documentation is still applicable with the latest version of ATE. Additionally, the client faces issues when trying to filter a link in a Divi module in the Divi Library. Solution: We confirmed that it is still possible to manually change link URLs with the latest version of the Advanced Translation Editor by searching for the URL in ATE and manually translating it. For issues related to filtering links in Divi modules, we suggested creating a custom XML configuration code for the module to override the default WPML feature and translate the URL in ATE. For further guidance, refer to the documentation on Maintaining Divi Builder Compatibility with WPML.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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.
Problème : Le client travaille sur le site en utilisant WPML et cherche à accéder aux phrases non validées dans l'ATE pour terminer la traduction. Il souhaite pouvoir filtrer les phrases non encore traduites directement dans l'ATE, similaire à l'ancienne fonctionnalité de l'éditeur classique V1. Solution : Nous avons suggéré d'utiliser les outils de navigateur ou une extension de navigateur pour modifier la classe CSS
1
.AT-segment_list__add_translation_container
. Cette classe est présente uniquement sur les blocs en attente de traduction, permettant ainsi de les mettre en évidence en changeant la couleur d'arrière-plan. Nous avons recommandé l'extension Chrome Visual CSS Editor qui permet de modifier les paramètres CSS de ces éléments sans coder.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous invitons à consulter les problèmes connus, vérifier la version des correctifs et vous assurer que vous avez les dernières versions des thèmes et plugins installés. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem:
PHP Fatal error: Uncaught TypeError: str_contains(): Argument #1 ($haystack) must be of type string, array given in ...m/wp-includes/blocks.php:1409 When enabling "Scellius for WooCommerce" plugin with PHP 8
Solution:
The error was happening due to the settings being corrupted.
To fix this, We went to the site database wp_options table and searched for the option name "woocommerce_scelliusstd_settings" and renamed it to "woocommerce_scelliusstd_settings_old", this stored the plugin settings.
Problem: The client is not receiving notifications and experiences delays in displaying translation changes, despite clearing WordPress cache, browser cache, and deactivating hosting CDN. Solution: We recommend checking the notification settings in the top bar of the ticket conversation.
Problem: The client reported that translations do not update instantly, and this issue persists even in a minimal environment. It affects both pages and posts. Additionally, the client receives a message stating, "Translation successfully completed. Please return to your site manually, as we couldn't redirect you automatically." Solution: We accessed the client's website and performed the following steps to verify the issue: 1. We navigated to the Pages tab and opened the editor for a specific page. 2. We edited the Spanish translation of the page, changed the title, and saved the changes. 3. We then checked the corresponding Spanish page and confirmed that the changes were reflected instantly. We recommend the client to verify if the website is functioning correctly now. If the issue persists, we suggest recording a video demonstrating the problem using Loom, which is free and easy to use.
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. 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, you can also contact us directly at the WPML support forum.
Problem: The client reported a styling issue on the English version of their website, specifically on a certain page, which differed from other languages. Additionally, the client inquired about a feature in the translation editor to automatically display strings that are not translated or not checked yet. Solution: We updated the translation to address the styling issue. For the translation editor query, we recommend using filters available in the WPML translation management system to display untranslated or unchecked strings. This can streamline the process of finding and translating missing strings.
If this solution does not resolve your issue or seems outdated, please check the related known issues and verify you have the latest versions of themes and plugins installed. If the problem persists, we encourage you to open a new support ticket.
