Problème : Vous essayez de traduire vos pages créées avec Elementor sur votre site, mais la fonction de traduction automatique ne fonctionne pas. Le plugin duplique tout le contenu en français sans le traduire et le tableau de bord de traduction affiche continuellement le message 'Chargement des éléments...'. Solution : Nous avons identifié que le thème Amanus que vous utilisez n'est pas officiellement pris en charge par WPML, ce qui peut causer des problèmes avec les widgets personnalisés d'Elementor. Pour résoudre ce problème, nous vous recommandons d'enregistrer ces widgets via XML pour permettre à WPML de les reconnaître et de les traduire correctement. Vous pouvez trouver les instructions détaillées ici : https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/ Si cette solution ne fonctionne pas, envisagez de contacter les auteurs du thème ou de passer à un thème compatible avec WPML.
Il est possible que cette solution ne soit plus pertinente, soit parce qu'elle est obsolète, soit parce qu'elle ne correspond pas à votre cas. Nous vous recommandons vivement de consulter les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version de la correction permanente et de confirmer 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 de support.
Problem: The client reported that a page translated into Japanese using WPML does not display when switching to the Japanese language, although translations into French and Spanish work correctly.
Solution: We identified that the issue was related to the translation of Advanced Custom Fields (ACF) field groups. To resolve this, we: 1. Accessed ACF > Custom Fields Group and selected the translations languages (fr, es, ja). 2. Ensured no field groups were listed there by deleting any translations made. 3. Went to WPML > Settings > Post type translation and set "Field Groups (acf-field-group)" to "not translatable". 4. Advised the client to resave the translation, which immediately fixed the issue.
Additionally, for the site key issue, we recommended: - Visiting the account page (https://wpml.org/account/sites/) - Deleting the old site key and unregistering WPML from the site. - Registering WPML again and entering a new site key.
This should restore the translation functionality. For the prepaid credits, they will automatically be used at the end of the payment cycle.
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.
Problem: The client is using the 'Content Control' plugin by 'Code Atlantic' for WordPress, which allows setting a 'Custom Redirect URL' under 'Protection' in the 'Restriction' settings. However, the plugin does not support language-specific options for the 'Custom Redirect URL'. Solution: We recommend creating separate restrictions for each language. For instance, set up one restriction with a custom redirect URL for English pages and another for German pages. This approach allows the 'Custom Redirect URL' to adapt based on the current WPML language.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
