The client was experiencing an issue where the accordion widget displayed incorrect characters on the translated page on their website. Initially, the problem was resolved in two languages after updating the translation, but it persisted in the Catalan language.
Solution:
We recommended the following steps to address the issue: 1) Navigate to WPML>>Settings>>Custom Fields Translation. 2) Click on the Show systems fields link. 3) Search for the
1
*_eael_widget_elements*
field. 4) Set it as Copy and save the changes. 5) Open the page for editing in the original language and make a minor change to refresh the translation settings and update it. 6) Update the translation.
Additionally, to address the issue with the Catalan translation specifically: 1) Visit Essentials Addons>>Tools and click on the Regenerate Assets button. 2) Update the page and then update the translation.
If these steps do not resolve your issue, or if the solution 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: The client is experiencing two main issues with a translated contact form. First, the dropdown options in the form are not fully displayed in the translated version. Second, the link to the privacy policy page is not correctly pointing to the translated version of the page. Solution: 1. For the dropdown options not displaying correctly, ensure that the options are correctly added and formatted in both the default and translated forms. You might need to update the default form to match the format shown in this demo, and then resend the form for translation. 2. For the incorrect privacy policy link, the link should be translated through the Translation Editor. In the Translation Editor, find the paragraph where the link is added, unlock the field with the lock icon, update it with the translated page link, and save the translation. If these steps do not resolve the issues or if the solution seems 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 the problem persists, please open a new support ticket.
Problem: The client's website is set up in multiple languages, and they are using the Events Calendar with WPML for translations. The main issues were that events were only showing in the Spanish version and not in other languages like Catalan, and some strings from the Events Calendar were not appearing translated on the event pages despite being translated in WPML.
Solution: 1. To ensure events appear in all languages, we advised setting the translation preference for the 'tribe_events' post type to 'Translatable - use translation if available or fallback to default language' in WPML > Settings > Post Type Translation. 2. For the untranslated strings, we recommended rescanning the Events Calendar plugin for strings via WPML > Theme and Plugins Localization, then translating them in WPML > String Translation. If strings still did not appear translated, generating MO files through WPML > Support > Troubleshooting was suggested. 3. We also addressed a specific issue with the string 'Calendar' appearing twice by removing the duplicate translation in WPML > String Translation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Additionally, please check 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. For further assistance, visit our support forum at https://wpml.org/forums/forum/english-support/.
Problema:
El cliente tiene preguntas sobre la redirección automática de usuarios a la versión del sitio web en su idioma, basándose en su ubicación geográfica, y cómo afecta esto a usuarios de diferentes regiones que hablan el mismo idioma.
Solución:
Si estás experimentando dudas sobre la redirección automática basada en la ubicación geográfica de tus usuarios, te recomendamos no utilizar este enfoque. Nuestra funcionalidad de redirección se basa en el idioma del navegador del usuario, no en su país de origen. Por ejemplo, si un usuario en Italia tiene su navegador en inglés, será redirigido a la versión en inglés del sitio, no a una posible versión italiana. Lo mismo ocurre con los usuarios de Portugal que, si tienen su navegador en portugués, serán redirigidos a la versión en portugués del sitio, independientemente de la variante regional del idioma.
Es posible que esta solución no sea relevante para tu caso, ya sea porque la información está desactualizada o simplemente no se aplica a tu situación. Si es así, te sugerimos abrir un nuevo ticket de soporte. También te recomendamos encarecidamente revisar los problemas conocidos relacionados, verificar la versión de la solución permanente y confirmar que has instalado las últimas versiones de temas y plugins.
