Problème : Le client a rencontré des problèmes avec la traduction des termes meta et des attributs produits WooCommerce sur son site, avec des comportements incohérents et des erreurs de mémoire PHP lors de l'utilisation de WPML. Les vérifications ont montré que les configurations et les relations de traduction étaient correctes, mais le problème persistait, indiquant un problème lié à la limite de mémoire PHP.
Solution : Nous avons identifié que le problème était lié à la limite de mémoire PHP sur le serveur du client. Pour résoudre ce problème, nous avons augmenté la limite de mémoire PHP et ajusté la configuration du serveur en conséquence. Nous avons également optimisé la configuration du site selon vos recommandations. Si vous rencontrez des problèmes similaires, nous vous recommandons de vérifier et d'augmenter la limite de mémoire PHP de votre serveur et de vous assurer que votre configuration est optimisée pour l'utilisation de WPML.
Il est possible que cette solution ne soit plus pertinente en raison de mises à jour ou de différences dans votre cas spécifique. Nous vous recommandons vivement de consulter les problèmes connus, de vérifier la version des correctifs permanents 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 sur notre forum de support.
Problem: The client is experiencing issues with the 'Automatic Translation Management' section in their WPML account. These include duplicate and ghost entries for the domain developress.pp.ua in the credit management dashboard, with one entry showing 2,000 credits and another showing 60,020 credits but with an invisible domain name. Additionally, the registered site fitolavka.shop does not appear in the Credit Management section, and the client is unable to withdraw credits, receiving an error message. Solution: We have added the credits from the ghost entry back to the client's account and rounded it up for the inconvenience. However, we do not have clearance to fix this issue directly, so we escalated the ticket for further resolution. The client should expect a delay due to a higher than usual queue, but we will keep them posted on the progress.
Please note that this solution might be 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 issue persists, please open a new support ticket at WPML support forum.
Problem: Si estás experimentando un error crítico al intentar editar o crear la versión en euskera de una página en WPML, y la página en cuestión no puede desvincularse desde la interfaz, es posible que la vinculación actual esté corrupta. Este problema puede ocurrir tanto al intentar crear la traducción desde el español original como desde otra traducción. Solution: En un caso similar, descubrimos que el problema estaba relacionado con una entrada corrupta en la base de datos de WPML, específicamente con un elemento global de Avada. Eliminamos la entrada defectuosa, lo que permitió que el sistema volviera a funcionar correctamente y las traducciones se pudieran desconectar sin inconvenientes. Te recomendamos verificar si existe una situación similar en tu caso. Si no estás seguro de cómo proceder o si el problema persiste, te sugerimos abrir un nuevo ticket de soporte. Además, te recomendamos encarecidamente revisar los problemas conocidos relacionados, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Si necesitas asistencia adicional, no dudes en contactarnos a través de nuestro foro de soporte.
Problema: Dopo l'attivazione del plugin WPML, si verifica un errore che impedisce la visualizzazione del sito. Soluzione: Il problema è causato dall'assenza delle tabelle di WPML nel database a seguito di una migrazione. Abbiamo risolto ricreando le tabelle necessarie e ricollegando manualmente le traduzioni. Questo processo non ha comportato la perdita di traduzioni. Inoltre, abbiamo effettuato un reset di WPML e fornito un video esplicativo per assisterti ulteriormente, che puoi visualizzare qui: video esplicativo.
Se la soluzione proposta non risolve il problema o se sembra non essere più attuale, ti invitiamo a verificare i problemi noti, a controllare la versione del fix permanente e a confermare che hai installato le ultime versioni dei temi e dei plugin. In caso di ulteriori difficoltà, ti consigliamo di aprire un nuovo ticket di supporto.
Problem: The client is experiencing an issue where the post category has been translated, but the translated blogs still use an untranslated path. Solution: If you're encountering a similar issue, we recommend following these steps: 1. Ensure you have a full backup of your website for safety. 2. Navigate to Settings > Permalinks and re-save your options. 3. Go to WPML > Taxonomy Translation, select Categories, and check if there's an option to synchronize them. 4. Still in WPML > Taxonomy Translation, select Categories and verify if the slug is translated by clicking on the pencil icon for the mentioned category.
If these steps do not resolve your issue, or if the solution seems 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: After migrating a website using the All In One WP Migration plugin, the client is unable to edit translations or translate new pages. Instead, they are redirected to the translation queue, and upon attempting to take and translate, they receive an error message stating 'The translator could not be assigned to the job.' Solution: We discovered a small bug related to the All In One WP Migration plugin that affected WPML's functionality. This issue has been resolved, and WPML should now function normally on your website.
If you're experiencing similar issues, we recommend checking our related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists or the solution provided here is outdated or not applicable to your case, please open a new support ticket.
Problem: The client was experiencing issues with WPML on their site after adding a card for unlimited translation. This led to the disappearance of the "translator" page and a request for a key for a translation service. Despite deactivating everything, performing a hard reset, and cleaning database tables and options related to WPML, the problem persisted. The client also noted a JavaScript file that was blocking the page. Solution: We suggested verifying if both sites (production and development) were hosted on the same server with identical CDN, dependencies, and firewall configurations. We recommended trying an older version of WPML, specifically version 4.8.6, which can be downloaded from here. If this version worked, the client could then update to the newer version. Additionally, we advised checking the WPML > Support > Installer debug to ensure the API was connected properly.
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 issue persists, please open a new support ticket at WPML support forum.
