ATE

Problem:
Der Kunde versucht, die automatische Übersetzung auf seiner Website zu starten, aber die Übersetzungswarteschlange bleibt bei 0% und wird nicht abgearbeitet.
Solution:
Wenn Sie ähnliche Probleme erleben, empfehlen wir Ihnen, ein Datenbank-Backup zu erstellen und das Adminer-Plugin zu verwenden, um bestimmte Einträge in der

wp_options

Tabelle zu löschen. Die zu löschenden Einträge sind:

WPML_TM_AMS

,

WPML_SITE_ID:ate

und

WPML_SITE_ID:global

. Nachdem diese Einträge gelöscht wurden, sollten Sie versuchen, die automatische Übersetzung neu zu starten.
Es könnte auch hilfreich sein, den Schlüssel für Ihre Website zu entfernen und erneut hinzuzufügen, insbesondere wenn der Schlüssel veraltet ist. Weitere Informationen finden Sie hier: https://wpml.org/faq/how-to-remove-the-this-site-is-registered-on-wpml-org-as-a-development-site-notice/#what-if-the-notice-still-appears-after-moving-to-production

Diese Lösung könnte veraltet sein oder nicht auf Ihren Fall zutreffen. Wir empfehlen Ihnen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu bestätigen 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:
Hai creato una nuova pagina sul tuo sito web e richiesto la traduzione automatica. Dopo l'acquisto dei crediti, la traduzione rimane in sospeso con lo stato da aggiornare. Il problema è che il nostro server di traduzione ha un limite di 4000 segmenti per post, e la tua pagina supera questo limite.
Solution:
Una soluzione rapida potrebbe essere rimuovere la lista dei comuni dalla pagina, permettendo così al sistema di procedere con la traduzione. Alternativamente, potresti rimuovere il campo problematico e poi riaggiungerlo manualmente nelle traduzioni. Se queste soluzioni non sono applicabili o sufficienti, ti consigliamo di verificare i problemi noti e di assicurarti di avere installato le ultime versioni dei temi e dei plugin. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.

Problem:
The client was manually translating a page on their site, which they had done successfully for over 1,500 pages. However, one specific page was not displaying its content in the translation, showing only the title, SEO fields, and URL. The client tried deleting the translation and starting over, as well as updating the content to force a content recheck. They installed the WPML String plugin, but it did not resolve the issue. Eventually, the client created a new page from scratch, duplicated the content, and translated it successfully.
Solution:
We noticed that the client was using a Blog license, which lacks additional addons for page builders and automatic translation. We recommended upgrading the license to CMS to use automatic translation features and ensuring all plugins are updated to the latest versions. For manual translation, especially with page builders like Elementor, we advised following the specific guidelines provided in our documentation:
https://wpml.org/documentation/plugins-compatibility/elementor/translate-elementor-site-wpml-multilingual-blog/

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 at our support forum.

Problem:
You are unable to save translations in WPML because the HTML entity   is required in French for spacing before colons, but not in English, causing issues when translating and saving content.
Solution:
We acknowledge that WPML currently expects translations to maintain the same HTML markers across languages. We have noted your feedback for a feature request to change this behavior. In the meantime, we recommend two workarounds:
1. Use CSS to hide the   entity in the English version of your content. This approach allows you to maintain the entity in French while visually omitting it in English.
2. Consider using a manual translation method for pages where this issue persists. You can find more information on using different translation editors here: Using Different Translation Editors for Different Pages.

If this solution does not apply to your case, or if it becomes 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 do not hesitate to open a new support ticket at WPML Support Forum.

Проблема:
Клиент использует WPML для перевода статей и сталкивается с ошибкой при сохранении некоторых статей в редакторе переводов.
Решение:
1. Внесите любое незначительное изменение в оригинал страницы и обновите её.
2. Зайдите в редактор переводов WPML снова или перейдите в WPML → Translation Management и отправьте страницу на перевод, затем снова войдите в редактор переводов.
3. Мы обновили редактор переводов WPML, поэтому рекомендуем обновить оригинал проблемной страницы с внесением незначительного изменения и затем зайти в редактор переводов WPML.

Если проблема сохраняется, рекомендуем проверить известные проблемы и убедиться, что у вас установлены последние версии тем и плагинов. Если это не помогает, пожалуйста, откройте новый тикет поддержки.