Documentation request

Problema:
Estás intentando traducir los emails de WooCommerce en tu sitio y desde que conectaste con woo.com para activar un plugin, las traducciones al castellano de los emails han desaparecido. No encuentras las cadenas en inglés de ciertas partes de casi todos los emails de WooCommerce, a pesar de haber escaneado de todas las formas posibles.
Solución:
Si estás experimentando este problema, te recomendamos seguir los pasos descritos en la guía de cómo traducir los emails de WooCommerce, disponible en https://wpml.org/documentation/related-projects/woocommerce-multilingual/how-to-translate-woocommerce-emails/. Además, te sugerimos revisar la guía sobre cómo encontrar y traducir cadenas que no aparecen en WPML -> Traducción de Cadenas, que puedes encontrar aquí: https://wpml.org/es/documentation-2/guia-de-inicio/traduccion-de-cadenas/buscar-cadenas-que-no-aparecen-en-la-pagina-traduccion-de-cadenas/.
Esta solución podría ser irrelevante si ya está desactualizada o no se ajusta a tu caso. Te recomendamos verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Si el problema persiste, te sugerimos abrir un nuevo ticket de soporte. También te recomendamos revisar los problemas conocidos en https://wpml.org/known-issues/. Para más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.

Problem:
The client is experiencing a 'Download failed. (Forbidden)' error when attempting to update or download WPML plugins, even after deregistering and registering the sitekey.
Solution:
1. Revalidate your domain with your sitekey by navigating to https://wpml.org/account/sites/ and copying the sitekey created for your domain. Then, go to WP > Plugins > Add new > Commercial Tab > Deregister and register the sitekey again.
2. If the issue persists, manually install the plugin. Download WPML manually by visiting https://wpml.org/account/downloads/, scroll down, and click on 'Download WPML manually'. Then, in your WP dashboard, navigate to WP > Plugins > Add new and upload the downloaded zip file directly.

If these steps do not resolve your issue, or if the solution becomes 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 you still encounter problems, please open a new support ticket at WPML support forum.

Problem:
The client needed to enable automatic translation for post content while disabling it for String Translations in the WPML plugin.
Solution:
We advised the client to use the Translation Management dashboard (WPML -> Translation Management) to control which content should be translated. Specifically, to disable automatic translation for strings, the client should not select them in the dashboard. For detailed guidance, we recommended reading the Translation Management guide.

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 further assistance is needed, please open a new support ticket.

Problem:
Estás experimentando un error 404 en las páginas traducidas de tu sitio web principal, específicamente en los idiomas inglés y portugués, incluso después de actualizar los enlaces permanentes. Además, mencionaste que desactivaste WPML Media Translation, WPML SEO y WPML String Translation, lo cual resolvió temporalmente el error.
Solution:
Si estás enfrentando este problema, te recomendamos seguir estos pasos:
1. Ve a WPML → Configuración → Traducción de taxonomías.
2. Haz clic en Guardar, asegurándote de que el slug de la categoría de producto esté correctamente traducido.
Para ayudarte mejor, hemos preparado un video con los pasos que puedes seguir: https://komododecks.com/recordings/Cv22QxJxc02DdVPdAN34

Es posible que esta solución pueda ser irrelevante debido a que está desactualizada o no se aplica a tu caso. Si después de seguir los pasos el problema persiste, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos 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.

Problem:
The client's website front page is not translated using WPML, despite the rest of the site being translated. The site uses Composer, not a page builder, which complicates the translation process as Composer handles content differently.
Solution:
1. Increase the memory limit of the site as it is currently set to 40M, which might be insufficient.
2. Use the WPML String Translation to handle the translation of the front page. Specifically, navigate to String Translation > Admin strings, register all homepage content, and then either send it for translation or translate it manually. More details on this process can be found here.
3. If the theme is claimed to be multilingual-ready by the author, ensure it is compatible with WPML's String Translation. If issues persist, contact the theme author for more detailed guidance on translating the theme.

Please note that this solution might be outdated or not applicable to your specific 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:
The client activated the Arabic translation for their English website using WPML. However, the translated pages, menu, header, and footer were only visible when logged in as an admin. When logged out, the Arabic content disappeared and was inaccessible even via direct URL.
Solution:
1. We recommended checking if the Arabic language was set as hidden in WPML -> Languages -> Hidden languages. If not hidden, we advised ensuring that the translated homepage was published by filtering pages by Arabic and checking the publish status.
2. We suggested increasing the WordPress memory limit to at least 128MB by adding the following code to wp-config.php:

This code should be placed above the line /* That's all, stop editing! Happy blogging. */.
3. We also recommended creating a staging site to safely test changes without affecting the live site. This could be done using the WP Staging plugin or by authorizing us to create one.
4. After further investigation, we found that the 'Copyrights' string in the footer was incorrectly translated because the Arabic translation didn't contain the necessary variables. Deleting the incorrect Arabic translation resolved the issue.
5. For issues with the Revolution Slider not displaying correctly, we advised following the steps in our documentation on creating multilingual sliders with Revolution Slider and WPML, ensuring to use only one slider with slides assigned to both English and Arabic languages.

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.