Problem: You are trying to set different permalink structures for posts in Dutch and English using WPML. Specifically, Dutch posts should use the permalink structure: /nieuwsitems/%postname%/, and English posts should use: /newsitems/%postname%/. Despite enabling 'Translate custom post and taxonomy base slugs' in WPML > Settings, setting the post type 'Posts' to Translatable - only show translated items, and configuring slug translations in WPML > String Translation, all posts, regardless of language, use /nieuwsitems/%postname%/ instead of the expected language-specific slugs.
Solution: We have found that WPML does not support translating custom permalink structures. It only supports translating custom slug translation when the custom type is registered. For more details, you can refer to our guide for developers here: Translating Slugs for Custom Post Type Archives.
As a workaround, consider using a Custom Post Type (CPT) instead of standard posts, as this allows for slug translation. Alternatively, you can create a category with the desired slug, assign it to all relevant posts, and update the permalink structure to include the category. This category slug can then be translated. For more guidance, check out these links:
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 you still need assistance, please open a new support ticket at WPML Support Forum.
Problem: After updating WPML to version 4.6.15 and then updating Elementor to 3.26, the client experienced issues where page translations worked, but the menu remained in the base language. The menu, created with PowerPack Elementor using the Advanced Menu widget, did not update to the selected language. Additionally, the language selector was redirecting to an Elementor library page instead of switching languages correctly. Solution: We suggested reverting to the initial versions of WPML and String Translation to see if the issue persists. We also recommended backing up the site and using the troubleshooting options available under WPML > Support > Troubleshooting. For detailed steps on how to perform these actions, you can refer to our documentation here: https://wpml.org/documentation/support/wpml-troubleshooting-options. Additionally, we advised checking under Appearance > Menus to ensure the menu is translated correctly in all languages and verifying that the Elementor header 'elementor-en-tete-183' is published in both languages.
If these steps do not resolve the issue, we recommend opening a new support ticket. It's also advisable to 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, please visit our support forum: https://wpml.org/forums/forum/french-support/.
Problème : Vous avez rencontré un problème où les blocs DIVI perdent les espaces et les bordures sur la version anglaise de votre page. Ce problème survient après avoir quitté le visual builder, bien que tout semble correct lors de son utilisation. Solution : Nous avons constaté que normalement, le CSS devrait se copier correctement lors de la traduction. Si vous rencontrez ce problème, il se pourrait qu'il s'agisse d'un problème temporaire, car nous avons déjà eu des cas similaires. Nous vous recommandons de vérifier que vous avez bien effectué toutes les mises à jour nécessaires et de vider tous les caches (cache normal, cache objet, cache navigateur, cache statique DIVI). Si le problème persiste, il est possible que la solution soit obsolète ou ne s'applique pas à votre cas. Nous vous conseillons de consulter les problèmes connus et de vérifier la version des corrections permanentes. Assurez-vous également que vous avez installé les dernières versions des thèmes et plugins.
Si aucune de ces solutions ne résout le problème, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum d'assistance.
