Problème : Vous avez lancé WPML pour la traduction de votre site web, mais vous rencontrez un problème où les champs des images dans vos CPT sont vides. Solution : Le contenu est bien présent sur la page, mais il est masqué par un JavaScript personnalisé. Ce script ajoute une règle
display: none !important;
qui surcharge les autres styles et masque l’élément sous certaines conditions. Ce JavaScript est inclus dans le template d’en-tête. Voici les étapes que nous avons suivies pour résoudre ce problème : 1. Nous avons modifié le template d’en-tête pour supprimer le JavaScript personnalisé. 2. Le template a été enregistré et le contenu a été renvoyé en traduction. 3. Les templates traduits ont été mis à jour. Malgré ces modifications, la condition continue de se déclencher et les éléments restent masqués. Le contenu est toujours présent dans le HTML et peut être visible via l’inspection du code.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de confirmer que vous avez installé les dernières versions de vos thèmes et plugins, et de vérifier la version du correctif permanent. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: The client is developing a site using WPML to add Arabic as a secondary language and has translated everything. However, they are facing an issue where the WooCommerce 'shop' page appears differently between the French and Arabic versions, and they are unable to standardize them. Solution: We recommended enabling WPML's debugging features to identify any potential errors that might be causing the display issues. Here are the steps we suggested: 1. Edit the
wp-config.php
file and change the line
define('WP_DEBUG', false);
to
define('WP_DEBUG', true);
2. Add the following lines to the
wp-config.php
file, just before the 'stop editing here' comment:
file in the site's root directory, which should be checked for any errors. Additionally, we requested temporary access to the client's site to further investigate the issue, emphasizing the importance of taking a full backup before providing access. We often recommend using the Duplicator plugin for this purpose, available at http://wordpress.org/plugins/duplicator/.
If this solution does not resolve the 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 the problem persists, please open a new support ticket.
Problem: The client needs to ensure that image meta fields are automatically translated in such a way that the image remains the same across all languages, both when using automatic translation and when manually translating posts or taxonomies. Solution: 1. To ensure images are available in all languages when using automatic translation, navigate to WPML > Settings > Media translation. Verify that the images exist in all languages by checking in Media > All and switching between languages. This setting uses the same file but ensures the image exists in the database for all languages. 2. For manual translations where you want the image to be set automatically, go to WPML > Settings > Custom fields, find your custom field, and set it to COPY. This will copy the same image IDs to your translated posts.
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 at WPML support forum.
