Problem: Sie haben festgestellt, dass nach der Übersetzung eines deutschen Artikels die zugeordneten Kategorien in der englischen Version verloren gehen. Zusätzlich wird die TablePress-Tabelle nicht korrekt übersetzt, sondern behält die deutsche Tabelle-ID bei. Solution: Für das Problem mit TablePress empfehlen wir, für jede Sprache eine separate Tabelle anzulegen, da derzeit keine direkte Übersetzung über den WPML Übersetzungseditor möglich ist. Weitere Informationen finden Sie in unserer Anleitung: https://wpml.org/errata/tablepress-tables-cant-be-translated/ Bezüglich der Kategorien stellen Sie bitte sicher, dass diese unter WPML > Einstellungen > Taxonomien übersetzen als "Übersetzbar" eingestellt sind. Eine detaillierte Anleitung dazu finden Sie hier: https://wpml.org/de/documentation-3/ratgeber-zum-loslegen/ubersetzung-von-beitragskategorien-und-benutzerdefinierten-taxonomien/ Sollten diese Lösungen veraltet sein oder nicht auf Ihr Problem zutreffen, 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.
Problema: Stai cercando di risolvere un problema con l'ACF Repeater sul tuo sito WordPress, dove sono presenti campi traducibili e non traducibili insieme. Il problema si verifica quando crei, elimini o sposti le righe nella traduzione principale. Soluzione: Il problema che stai riscontrando è noto e documentato qui: problema noto. La soluzione consiste nell'aggiornare la pagina facendo solo lo spostamento. È importante aggiornare prima l'originale e poi le traduzioni, assumendo che tu stia utilizzando l'editor di WPML e non quello di WordPress. Nel tuo caso, la soluzione migliore è eseguire le due operazioni separatamente: prima aggiungi il nuovo elemento, poi lo sposti.
Se questa soluzione non risolve il tuo problema o se sembra non essere più rilevante, ti consigliamo di verificare i problemi noti, controllare la versione della correzione permanente e confermare che hai 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 experiencing an issue with the event calendar on the French version of their site, where the calendar would get stuck in a loop when performing actions such as queries, searches, or date changes. This was suspected to be due to WPML translating a URL for a script incorrectly, causing JavaScript errors in the console. Solution: We suggested that the issue might be related to a known problem with The Events Calendar and custom slug translations, similar to what is described in https://wpml.org/errata/the-events-calendar-incorrect-link-format-with-custom-slug-translations/. We recommended trying the workaround mentioned there. Additionally, upon further inspection, it was found that remnants of a previous translation app in the .htaccess file were causing the issue. Removing these remnants resolved the problem.
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.
The client was unable to translate the Single Product Layout using WPML as it would freeze and changes could not be saved. Other layouts were translating without issues.
To resolve this, we recommended adding the following code to the functions.php file of the client's child theme and clearing the caches:
add_action( 'woocommerce_before_template_part', function () {
global $product;
if ( wp_is_json_request() && ! $product ) {
$random_product = new WP_Query(
array(
'posts_per_page' => '1',
'post_type' => 'product',
)
);
while ( $random_product->have_posts() ) {
$random_product->the_post();
$product_id = get_the_ID();
}
wp_reset_postdata();
$product = wc_get_product( $product_id );
}
} );
We advised the client to try translating the Product Layout again to ensure it works as expected.
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 WPML 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.
Problem: You are experiencing issues with fields not being consistently hidden in the WPML translation editor, despite setting 'wpml_cf_preferences' to specific values to control their visibility. This problem affects various field types, including dropdowns and links, and occurs even though the fields are set to translate, copy, copy_once, or not display at all. The issue persists across different testing environments. Solution: This issue is identified as a known problem with the 'Advanced Custom Fields Multilingual' plugin. A fix is scheduled for release in version 2.2.0. Until this version is available, we recommend ensuring that your fields are registered within the ACF on your wp-admin backend. For more details on this issue, please visit the errata page at Advanced Custom Fields Local Fields Translation Preference Issue for PHP Registered System Fields.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please open a new support ticket. We also 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.
Problem: Sie versuchen, WPML Translation (automatic) mit ACF Custom Fields zu verwenden, welche per PHP im Theme registriert wurden, aber die ACF-Felder werden im Backend nicht angezeigt/erkannt und können somit nicht automatisch übersetzt werden. Das Problem tritt auf, sobald Repater Fields in PHP registriert werden. Solution: Das Problem, das Sie beschreiben, ist bekannt und noch nicht gelöst. Ein Fix ist für die Version 2.2.0 von "Advanced Custom Fields Multilingual" geplant. Leider gibt es noch keinen festen Termin für das Update, da noch einige interne Tickets offen sind. In der Zwischenzeit empfehlen wir, die Felder direkt im Backend anzulegen.
Da diese Lösung möglicherweise veraltet oder nicht auf Ihren Fall zutreffend ist, empfehlen wir Ihnen, die bekannten Probleme zu überprüfen, die Version des dauerhaften Fixes zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollte das Problem weiterhin bestehen, zögern Sie nicht, ein neues Support-Ticket zu eröffnen. Besuchen Sie dazu unser Support-Forum.