Problem: The client was unable to edit translations because they were redirected to the page direction instead of the strings of translations. Solution: We checked the page and found that it was using the WordPress editor. We switched it to the WPML editor for the client. We recommend checking if the page now works correctly by attempting to edit the translation again. If you're experiencing a similar issue, we suggest switching to the WPML editor from the WordPress editor when trying to edit translations. If the solution provided here is not relevant to your case, because it might be outdated or not applicable, we encourage you to open a new support ticket. We also highly recommend checking related 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 contact us in the WPML support forum.
Problème :
Le client a rencontré un problème avec les couleurs du menu qui ne s'affichent pas correctement sur son site.
Solution :
Nous avons fourni des conseils pour ajuster les couleurs et la transparence du menu à l'aide de CSS personnalisé. Voici les étapes recommandées :
1. Pour définir un fond blanc pour le sous-menu :
.wpml-ls-slot-2.wpml-ls-current-language .wpml-ls-slot-2:hover, .wpml-ls-slot-2.wpml-ls-current-language .wpml-ls-slot-2:hover a {
background-color: #fff !important;
}
2. Pour ajouter un effet de transparence au lien lors du survol :
.et_pb_menu_0_tb_header.et_pb_menu .nav li ul.sub-menu li.wpml-ls-slot-2 a:hover {
opacity: .7;
}
Nous avons également suggéré de choisir une couleur spécifique plutôt qu'une opacité pour le survol des liens, car la transparence appliquée sur des fonds de couleurs différentes ne donnera pas le même résultat :
Il est important de noter que cette solution pourrait ne pas être pertinente si elle est obsolète ou ne correspond pas à votre cas. Nous vous recommandons de vérifier les problèmes connus, de vérifier la version de la correction permanente et de vous assurer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum d'assistance.
Problem: The client needed to display a different ClickUp form on the French version of an 'Information request' page, but changing the code on the French page also changed it on the English one.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, we encourage you to open a new support ticket. We also 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 you need further assistance, please contact us in the WPML support forum.
Problem: The client was experiencing an issue with their website not displaying normal French characters, but instead showing HTML strings. Solution: We recommended the client to first create a full backup of their website. Then, we advised them to follow the workaround provided on our errata page for issues related to the Divi theme where apostrophes display as HTML entities. You can find the workaround here: https://wpml.org/errata/divi-button-apostrophes-display-as-html-entities/.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If after checking the related known issues at https://wpml.org/known-issues/ and confirming that you have the latest versions of themes and plugins installed, the problem persists, we highly recommend you to open a new support ticket. For further assistance, please visit our support forum: https://wpml.org/forums/forum/english-support/.
Problem: The client was experiencing issues with CSS not being the same across different language versions of their website using the Divi theme. They noticed that custom fields were set to not translate and were unsure what this meant for their site.
Solution: We advised the client that the issue might stem from how the page builder or theme stores the styling information. We recommended setting the relevant custom field that contains styling information (usually containing words like "style", "css", "layout", or "styling") to "copy". This would allow the styling to be carried over to the translated page. The client should then: 1. Make a small change in the default language page. 2. Save the page. 3. Go to the translated page and save it again to ensure the CSS is copied over. For more detailed instructions, we provided a link to our documentation on translating custom fields: https://wpml.org/documentation/getting-started-guide/translating-custom-fields/
If the solution provided here is not relevant due to being outdated or not applicable to your case, we encourage you to open a new support ticket. We also 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 contact us in the WPML support forum.
