Problema: El cliente ha traducido una plantilla en Bricks Builder usando el Traductor avanzado de WPML y aunque la plantilla aparece traducida en el backend, no se muestra correctamente en el frontend al cambiar de idioma. Solución: Actualmente, existe un problema conocido con el tema Bricks donde las traducciones realizadas con el Editor de Traducción Avanzada no se muestran correctamente en el frontend. Para más información, por favor consulta el siguiente enlace de Errata: https://wpml.org/errata/bricks-translated-content-not-showing-on-frontend/. Te recomendamos seguir el método alternativo mencionado en la Errata y volver a traducir la plantilla. Sin embargo, también puedes optar por duplicar la plantilla para traducirla.
Si esta solución no es relevante debido a que está desactualizada o no se aplica a tu caso, te sugerimos abrir un nuevo ticket de soporte. Te recomendamos encarecidamente revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Si necesitas más ayuda, por favor visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: You are using WPML to translate content from German to French, and some images are not displaying on the translated pages. The issue is due to broken image links where the 'uploads' folder is missing from the URL. Solution: We recommend checking the format of your image links to ensure they include the 'uploads' folder. This problem might be related to a known issue with SVG support when WPML Media is activated, which strips the 'uploads' folder from the SVG image URL. For a workaround, please visit the following documentation: WPML Errata on SVG Support.
If this solution does not apply because it is outdated or not relevant 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 issues persist, please open a new support ticket at WPML Support Forum.
Problem: The client is experiencing issues with a site built using Kadence and Beaver Builder, where the translation lost text formatting, resulting in a block of text instead of paragraphs. Additionally, the mobile CTA button from Kadence Conversions is displayed on all screen sizes, not just on mobile, and editing the French Conversion version causes a 500 Internal Server error. Solution: For the issue of lost text formatting, we recommend disabling the option "I prefer bigger segments" in the Advanced Translation Editor as it might be causing the line breaks to be ignored. You can find more details and workarounds on this issue at https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/. Regarding the mobile CTA button displaying on all screen sizes, please ensure that Kadence Conversions is compatible with WPML and check any specific settings within Kadence Conversions that might be affecting visibility across different devices.
If these solutions do not resolve your issues or if the information provided 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.
Problem: You added three new pages to your website and attempted to translate them. However, a code script used for a form is incorrectly appearing on the front end of other translated pages. Solution: First, ensure that the translated pages are displaying correctly by visiting them. We have disabled the 'I prefer bigger segments' option and updated the page in the default language along with its translations. It's important to check if this adjustment resolves the issue. For further details, you can refer to our documentation on similar issues here: WPML Errata Page.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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 contact us through our support forum at WPML Support Forum.
Problem: The client was experiencing an issue where attempting to order a product with only 1 in stock resulted in an error, and it appeared as though two orders were created, but only one was processed in the admin. This occurred when WPML String Translation was enabled, and there was also a problem with the refund process when WPML Multilingual CMS was active. Solution: We identified a PHP fatal error related to a format specifier in the WooCommerce email notification system. The error was traced to a translation string for the 'out of stock' message in WPML String Translation, which had an incorrect format. We corrected the translation from "Níl stoc de % againn." to "Níl stoc de %s againn." and verified that the checkout and refund processes functioned correctly thereafter. For further details on this type of error, you can refer to the documentation at https://wpml.org/errata/php-8-php-fatal-error-uncaught-valueerror-unknown-format-specifier-in/.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
