Problem: You are working on a site under development and encountering an issue where 100% translations show a gear icon. You've identified an XLIFF Server Communication error and noticed that when trying to retrieve pages, you receive an 'access denied' error. The error log shows issues with the download URL from the WPML server. Solution: We recommend duplicating the problematic page for testing purposes. The issue might be caused by a large JavaScript block within an Elementor HTML widget on your page. Removing this HTML block should resolve the translation issue. Instead of embedding JavaScript directly in the page content, consider adding it via theme options or using a custom code plugin. This approach is likely to resolve similar issues on other pages, such as the homepage. Check and remove any similar HTML blocks that might be causing the problem.
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 issues persist, please open a new support ticket.
Problem: The client needed to hide a translated page that was out of date by setting it to draft. However, the link to the unpublished translation still appeared in the menu and widget language switcher, leading to a 404 error. Solution: We explained that for an admin user who is logged in, it is expected to still see language options for drafts. For non-logged-in users, only the "English" language option should be visible. Additionally, the client needs to manually adjust the menu to remove the link from the language switcher, as this is not an issue specific to WPML but a general behavior when unpublishing content.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You have hundreds of WooCommerce products in Spanish that you want to update the translations into French in bulk, for specific words. The manual translation using CTE does not support glossary. You are looking for a way to customize the 'Duplicate' method or insert a new method into the dropdown list for processing and publishing translations with specific text string replacements.
Solution: Unfortunately, customizing the 'Duplicate' method or inserting a new method directly via WPML is not possible out of the box. However, you can use the WPML's Coding API to achieve your goal. First, identify the Post IDs of the translations using the
wpml_get_element_translations
hook available at this link. Then, you can run a custom script to modify the content of these posts accordingly. It's important to note that support for custom coding is beyond the scope of our forum, and we strongly recommend testing any custom solutions on a development or staging site first.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if further assistance is needed. You can do so at WPML support forum.
Problem: You are trying to install the OTGS Installer as a plugin in WordPress, but Wordfence is blocking the installation, resulting in a 403 Forbidden error.
Solution: We recommend disabling Wordfence temporarily to proceed with the installation and activation of the OTGS Installer plugin. Once the installation is complete, you can reactivate Wordfence. This issue often arises due to tight security settings that may trigger false alarms.
Please note that this solution might be outdated or not applicable to your specific case. If this does not resolve your issue, 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 at WPML support forum for further assistance.
Problem: You are trying to register the WPML plugin but encounter a connection error: 'Unable to get data from service. Detailed error: cURL error 28: Connection timed out after 10000 milliseconds'. You want to know what causes a request timeout during registration and how to resolve a cURL error 28.
Solution: The issue might be due to a temporary slowdown between your site and WPML servers. We recommend trying to register again in a few minutes. If the problem persists, please contact your hosting provider for assistance. Additionally, you can follow these steps to potentially resolve the issue: 1. Ensure you take a full backup of your website and database. 2. Deactivate all plugins except for WPML. 3. Attempt to register WPML. 4. Reactivate other plugins. This approach helps determine if there is a conflict with another plugin or theme that might be causing the issue.
If this solution does not resolve your issue or seems irrelevant due to being 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problema: El cliente tiene configuraciones en español e inglés para su sitio web, usando 'producto' para español y 'product' para inglés. Sin embargo, la URL para los productos en inglés no se traduce correctamente, mostrando 'producto' en lugar de 'product'. Solución: Si estás experimentando este problema, te recomendamos ir a WPML -> Configuración -> Traducción de tipos de entrada y configurar los productos en la primera opción de la izquierda. Después, guarda los cambios y verifica si el problema se ha resuelto.
Si esta solución no resuelve tu problema o parece estar desactualizada, te sugerimos abrir un nuevo ticket de soporte. También recomendamos revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, puedes visitar nuestro foro de soporte.
After translating the header and footer using WPML, the header's appearance changed and the footer disappeared. Even after deleting the translations, the issue persisted.
Solution:
If you're experiencing this issue, we recommend managing your header and footer through Elementor templates. Ensure that the theme-related custom fields are set to "Copy" in the WPML settings. Here are the specific fields you should check:
wcf-addons-template-meta_type
wcf-addons-template-meta_location
wcf-addons-template-meta_splocation
After adjusting these settings, update (resave) the Header and Footer templates in both languages. This action refreshes the translation settings and should resolve the display issues in the translated versions.
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 at WPML support forum.
You need to delete specific translations for header and footer templates in your WPML site.
Solution:
First, ensure you have a full site backup. Then, follow these steps:
1. Access your Dashboard and navigate to the templates section for headers or footers. 2. Use the language switcher to select Arabic. 3. Click on the 'Published' link to view all published templates in Arabic. 4. Move the Arabic translated templates to the Trash. 5. Permanently delete them from the Trash.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/ to verify the version of the permanent fix and confirm that you have installed the latest versions of themes and plugins.
Problem: The client is experiencing issues with nonsensical redirects and mixed-up hreflang tags on their multilingual website. They are unsure if WPML or another plugin is causing these redirects and are unable to effectively troubleshoot as the redirects are only visible in the Search Console. Solution: 1. Increase the WordPress memory limit to at least 256MB by adding the following line to the wp-config.php file:
Place it above the line /* That's all, stop editing! Happy blogging. */. 2. Create a full site backup or a staging site. 3. Update any outdated plugins or themes. 4. Flush any existing cache. 5. Deactivate all plugins, including WPML, and activate a default WordPress theme like Twenty Twenty. 6. Reactivate the WPML plugins. If the issue resolves, reactivate the theme and other plugins one by one to identify the culprit. 7. Check the WPML configuration for automatic redirection based on browser language, which can be found here: Automatic Redirect Based on Browser Language. Also, investigate other plugins that might create redirects, such as Yoast.
If these steps do not resolve your issue, or if the information provided here 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. If the problem persists, please open a new support ticket with us for further assistance.
Problem: You are trying to translate the Newspaper theme's (by tagDiv) post settings using the WPML translation editor, but the translations of theme's custom fields attached to the post revert to the original language.
Solution: We have identified that the issue stems from an accompanying plugin by the theme, the tagDiv Cloud Library. To resolve this, deactivate the tagDiv Cloud Library plugin, update the translation, and then check again. This should retain the proper translated values in both the backend and frontend. If this does not resolve the issue, we recommend contacting the theme support for further assistance.
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 issue persists, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
