Problem: Der Kunde berichtete, dass nach kleinen Textänderungen auf der Homepage die bisherigen Übersetzungen im Übersetzungseditor verschwunden sind und nur die geänderten Textstellen sichtbar waren. Es bestand Unklarheit darüber, warum 95% der Felder leer waren, obwohl nur zwei Sätze hinzugefügt wurden. Solution: Wir haben erklärt, dass im Übersetzungseditor Segmente geleert werden, wenn der originale Inhalt geändert wird. Dies könnte erklären, warum die Felder leer waren. Zusätzlich haben wir bestätigt, dass einige Inhalte zuvor im Advanced Translation Editor übersetzt wurden und der Übersetzungsspeicher in bestimmten Sprachen nicht mehr existierte. Wir haben einige Credits gutgeschrieben und die laufenden Übersetzungen automatisch abgeschlossen, um das Problem zu beheben. Für die Zukunft empfehlen wir, Änderungen im WordPress-Editor in der Zweitsprache zu vermeiden und sich an die gewählte Übersetzungsmethode zu halten. Mehr Informationen zu Credits finden Sie unter https://wpml.org/de/documentation-3/automatische-uebersetzung-fuer-wordpress-inhalte-mit-wpml/preise-fuer-automatische-uebersetzung/.
Diese Lösung könnte veraltet sein oder auf Ihren Fall nicht zutreffen. Wir empfehlen, die aktuellen bekannten Probleme unter https://wpml.org/known-issues/ zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten weiterhin Probleme auftreten, zögern Sie nicht, ein neues Support-Ticket zu eröffnen.
Problem: Ein Kunde berichtete, dass bei mehreren Posts die Überschriften in der englischen Übersetzung teilweise in der Originalsprache angezeigt werden, obwohl diese bereits vollständig übersetzt und abgeschlossen waren. Zusätzlich wurden unerwartet hohe Kosten für Auto-Übersetzungen gemeldet, die auf den Rechnungen jedoch nicht ersichtlich sind. Solution: Wir haben erklärt, dass PTC die Übersetzungen nur dann erneut überarbeiten würde, wenn nach der automatischen Übersetzung eine Änderung am Original vorgenommen wird, die ein Update auslöst. Andernfalls wird keine weitere Übersetzung gestartet. Wir empfehlen, den Usage Report zu überprüfen, wie in der folgenden Dokumentation beschrieben: https://wpml.org/documentation/automatic-translation/automatic-translation-invoices/
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem 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.
Problem: You need to change the URL translation for WooCommerce products. Solution: We recommend enabling the translation of the product slug by adjusting your WPML settings. Here’s how you can do it: 1. Navigate to WPML → Settings → Translated documents options and select the “Translate” option. This setting allows the slug to be translated manually. 2. If you are working with an existing product and its translation, trigger an update to make the slug appear in the Translation Editor by: a. Making a small change to the product description in the original language. b. Updating the product. c. Opening the Translation Editor for the translated product. After these steps, the slug field should be available for manual translation in the Translation Editor.
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.
Problem: The client was using WPML to translate products and encountered issues with the auto-translate feature stopping. The pay-as-you-go option was deactivated, and upon reactivation, the credit count appeared to reset, increasing the cost per translation. Additionally, the client faced payment issues with their credit card being rejected. Solution: We confirmed that the issues with the credit card were due to it being repeatedly rejected by Stripe and our system, requiring additional authentication from the bank. Using a different card resolved the payment issues. We also verified that the usage history and credit count did not reset after reactivating the subscription; the account continues to track prior usage. If you're experiencing similar issues, we recommend trying a different payment method if the current one fails and ensuring that your bank has authorized the transaction. For any discrepancies or further issues, 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 the problem persists, we highly recommend opening a new support ticket for personalized assistance. Contact WPML support for further help.
The client was experiencing issues with ACF fields not being translated in their products, displayed in white boxes within an Elementor Loop Grid. In the English version, these fields appeared as empty spaces. Additionally, the links within these fields did not translate correctly and targeted the original language URLs instead of the translated ones.
Solution:
We advised the client to set the 'acf_field_group' CPT to 'Not translated' in WPML > Settings > Post Types Translation, as having it set to 'translated' is not recommended. This change required re-translating the products where the ACF fields were missing.
For the links in the Elementor template, we identified a bug where the 'URL' field set to 'copy' by default was not being automatically converted.
As a temporary workaround, we suggested switching the field group to the 'Expert' mode and setting the 'URL' field translation preference to 'Translate'.
After updating the original post, the 'URL' field will appear in the translation job, allowing to manually convert the URL.
Problem: If you're experiencing repeated API errors stating 'No sitekey found for this website' when trying to translate a page or post, it indicates an issue with the sitekey in your WPML account. Solution: We recommend you try the following steps to resolve this issue: 1. Remove the old sitekey from your WPML account. 2. Navigate to Plugins → Add New and open the Commercial tab. Click on 'Unregister WPML from this site'. 3. Once the page reloads, click on 'Register WPML'. You will be prompted to enter a sitekey. Click on 'Get a key for this site'. 4. Complete the sitekey creation wizard in your WPML account and specify the site type as 'Production site'. 5. Copy the new key and paste it into the Commercial tab in the WordPress admin panel. Additionally, ensure that the REST API is enabled on your site, as it is crucial for WPML's operation. You can check the REST API dependencies here: https://wpml.org/documentation/support/rest-api-dependencies/
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. If issues persist, please open a new support ticket for further assistance.
Problem: The client is experiencing issues translating a template into five different languages. In some languages, the template appears in advanced mode, while in others, it remains in a simpler, previously used mode. Additionally, links that were translated in the simple mode are not translated in the advanced mode, and previous link translations are forgotten. Media images are also not translating, including previous translations. Solution: If you're experiencing similar issues with translating content in different modes, we recommend switching to the Advanced Translation Editor (ATE). It's important to note that any content previously translated using the Classic Translation Editor (CTE) will not automatically appear in the ATE. However, these translations should still be visible on the front-end of your site. You can manually open the translated pages on the front end and copy the content, including links, if necessary. This means that the content will need to be retranslated using the Advanced Translation Editor.
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.
