Problem: The client is using a multisite installation dedicated to WooCommerce and encountered an issue with the String Translation table, which could potentially become critical in the future. Solution: We suggested that the client first try translating a string on their site to check if the String Translation table is functioning correctly. If the problem persists, we recommended cloning the site to another staging environment for further troubleshooting.
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.
Problem: The client is using DeepL for automatic translations on their website with German as the default language, and includes Turkish and English. They need the English translations to consistently use American English (EN-US) due to differences in spelling and vocabulary. They are concerned that DeepL's output might default to British English (EN-GB) or be inconsistent, and they are unsure how to configure WPML's DeepL automatic translation engine to always translate to American English (EN-US). Solution: We recommend checking the translation Formality setting of the DeepL translation engine to see if adjusting it improves the results. Here is how you can adjust the Formality: https://wpml.org/documentation/automatic-translation/translate-your-wordpress-site-with-deepl/#deepl-formality Please note that WPML uses DeepL's API for automatic translations, and most of the translation processing occurs on DeepL's side, so we have limited control over the output. Additionally, WPML does not yet include a feature to provide hints to the translation engine regarding how the translation should appear. You can also experiment with custom language settings in DeepL to see if you get a translation that meets your needs. For more information on using custom languages, refer to the guide here: https://wpml.org/documentation/getting-started-guide/language-setup/editing-wpmls-languages-table/ If you want specific words to appear in a particular way, it's best to use the Glossary feature and configure how those words should be translated.
If this solution does not resolve your issue or 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 at WPML support forum.
Problem: The client is using WPML with Elementor to create a multilingual site in Spanish and Galician and wants the image gallery on their pages to automatically update across both languages when modifications are made in the main language.
Solution: To achieve automatic updates of the Elementor image gallery across languages, follow these steps: 1. Edit your gallery page in the main language. 2. Ensure the gallery uses Elementor’s Gallery widget or a compatible add-on. 3. In WPML settings, set your Pages to “Translatable – use translation if available or fallback to default language.” 4. Use the “Duplicate” option in WPML to copy the gallery content to the other language, ensuring the pages remain linked. 5. If updates are not reflecting, use the WPML Translation Dashboard to resend the page for translation or re-duplicate it.
Ensure the WPML Media Translation plugin is active for image reuse across translations. Check by editing the gallery in the main language and verifying the changes appear in the translated version.
If the solution provided here does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with translated 'account' pages showing as blank and Elementor templates and JetFormBuilder forms not displaying in French on their website. Solution: 1. Ensure that JetEngine Profile Builder pages are set as Translatable in WPML → Settings under the Post Types Translation section. 2. Verify that each account page has a French translation by checking under the French flag in Pages. Edit and update the French version if necessary. 3. If the navigation menu is missing or blank in French, go to Appearance → Menus, select the French menu, and ensure all relevant profile/account pages are added and published in French. 4. Use WPML → String Translation to translate any static or dynamic text, such as menu labels or JetEngine-generated elements. 5. Set Elementor templates and JetFormBuilder forms to Translatable under Post Types Translation in WPML → Settings. Check for French translations in Templates → Saved Templates and JetFormBuilder → Forms, and add or review the translation as needed. 6. Use the Advanced Translation Editor to verify and publish the translation. 7. Clear any site or browser cache if the preview still does not show the template in French. 8. If issues persist, consider switching to the parent theme temporarily to rule out issues with child theme customizations.
If after following these steps the issues persist, or if you encounter any error messages or blank content, it might be necessary to consult further with our support team. 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 the problem continues, please open a new support ticket at WPML support forum for personalized assistance.
Problem: The client is experiencing an issue where ACF fields in the hero layout become readonly on a translated page, despite being set to 'Copy Once'.
Solution: 1. Verify that the ACF field and its sub-fields within the Flexible Content field are set to 'Copy Once' in WPML → Settings → Custom Fields Translation. 2. Ensure you are using the WordPress Editor to translate the page. If using the WPML Translation Editor, switch to the WordPress Editor by clicking the pencil icon next to the translation and selecting the WordPress Editor. 3. After switching, check if the hero layout ACF fields are editable on the translated page. If they remain readonly, review the field group settings in ACF → Field Groups to confirm correct translation preferences. 4. If issues persist after these steps, remove the translation and recreate it using the WordPress Editor to correctly apply the 'Copy Once' setting.
If the solution provided does not resolve your issue or seems outdated, we recommend opening a new support ticket for personalized assistance. Additionally, please check related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and confirm the version of the permanent fix. For further support, visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You are trying to display a custom field translated by WPML on your website. The field is a Repeater field in ACF, and it should show translated data on the English version of the post. However, the translated data for the ACF Repeater field is not displayed correctly; only the title 'Environment' appears in English, while the Polish version displays detailed information. Solution: 1. Ensure that the Field Group for the post is set to 'Te same pola we wszystkich językach' (same fields across languages). You should use the WPML Editor as the default option for this setting. For more details, visit Using different fields across languages. 2. It is recommended not to set ACF Field Groups to Translatable. For further information, please check this note: The Advanced Custom Fields Field Group should be set as Not Translatable. 3. Update your WPML and the ACF add-on to the latest versions to ensure compatibility and functionality. You can update here: update here. After implementing these steps, make a change in the original post and verify if it appears correctly in the WPML editor.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket.
Problema: El cliente ha cambiado la URL de su sitio web de salubal.com a ingulados.com y necesita asegurarse de que WPML funcione correctamente tras este cambio. Solución: Si estás experimentando problemas después de cambiar la URL de tu sitio web, te recomendamos seguir estos pasos: 1. Completa el asistente de migración de WPML: Al entrar al panel de WordPress, WPML mostrará un aviso preguntando si el sitio se ha movido o copiado. Haz clic en Iniciar migración o la opción equivalente para indicar que el sitio se ha movido. Sigue los pasos del asistente hasta el final. 2. Vuelve a registrar el sitio con la nueva URL: Después de la migración, WPML te pedirá que registres el sitio de nuevo. Ve a Plugins → Añadir nuevo → Comercial y usa el enlace para obtener un nuevo código de registro desde tu cuenta de WPML. 3. Actualiza enlaces internos y referencias antiguas: Si notas que imágenes o enlaces siguen apuntando a la URL antigua, puedes corregirlo fácilmente: - Ve a WPML → Configuración. - Baja hasta Traducir objetivos de enlaces y haz clic en Escanear ahora y ajustar enlaces. Esto actualizará los enlaces internos automáticamente. Si después de seguir estos pasos continúas teniendo problemas, por favor sigue la guía en https://wpml.org/es/faq/how-to-remove-the-this-site-is-registered-on-wpml-org-as-a-development-site-notice/ y contacta con nosotros si necesitas más ayuda.
Es posible que esta solución sea irrelevante debido a que está desactualizada o no se aplica a tu caso. Te recomendamos abrir un nuevo ticket de soporte si es necesario y te sugerimos revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins.
Problem: The client is experiencing an issue where WPML, when activated, prevents further reservations for the same dates after a booking is made on their WooCommerce Booking platform. For instance, if one snowmobile is booked for specific dates, those dates become blocked for all other snowmobiles. This issue does not occur when WPML is deactivated. Solution: We recommended the client to ensure they have followed all the steps in our guide for translating bookable products with WooCommerce and WPML. You can find the guide here: Translating WooCommerce Bookings with WooCommerce Multilingual. Additionally, we asked the client to provide details about any recent changes made to the site before the issue was noticed and to share access credentials for further investigation, ensuring that a full site backup is available or alternatively, to set up a staging site using the WP Staging plugin.
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.
Problem: After updating WPML to the latest version, the client is unable to translate content and encounters a 500 error when attempting to use the string translation or open the WPML support tab. The issue began after URL slug manipulations were made, which might have caused disruptions in the translation engine. Solution: We recommend enabling the debug log to identify the specific cause of the 500 error. You can follow the instructions here: https://wpml.org/documentation/support/debugging-wpml/. After enabling the debug log, please share the log files with us for further analysis. If the problem persists, consider reverting to a previous stable version of WPML and its components, as this resolved the issue temporarily for the client.
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 continues, please open a new support ticket at WPML support forum for personalized assistance.
Problem: You are trying to translate your menu using WPML on a site with BuddyBoss, but the items from the BuddyBoss menu do not appear in the translation interface. Solution: 1. Ensure that you have installed the BP Classic plugin as it is necessary for translating BuddyBoss menus. You can find the documentation here: https://wpml.org/documentation/related-projects/buddypress-multilingual/#getting-started. 2. If the menu items still do not appear after installing the BP Classic plugin, we recommend adding custom links manually to the menu for the items related to BuddyBoss.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: El cliente está experimentando un error 500 de servidor debido a que el plugin WPML modifica el archivo htaccess, añadiendo el prefijo '/es' a las URLs, lo que provoca el error. Solution: 1. Para identificar la causa del problema, recomendamos seguir los pasos descritos en esta guía: https://wpml.org/es/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/ 2. Además, sugerimos actualizar los plugins de WPML desde Plugins -> Añadir nuevo -> Pestaña 'Comercial'.
Si esta solución no resuelve el problema o si parece no ser relevante debido a que está desactualizada o no se ajusta a tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: The client was experiencing an issue where the translation job was stuck 'In Progress' even after marking it as complete. The error log indicated that the uploaded xliff file was not properly formed, with missing or wrong data. Solution: We resolved the issue on our Advanced Translation Editor server side. We recommended the client to resend the page for translation. Additionally, we suggested clearing any server cache and resaving the translated page, as this seemed to fix the issue after translation, as demonstrated in a screen recording provided by our support team.
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 do not hesitate to open a new support ticket at our support forum.
