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 is experiencing an issue where special characters like the en dash (–) are being replaced by a regular hyphen (-) in translations using WPML. This alteration occurs regardless of the translation method used, affecting the intended formatting of product titles and descriptions.
Solution: We conducted detailed tests using both automatic and manual translations across different language pairs and translation services. Here are the findings: 1. When using PTC for translations, the issue does not occur. The en dash remains unchanged in both the Advanced Translation Editor (ATE) and on the frontend. 2. When using DeepL, the en dash is replaced by a regular hyphen in the ATE, but it displays correctly as an en dash on the frontend. This inconsistency is due to DeepL's internal grammar rules, which we cannot alter.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, please check the related 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, visit our 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.
