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.
Problem: Nach dem Umzug einer Website auf eine andere Domain tritt ein Fehler auf, weil die Tabelle 'dbs15205574.wp_icl_strings' nicht existiert, auch nachdem sie manuell hinzugefügt wurde. Solution: Wenn möglich, führen Sie die Migration der Website erneut durch, idealerweise mit dem Plugin All In One WP Migration oder Duplicator, da diese gut mit WPML funktionieren. Sollte eine erneute Migration nicht möglich sein, entfernen Sie die manuell erstellte Tabelle und wenden Sie die Lösung aus dem folgenden Link an: https://wpml.org/errata/missing-_icl_strings-_icl_string_translations-data-tables/ Stellen Sie sicher, dass Sie ein vollständiges Backup Ihrer Website haben, bevor Sie eine dieser Lösungen umsetzen.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues 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 Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: El cliente, monicaG-12, enfrenta un problema recurrente donde los textos en su sitio web cambian automáticamente a pesar de estar correctamente traducidos en WPML. Este problema persiste incluso después de desactivar plugins, actualizarlos y borrar cachés. Las cadenas problemáticas están relacionadas con el tema Astra y no se detectan ni registran correctamente en la Traducción de Cadenas de WPML.
Solution: 1. **Actualizar todos los plugins y temas**: Es crucial mantener todo el software actualizado para evitar conflictos y errores. Actualizar aquí. 2. **Desactivar Premmerce Permalink Manager for WooCommerce**: Este plugin no es compatible con WPML y puede estar causando conflictos. Más información aquí. 3. **Re-registrar las cadenas problemáticas**: Eliminar y volver a registrar las cadenas en WPML puede resolver el problema de visualización incorrecta. 4. **Instalar un plugin de monitoreo**: Para identificar qué cambios podrían estar disparando el problema, se instaló Activity Log Pro.
Si estas soluciones no resuelven el problema o si el problema persiste, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos relacionados en WPML Known Issues y confirmar que tienes instaladas las últimas versiones de temas y plugins. Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte.
Problem: The client reported that category images on translated category pages were not displaying, showing a placeholder image instead, despite working correctly for years. This issue seemed to occur after recent updates. Solution: We recommended the following steps to resolve the issue: 1. Navigate to WPML → Settings → Custom Term Meta Translation. 2. Click on Show system fields to make it visible if it isn't already. 3. Set the custom fields
z_taxonomy_image
and
z_taxonomy_image_id
to Copy. 4. Return to Products → Categories, edit the category in the main language, and save it. This should ensure that the thumbnail appears correctly in all translations. Note: It is important to edit and save each category individually in the main language, as bulk actions could cause the thumbnails to disappear again.
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 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing 404 errors on the order confirmation page and the endpoint 'order-paid' in translations. The issue temporarily resolves by saving the permalinks but reoccurs the next day. Deactivating the WPML String Translation plugin stops the error. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Navigate to WPML → String Translation and ensure that the endpoints are set to their original English values (not translated). 2. Save the permalinks again to resolve the current 404 errors. 3. Return to WPML → String Translation and translate the endpoints as needed. Important: After translating the endpoints, please do not save the permalinks again. We are aware of this issue and are actively working on a permanent solution.
We already have a development ticket for this problem and are actively working on a permanent solution in future releases.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues 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 here.
