Problem: The client is experiencing issues with their WPML installation in production on Pantheon. They are unable to register their site due to a mismatch in the 'site_key' between their wp-config.php and the database, and cannot access the 'commercial' tab to register the site. They also cannot allocate credits on wpml.org as the PROD site is not active. Solution: We recommend the following steps to resolve the issue: 1. Visit https://wpml.org/account/sites and remove any old versions of the website from the list. 2. Add the production website URL again and copy the newly generated key. 3. Update the key in your wp-config.php file to match the newly generated key.
This process should help in correctly registering your site in production, allowing you to assign credits and activate PAYG translation services.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problème : Le client a ajouté l'italien et l'espagnol à son site multilingue, qui affichait déjà l'anglais sans problème. Cependant, une erreur critique apparaît sur les pages en italien et en espagnol. Après avoir désactivé les plugins, le client a identifié un conflit avec le plugin B2BKing Pro. Solution : Nous avons vérifié que l'API REST fonctionnait correctement, éliminant ainsi les problèmes de connexion au serveur. Le problème d'erreur critique était dû à une règle de
flush_rewrite
configurée par le plugin B2BKing Pro, qui ajoutait un dossier de langue inutile dans l'URL, rendant celle-ci inaccessible. Nous avons apporté une correction au fichier
Problem: If you're experiencing an issue where clicking 'Edit in Advanced Translation Editor' on a 'teams' post type redirects you to a blank page, and your logs show an 'ATE Server Communication Unauthorized "status":401', this indicates an authentication problem between your site and the ATE server. Solution: First, ensure that you have cleared the cache of all caching plugins and performed the following actions: 1. Clear WPML cache 2. Synchronize local job ids with ATE 3. Synchronize local job ids with ATE jobs 4. Synchronize posts taxonomies 5. Fix post type assignment for translations If the issue persists, we recommend updating WPML to the latest version to ensure compatibility and functionality. If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, 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 problems continue, we highly recommend opening a new support ticket with us for further assistance.
Problem: If you're receiving a message that the REST API is not enabled and have tried deactivating all plugins except Elementor, checked your .htaccess file, and re-saved your permalinks without resolving the issue, the problem might still persist even if an endpoint test shows a correct result. Solution: We recommend trying to access your site using a private browser window. This approach resolved the issue for another client, indicating that the problem could be related to browser caching rather than your WordPress setup or WPML configuration.
Please note that this solution might be irrelevant if it's 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.
Problem: The client reported that the JavaScript file 'wpgmp-project-filters.js' was not loading on their site's translated pages for German (de), French (fr), Norwegian (no), Danish (da), and Swedish (sv) languages, although it was loading correctly for English (en), Dutch (nl), and Spanish (es). Solution: Initially, we suggested clearing all caches (plugin, server, Cloudflare, etc.) to see if that resolved the issue. Upon further investigation, we discovered that the problem was due to custom code in the file
wp-content/themes/kebonyglobal/functions.php
. Specifically, the function
kebony_relocate_inline_scripts()
contained a line of code that needed commenting out:
// strpos($src, 'project') !== false ||
After making this change, the JavaScript file should load correctly on all language versions of the site.
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 persist, please open a new support ticket.
Problem: Le client rencontre des problèmes avec l'ajout d'éléments à la liste de traduction et la traduction manuelle sur Elementor, où les actions ne se complètent pas et les pages se rafraîchissent sans résultat. De plus, des erreurs 504 liées à Cloudflare apparaissent lors de l'accès à certaines pages de l'administration WPML. Solution: 1. Nous avons identifié un conflit potentiel avec les connexions IP et Cloudflare qui pourrait affecter les fonctionnalités de WPML. Nous recommandons de tester à nouveau le problème de traduction et de fournir un enregistrement vidéo ou un guide étape par étape pour reproduire le problème. 2. Un problème spécifique a été résolu en supprimant les balises HTML incompatibles d'un champ de texte, ce qui a permis à la traduction de fonctionner correctement. Pour les styles, il est conseillé de les appliquer via un widget bouton normal sans inclure de HTML dans les champs de texte. 3. Pour les liens partiels non traduits automatiquement par WPML, trois solutions sont proposées : remplacer par des liens complets, utiliser des liens dynamiques pour pointer vers les taxonomies souhaitées, ou traduire manuellement les liens. La solution des liens dynamiques est recommandée pour une meilleure stabilité et synchronisation automatique. 4. Pour les modèles bloqués dans la traduction, une duplication manuelle et un renvoi à la traduction ont été nécessaires.
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.
