Problem: The client is unable to log in to their website due to a fatal error indicating that the allowed memory size has been exhausted. Solution: We recommend checking with your hosting provider as the issue might be related to server/hosting settings which they can address. Additionally, you can search through existing support tickets for potential solutions using this custom search URL: WPML support tickets. Ensure that your server meets our minimum requirements. Make sure to update your WPML plugins to the latest version by going to Plugins > Add new > Commercial > click on "check for updates".
If the solution provided here is not relevant to your situation, or if it's outdated, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
Problema: Las categorías de productos no se muestran en las páginas de inicio traducidas.
Solución: Si estás experimentando este problema, te recomendamos seguir estos pasos: 1. Ve a WooCommerce >> WooCommerce Multilingual >> pestaña de Configuración >> enlace de Solución de problemas (abajo a la derecha) y selecciona las siguientes opciones:
Sincronizar variaciones de productos
Reparar relaciones de variaciones traducidas
y haz clic en el botón 'Iniciar'.
2. Si el problema persiste, sigue estos pasos: 2.1. Ve a WPML >> Soporte >> página de Solución de problemas y presiona los siguientes botones:
Limpiar la caché en WPML
[Productos] Sincronizar taxonomías de entradas
Sincronizar identificadores de trabajos locales con trabajos de ATE
Sincronizar traductores y gestores de traducción con ATE
Asignar estado de traducción al contenido duplicado
Establecer información de idioma
En el caso del cliente, realizamos los siguientes pasos adicionales: - Abrimos la versión en inglés de la página en el editor de Elementor, ya que se estaba actualizando manualmente la traducción. - Seleccionamos 'categorías de productos' en las opciones del widget Carousel, ya que estaba configurado como predeterminado. - Después de actualizar la página y limpiar las cachés del frontend, las miniaturas de las categorías comenzaron a mostrarse correctamente.
Si la solución proporcionada no es relevante para tu caso, porque podría estar desactualizada o no aplicarse a tu situación, te sugerimos abrir un nuevo ticket de soporte. Te recomendamos encarecidamente que revises los problemas conocidos, verifiques la versión de la solución permanente y confirmes que has instalado las últimas versiones de los temas y plugins. Si necesitas asistencia adicional, no dudes en contactarnos en el foro de soporte de WPML.
Problem: The client was experiencing issues with some sections breaking when translating the shop page, and some texts on the checkout page were not being translated. Solution: 1. Navigate to WPML-> Theme and plugins localization, select your theme/plugin, and scan for strings. 2. Go to WPML-> String Translation. 3. Click on the "Translate texts in admin screens »" link. 4. Search for the needed strings. 5. Select the strings you want to translate. 6. Click on the "Add to String Translation" button. 7. Return to the String Translation page by clicking on the "« Return to String Translation" link. 8. Translate the strings, clear your cache, and then check the front end.
Additionally, we confirmed that the products in both languages are working correctly.
Lastly, we requested the client to share their Debug information to better understand the site's configuration. Instructions on how to provide this information can be found here.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, 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 you still need assistance, please don't hesitate to open a new support ticket with us.
Problem:
The client needed assistance with translating the Cartflows Store Checkout page as there were no visible translation options. Solution:
Step 1: We navigated to WPML > Settings > Custom Fields Translation and enabled the option
Show Multilingual Content Setup meta box on the post edit screen
. This action allows the custom fields for each content to be visible at the bottom of the WordPress Editor. For further guidance, we provided a link to the documentation: Translating Custom Fields.
Step 2: On the Checkout Page Editor, we configured the fields for options and layout to
copy
and text fields to
translate
, thus opening up the translation.
Step 3: If there are still missing strings for translation, we advised the client to identify which fields control the text and set them to
translate
.
Additionally, we noted that the client switched the translation method to
Classic Translation Editor
at WPML > Settings > Translation Editor. We reminded the client that translations made in the Classic Translation Editor are not available in the Advanced Translation Editor (ATE). If issues arise with ATE, we recommended clearing the browser's cache and trying again. If problems persist, we advised the client to inform us.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If so, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
Problem: The client is experiencing a critical error on their website after installing the WPML String Translation plugin. Solution: We recommend enabling the WordPress debug log to identify the specific PHP error causing the issue. To do this, edit the
wp-config.php
file in the WordPress directory and insert the following lines:
After adding these lines, try to reproduce the issue. The debug log will be located in
/wp-content/debug.log
. The client should then paste the content of the debug log on a site like pastebin.com and share the link with us for further assistance. Relevant Documentation: https://codex.wordpress.org/Debugging_in_WordPress
If the provided solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, 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 contact us in the WPML support forum.
