Problema: Estás intentando traducir formularios de contacto usando el Editor de Traducción Avanzada (EAT) y no puedes pegar traducciones en la columna derecha para idiomas como coreano, hindi, chino y japonés, aunque el copiar y pegar funciona para otros idiomas. Solución: 1. Asegúrate de haber creado una copia de seguridad del sitio completo que puedas restaurar en caso de ser necesario. 2. Comparte un enlace a un video donde muestres paso a paso cómo estás intentando pegar las traducciones. Esto ayudará a identificar el problema específico.
Si esta solución no resuelve tu problema o si parece no ser relevante debido a que está desactualizada o no se aplica a tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable que revises los problemas conocidos, verifiques la versión de la solución permanente y confirmes que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
Problem: You are working on a site under development and managing a large database caused by WPML. You have a glossary that is not functioning correctly, which works on a staging site but has issues in the production environment. The main symptoms include a huge list of strings that are either not used or linked to the wrong translation data, and the glossary itself has an error preventing its use. Solution: We discovered that the English language was mapped under an incorrect language code on our servers. We corrected this mapping for your site, which resolved the glossary error. It's possible that this issue was due to human error or a technical exception.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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, please visit our support forum at WPML Support Forum.
Problème : Vous travaillez sur un site en développement et essayez de désactiver la traduction automatique dans WPML, mais bien que l'option soit désactivée, la traduction automatique fonctionne toujours. Solution : Si la traduction automatique est active lorsque vous ouvrez l'éditeur de traduction, vous pouvez cliquer sur le bouton "revenir en arrière" en haut de l'éditeur, ce qui vous montrera également une option pour la désactiver depuis cet endroit.
La capture d'écran que vous avez envoyée concerne la fonction "traduire tout automatiquement", qui envoie tout votre contenu à la traduction automatique par défaut.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de vérifier la version de la correction permanente et de confirmer que vous avez installé les dernières versions des thèmes et des plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: You are experiencing issues with custom button URLs not consistently appearing in the Advanced Translation Editor (ATE). Sometimes these URLs are visible, and other times they are not, although they can still be accessed by searching.
Solution: We have identified that links within text are typically visible, whereas links in separate fields might not show up by default but can be searched for. This behavior was previously adjusted for some page builder elements to make separate links visible by default for usability purposes. If you are noticing discrepancies between your production and development sites, it might be due to the types of links used (internal vs external). To help us investigate further and provide a more tailored solution, we recommend replicating the issue in a test site. This will allow us to examine the problem in detail.
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 for further assistance.
Problem: You are trying to translate a WooCommerce product, but a specific part of a custom field, particularly dates, does not get sent for translation. For example, the date 'New MO XX.XX.XXXX' appears as 'New MO' only in the translated output. Solution: The issue arises because the Advanced Translation Editor primarily handles text translations and may not automatically recognize numeric values or dates. We recommend using the search bar at the top right of the Advanced Translation Editor to manually search for the date and translate it. If this method does not resolve the issue, it 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 problem persists, please open a new support ticket for further assistance at WPML support forum.
Problem: You are trying to use WPML for automatic translation of your website into Korean using AI, but the system does not support Korean for AI translation. Solution: Currently, Korean is available for translation using engines other than WPML AI. We recommend using an alternative translation engine listed here: https://ate.wpml.org/mt_langs. We are planning to add Korean to WPML AI, but we do not have a specific timeline for this addition yet.
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 open a new support ticket at WPML support forum.
Problema: Il cliente ha più di 60000 crediti per tradurre contenuti con WPML, ma quando tenta di utilizzare questi crediti, WordPress indica che non sono disponibili. Soluzione: Se stai riscontrando questo problema, ti consigliamo di seguire questi passaggi: 1. Vai su Plugin → Aggiungi nuovo 2. Clicca sulla scheda Commerciale 3. Fai clic su Deregistra e poi Registra nuovamente la chiave dove hai i crediti disponibili.
Questa soluzione potrebbe non essere più rilevante a causa di aggiornamenti software o potrebbe non applicarsi al tuo caso specifico. Se il problema persiste, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di controllare le questioni note, verificare la versione della correzione permanente e confermare di avere installato le ultime versioni di temi e plugin.
Problem: The client is on a pay-as-you-go credit plan and attempted to add credit for automatic translation, but received a message indicating no credits available and an infinite spinner when trying to fix the issue. Solution: We recommend creating a backup of your site first. Then, deactivate all plugins except WPML and switch to a standard theme temporarily. This step helps in determining if there's a CSS/JS conflict preventing the pop-up from appearing correctly. If the 'fix' button still does not work, it might be due to a safe limit being hit which isn't visible due to the pop-up not appearing.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: Sie möchten das WPML-Plugin in WordPress aktivieren und den API-Code für Übersetzungen mit der CAT-Methode und DeepL einfügen. Solution: Aktuell bietet WPML keine Möglichkeit, einen eigenen API-Key für DeepL hinzuzufügen. DeepL, Microsoft Azure und Google Translate sind bereits in unseren Advanced Translation Editor (ATE) integriert, sodass Sie diese Dienste direkt nutzen können, ohne separate API-Keys eingeben zu müssen. Zusätzlich steht Ihnen die WPML-eigene Übersetzungs-Engine "WPML AI" zur Verfügung. Sie können entweder direkt im Editor mit DeepL übersetzen oder den Übersetzungsprozess vollautomatisch über das Translation Management ablaufen lassen. Weitere Informationen finden Sie unter https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/.
Falls diese Lösung für Sie nicht relevant ist, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum unter https://wpml.org/de/forums/forum/support-in-german/.
Problem: Der Kunde hat Glossar-Einträge importiert, die falsche Codierung aufweisen und viele Einträge sind fehlerhaft. Der Kunde möchte wissen, wie er alle Glossar-Einträge auf einmal löschen kann. Solution: Wenn Sie feststellen, dass die Codierung Ihrer importierten Glossar-Einträge nicht korrekt ist und Sie alle Einträge auf einmal löschen möchten, können wir dies für Sie übernehmen. Bitte bestätigen Sie kurz, dass Sie möchten, dass wir die Löschung für Sie durchführen.
Beachten Sie, dass diese Lösung möglicherweise nicht mehr relevant ist, da sie veraltet sein könnte oder nicht auf Ihren Fall zutrifft. Wir empfehlen Ihnen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten weiterhin Probleme auftreten, eröffnen Sie bitte ein neues Support-Ticket.
