Problem: Nach der Migration von Divi 4 auf Divi 5 treten Probleme bei bestehenden Übersetzungsaufträgen auf, einschließlich der Unmöglichkeit, Aufträge zu übersetzen oder zu löschen, sowie 'Critical Errors' bei einigen Übersetzungen. Solution: Die Migration von Divi 4 zu Divi 5 verändert die interne Datenstruktur der Inhalte, wobei Inhalte von verschachtelten Shortcodes zu einem JSON-basierten Format wechseln. Dies kann Probleme bei alten Übersetzungs-Jobs verursachen, die noch auf der alten Shortcode-Struktur basieren. Um diese Probleme zu beheben, empfehlen wir: 1. Versuche, die hängenden Jobs unter WPML > Translation Dashboard > Jobs abzubrechen. 2. Wenn das nicht funktioniert, erstelle neue Übersetzungsaufträge für die betroffenen Inhalte unter WPML > Übersetzungsdashboard. 3. Eine weitere Möglichkeit könnte sein, die originalen Inhalte in Divi zu bearbeiten und erneut zu speichern, um die Struktur zu aktualisieren. Weitere Informationen zur Kompatibilität und Migration findest du hier: https://wpml.org/errata/divi-5-wpml-compatibility-while-new-features-are-being-released/
Falls diese Lösungen dein Problem nicht beheben oder die Informationen veraltet erscheinen, empfehlen wir, einen neuen Support-Ticket zu ö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 du die neuesten Versionen von Themes und Plugins installiert hast.
Problem: The client reported that Google only indexes the English pages of their multilingual site, even when manually indexing other languages. The '/EN/' slug appears despite other languages being set up, and WPML is configured correctly.
Solution: We recommended the following steps to address the issue: 1. Ensure the WPML SEO Add-on is active by checking under Plugins → Installed Plugins. If not present, install and activate it from Plugins → Add New → Commercial tab. 2. Verify the presence and correctness of 'hreflang' tags on translated pages by viewing the page source and searching for 'hreflang'. 3. Check the WPML's Language URL format under WPML → Languages and ensure 'Different languages in directories' is selected. 4. Disable the Browser Language Redirect temporarily under WPML → Languages to avoid confusion during indexing. 5. Re-save permalinks under Settings → Permalinks and re-submit sitemaps in Google Search Console.
Additionally, we advised against using the Browser Language Redirect feature as it does not distinguish between users and search engine bots, which can affect SEO and indexing. This is documented in our guides:
If these steps do not resolve the issue or if the information seems outdated, we highly recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum.
Problem: The client updated internal links and content in posts, resulting in up to 50% of segments showing an orange bar and being untranslated or needing re-approval. This issue did not occur previously and was suspected to be related to recent server issues. Solution: The issue was due to the site not being properly registered and migrated between different environments (WPML test site, staging site, and production site). The site was moved, creating a new entry instead of copying the existing translation memory. We resolved this by manually merging the translation memory of all site organizations into the current one. The client should now cancel any affected 'In Progress' jobs at WPML > Translation Dashboard > Jobs, and create new jobs for the affected contents at WPML > Translation Dashboard. Assign the translations to yourself and access them at WPML > Translations. We have already applied this solution to the 'Best of Nightlife and Bars in La Spezia' and confirmed a 100% completed translation on ATE. Please verify if the issue is resolved by creating new translation jobs, as changes might not be visible on jobs currently in progress.
If this solution does not apply to your case, or if it seems outdated, we 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 WPML support forum.
Problem: Il cliente ha riscontrato due problemi critici nel sito multilingue: 1. Le variazioni WooCommerce non appaiono nella versione spagnola del sito. 2. I campi personalizzati del plugin Advanced Product Fields for WooCommerce non sono traducibili in WPML. Solution: Per il primo problema, abbiamo suggerito di verificare che i prezzi siano sincronizzati e di utilizzare gli strumenti di "Risoluzione dei problemi" in WooCommerce Multilingual per sincronizzare le variazioni e rigenerare le tabelle di ricerca. Per il secondo problema, abbiamo identificato che il campo _wapf_fieldgroup può essere impostato su 'Copy' per copiare il gruppo di campi nel prodotto tradotto. Tuttavia, i label, le istruzioni e i placeholder dei campi non possono essere tradotti con WPML a causa della loro struttura interna serializzata.
Se questa soluzione non risolve il tuo problema o sembra non essere più attuale, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di controllare le questioni note e di verificare che tu abbia installato le versioni più recenti dei temi e dei plugin. Per assistenza ulteriore, visita il forum di supporto WPML.
Problem: When editors add and crop a featured image to an original post, the translated post does not receive the cropped version of the featured image. This issue persists despite expectations for a fix in version 4.7. Solution: We have confirmed that this is a known limitation where image metadata does not sync after edits to attachments that already have translations. Currently, there is no immediate development scheduled for this issue due to its complexity and relatively low impact. We recommend using the suggested workaround available at https://wpml.org/errata/cropped-featured-image-not-displayed-in-translations/.
If this solution does not apply to your case, or if it seems outdated, we encourage you to 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. For further assistance, please visit our support forum at https://wpml.org/forums/.
Problem: Der Kunde hat festgestellt, dass die wp_options Tabelle mehrere große Einträge von WPML enthält, die zusammen etwa 275 KB ausmachen. Dies erscheint ihm sehr viel und er schlägt vor, dass die WPML Entwickler sich insbesondere um die Reduzierung der wp_installer_settings kümmern. Solution: Wir haben das Problem bereits erkannt und in unserem Errata dokumentiert: https://wpml.org/errata/big-size-for-wp_installer_settings/. Anpassungen wurden bereits umgesetzt und werden mit WPML 4.9 veröffentlicht.
Falls diese Lösung für Sie nicht relevant ist oder veraltet erscheint, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen zu überprüfen: https://wpml.org/known-issues/, die Version der dauerhaften Lösung zu überprüfen und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: The client is experiencing issues with locked fields in WPML and has concerns about the translation of the footer, which does not display correctly across different language versions of the site. Solution: We clarified that the locked fields can be unlocked simply by clicking on the 'lock' icon. Regarding the footer, it appears that the client had previously attempted to fix the issue by deleting the translated footer template directly from the database. However, this did not resolve the problem as the footer still does not appear correctly. We suggested that the footer's translation issue might be due to the limitations described in the WPML errata for the Pro theme, where layout texts are not translatable via the WPML Translation Editor (https://wpml.org/errata/pro-theme-layout-texts-not-translatable-via-wpml-translation-editor/). The client can either manually translate the template or apply custom code to make it compatible with String Translation. We asked the client to confirm if they intend to use String Translation for the footer in the same way as the “Object (CPT) – Single View” template.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues (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.
Problema: Cuando traduces de español a catalán los títulos H1, H2, H3, H4, H5 y H6 que contienen apóstrofes, estos se convierten en código ASCII. Solución: Primero, verifica la versión de WPML que estás utilizando. Si encuentras que no es la más reciente, te recomendamos actualizar todos los plugins a la última versión disponible. Esto debería resolver el problema de los apóstrofes que se muestran como entidades HTML. Puedes revisar y seguir las instrucciones específicas para este problema en la página de erratas de WPML: https://wpml.org/errata/divi-button-apostrofes-display-as-html-entities/
Si después de actualizar continúas experimentando este problema, o si la solución proporcionada se ha vuelto irrelevante debido a actualizaciones o cambios en tu caso específico, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos verificar los problemas conocidos en https://wpml.org/known-issues/, confirmar la versión del arreglo permanente e instalar las últimas versiones de temas y plugins.
Problem: If you're experiencing a critical error when trying to access WPML -> Theme and Plugins Localisation, it might be due to a known issue. Solution: We recommend applying the fix detailed on our errata page. Please visit https://wpml.org/errata/flux-checkout-fatal-error-uncaught-valueerror-unknown-format-specifier-t/ and follow the instructions provided there to resolve the issue. After applying the fix, you should be able to access the Theme and Plugins Localisation option without encountering the critical error.
Please note that this solution might be irrelevant if it's 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 problem persists, please open a new support ticket.
