Problem: The client was unable to translate the header button text and footer text on their website using WPML due to the Aoriv theme not being officially compatible with WPML. Solution: We provided a CSS workaround to address the translation issue. The client should insert the following CSS in Appearance -> Customize -> Additional CSS:
This solution might be irrelevant due to updates or different circumstances. If this does not resolve your issue, please check related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists. For further assistance, please visit our support forum.
Problem: You are working on a site under development and facing issues with displaying variations and menus in Arabic. The variations and menus are not displaying correctly in Arabic. Solution: We have identified that the Max Mega Menu plugin used on your site is not fully compatible with WPML. To address this, you can follow the workaround provided in the Max Mega Menu documentation to make the menu translatable. Here is the guide: https://www.megamenu.com/documentation/wpml-setup/ If you encounter any issues during this process, we recommend contacting the plugin author and informing them of the compatibility issues. We are also willing to collaborate with them to enhance WPML compatibility.
Please note that this solution might be outdated or not applicable to your specific 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.
Problème : Vous travaillez sur un site avec traduction automatique à 100% et vous avez plusieurs Custom Post Types (CPT) dont vous voulez que tous les champs soient traduits sauf le titre du post. Vous ne savez pas comment interdire la traduction du titre d'un post tout en traduisant les autres champs. Solution : Pour ne pas traduire le titre d'un post tout en traduisant les autres champs, vous devez utiliser un code personnalisé. Appliquez le code suivant à chaque type de publication personnalisé en l'ajustant selon vos besoins :
$value ) {
if ( isset( $value->field_type ) && 'title' === $value->field_type ) {
// Ne pas traduire le titre + copier la valeur originale.
$value->field_translate = 0;
$value->field_data_translated = $value->field_data;
}
}
return $fields;
}
Pour les autres champs, conservez simplement leur configuration actuelle (comme traduisibles). Si cette solution ne s'applique pas à votre cas ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent 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 d'assistance.
Problem: You are trying to translate the slug for a custom post type (CPT) called 'book'. The slug should be 'book' for the single template and 'books' for the archive template. You have followed the instructions from the WPML documentation but cannot find the option in WPML settings to translate the archive slug, as the settings only provide a field for the singular slug. Solution: We currently do not support the direct translation of archive slugs for custom post types due to technical limitations. However, we recommend a workaround which you can find detailed in our forum: https://wpml.org/forums/topic/custom-post-type-via-acf-archive-translation/#post-16830228.
If this solution does not apply to your case, or if it seems outdated, please 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. For further assistance, you can contact us directly through our support forum.
Problem: If you're experiencing issues with WPML where translations of posts or products are incorrectly opening in the WordPress editor instead of the WPML Translation Editor, and you receive warnings about potential data loss, we have identified a solution. Solution: First, ensure you create a full backup of your database. Then, perform the following SQL queries via phpMyAdmin:
DELETE pm FROM wp_postmeta pm JOIN wp_posts p ON pm.post_id = p.ID WHERE p.post_type = 'product' AND pm.meta_key = '_wpml_post_translation_editor_native' AND pm.meta_value = 'yes'
DELETE pm FROM wp_postmeta pm JOIN wp_posts p ON pm.post_id = p.ID WHERE p.post_type = 'product' AND pm.meta_key = '_last_translation_edit_mode' AND pm.meta_value = 'native-editor'
UPDATE wp_icl_translate_job JOIN wp_posts ON wp_icl_translate_job.title = wp_posts.post_title SET wp_icl_translate_job.editor = 'wpml' WHERE wp_posts.post_type = 'product' AND wp_icl_translate_job.editor = 'wp'
After running these queries, verify by opening a few product translations at random to confirm that they now load in the WPML Translation Editor.
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 further assistance is needed, please open a new support ticket at WPML support forum.
