Problema: El cliente no puede actualizar las traducciones con el ATE porque se pierden las traducciones hechas y el diseño de la página no se sincroniza. Además, tiene problemas con el estilo de los botones de cierre y los listados en diferentes idiomas. Solución: 1. Para el problema del estilo del botón de cierre, recomendamos agregar el siguiente código CSS en Apariencia -> Personalizar -> Sección 'CSS Adicional':
2. Para el problema de los listados con puntos en español y rayas en las traducciones, es importante verificar cómo se creó el contenido original y cómo se tradujo. Si los puntos se añadieron manualmente y no como un listado HTML, recomendamos usar listados HTML para asegurar la consistencia en todos los idiomas. Puede encontrar más información sobre cómo crear listados HTML en https://www.w3schools.com/html/html_lists.asp. 3. Si los elementos o shortcodes no están registrados correctamente en WPML, puede perderse información en las traducciones. En este caso, recomendamos registrar el elemento siguiendo los pasos en nuestra guía: https://wpml.org/documentation/plugins-compatibility/elementor/how-to-add-wpml-support-to-custom-elementor-widgets/.
Si esta solución no resuelve su problema o si encuentra que la información está desactualizada, le recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tiene instaladas las últimas versiones de los temas y plugins.
Problem: The client reported that the navigation and footer disappear when selecting the German version of their site. Solution: For the navigation logo issue, we recommended creating a new HTML widget under WP > Appearance > Widgets > Logo and pasting the same HTML there, but selecting the German language for the "Display on Language" option. Here is the HTML code used:
Regarding the missing footer, we requested more information on how the client created the footers for the Danish and English versions, which were accessed through WP > Yootheme > Widgets > Bottom.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues where the Theme Settings display data for all languages on the same page instead of just the current language after updating WPML plugins. Additionally, there is an error in ACF PRO: Uncaught TypeError: Illegal offset type in isset or empty. Solution: We recommend deleting all field groups from the German and Italian versions completely, including removing them from the trash. Then, access your settings page and set the following options to "Not translatable": - Options Pages (acf-ui-options-page) - Field Groups (acf-field-group) This ensures that only one version of each field group exists. If the fields are still missing, you may need to manually recreate and translate them, or consider restoring the website to a previous state before these changes were made for further review.
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 problems persist, please open a new support ticket.
Problème: Les filtres sur les pages d'archives de produits disparaissent ou ne fonctionnent pas correctement lorsque la page est affichée en anglais. Les filtres affectés incluent la fourchette de prix, la sélection dropdown, les couleurs et les checkbox. Solution: Nous vous recommandons de suivre les guides de configuration pour assurer la compatibilité entre Jetsmartfilters et WPML. Voici les liens vers les documentations pertinentes:
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous invitons à ouvrir un nouveau ticket de support. Nous vous recommandons également de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version du correctif permanent, et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Pour toute assistance supplémentaire, veuillez contacter notre forum de support en suivant ce lien : https://wpml.org/fr/forums/forum/assistance-en-francais/.
Problem: You are developing a site and need help translating text and slugs for Custom Post Types created with ACF using WPML. You cannot find where to translate some text and slugs for Custom Post Types. Solution: First, ensure that the archive page is functioning correctly without a custom slug. If you're using a custom archive slug, it's not translatable by default. We recommend deleting the custom slug to see if the default archive slug works correctly. For further guidance, check this documentation.
Regarding the archive slugs, there are two types: 1)
'has_archive' => true
: This setting uses the default slug as an archive slug, which can be translated using WPML. 2)
'has_archive' => 'custom_slug'
: This setting uses a custom slug for the archive page. By defining a specific string as a value, you set the same slug for both the default and secondary languages.
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 at WPML support forum.
