Problem: Если вы столкнулись с ошибкой в консоли на товарных страницах в админпанели, где указано, что файл локализации (например, uk.json) не найден, это может быть вызвано отсутствием файла локализации для установленного языка. Solution: Мы подтвердили, что данная ошибка не влияет на функциональность сайта и является безвредной. Наша команда уже информирована о проблеме и рассмотрит возможность добавления необходимых файлов локализации в будущих обновлениях. Если ошибка вызывает беспокойство, мы рекомендуем проверить, установлены ли последние версии тем и плагинов, а также ознакомиться с известными проблемами на странице известных проблем.
Problem: The client was unable to translate certain texts and strings on their website using WPML.
Solution: We recommended several steps to make the strings translatable: 1. Enable auto-detection in WPML → String Translation and visit the front-end in a non-default language to help WPML detect and register the strings. 2. If strings are still missing, use WPML → String Translation → Utilities → Admin Texts Translation to find and select strings from theme or plugin options for translation. 3. If strings are not found in Admin Texts, scan the theme or plugin directly from WPML → Theme and plugin localization. 4. Check WPML → Translation Dashboard under Templates or Template Part sections for embedded strings in theme parts.
If these steps do not resolve the issue, it might be due to strings being hardcoded in theme/template files or using non-WPML-compatible functions. In such cases, a manual inspection of the texts and their page sources is necessary. We recommend not repeating previously confirmed ineffective steps and considering alternate methods like registering text via WPML hooks or direct gettext review.
If the solution provided here is 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problème : Les variations de certains produits ne s'affichent pas correctement en anglais ou en français sur le site du client. Les slugs des taxonomies traduites étaient différents, empêchant WPML de les relier correctement. De plus, des problèmes de style de boutons de variations et des problèmes de cache affectaient l'affichage. Solution : 1. Nous avons corrigé les slugs pour qu'ils correspondent dans toutes les langues en utilisant l'icône de copie dans l'interface de WPML. 2. Pour les chaînes non traduites comme "avis", nous les avons ajoutées manuellement à la traduction via String Translation. 3. Concernant le style des boutons de variations, le problème provenait des paramètres du thème et non de WPML. Nous avons suggéré de vérifier les paramètres du thème ou de contacter les auteurs du thème pour résoudre le problème de style. 4. Nous avons purgé le cache à chaque modification pour assurer que les changements soient visibles.
Si cette solution ne s'applique pas à votre cas ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de confirmer que vous avez installé les dernières versions des thèmes et plugins, et d'ouvrir un nouveau ticket de support si nécessaire.
Problem: The client was experiencing issues with forms created in Bricks Builder on pages translated with WPML. While forms worked correctly in the original language, submissions from translated versions were not being sent, and emails did not arrive at the specified address. Additionally, translated pages displayed a 404 error or redirected to the homepage. Solution: The issue was resolved by updating the GUIDs in the database after a site migration. The client updated the GUID fields correctly, which fixed the form functionality and email delivery on the translated pages. Regarding the WPML Troubleshooting message indicating 'Alias domains to https://bws-windows.com domain: * https://bws-windows.com', it is not a concern if the forms are functioning properly and can be ignored.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problème : Si vous constatez que les catégories de produits dans le widget de filtre de catégories de produits sur le front-end ne s'affichent pas correctement en anglais, alors que les traductions semblent correctes dans le back-end, cela pourrait être dû à un problème de tri des catégories. Solution : Nous vous recommandons d'essayer les étapes suivantes pour résoudre ce problème : 1. Ajoutez le code suivant dans le fichier
functions.php
de votre thème actif :
testfix();<br />function testfix(){<br /> global $wpdb;<br /> $elements = $wpdb->get_results("SELECT `element_id`<br />FROM {$wpdb->prefix}icl_translations<br />WHERE `element_type` = 'tax_product_cat' ORDER BY `trid`");<br />foreach ($elements as $element){<br /> $testelement = get_term_meta($element->element_id, 'order', true);<br /> if ($testelement == ""){<br /> add_term_meta($element->element_id, 'order', 0);<br /> }<br />}<br />}
2. Réglez l'option de tri du widget sur 'Ordre des catégories'. 3. Visitez le front-end de votre site une seule fois pour que les modifications prennent effet. 4. Retirez ensuite le code du fichier
functions.php
.
Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.
Problem:
When saving Automatic Translation settings in WPML (and other plugin settings like Hostinger Tools), client received a "Some error occurred" message. The settings were not being saved.
Solution:
During the investigation, I found that .htaccess file contained a custom "Trailing Slash Redirect" rule that was interfering with WordPress REST API requests.
This rule was forcing all URLs to end with a trailing slash (/), which caused:
- REST API POST requests (e.g., /wp-json/wpml/v1/save-automatic-translation-settings) to be redirected with a 301 status to the same URL with a trailing slash
- The browser converted the POST request to a GET request during the redirect (standard HTTP behavior)
- The REST API endpoint returned a 404 error because it doesn't accept GET requests at that URL
This affected all plugins using the WordPress REST API, not just WPML.
I modified the existing trailing slash redirect rule in .htaccess file to exclude REST API paths (/wp-json/).
Problem: 1) The client receives an error indicating that WPML has detected a change in the site's URL after moving from a development subdomain to a new domain, despite updating the WPML license key. 2) Errors in Language settings prevent automatic translation because languages are not mapped to supported languages. Solution: 1) To resolve the URL change issue, navigate to WPML → Translation Dashboard and select the appropriate action on the migration banner. For more details, visit Using Advanced Translation Editor when you move or use a copy of your site. 2) After addressing the first issue, if language setting errors persist, go to WPML → Settings and ensure that a translation engine is selected.
If these solutions do not apply to your situation or seem outdated, we recommend opening a new support ticket. Additionally, 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.
