Problem: You are trying to display a data table on a translated page, but it is not visible due to the URL translation affecting content filtering. Solution: We recommend ensuring that your table setup adheres to WPML's guidelines for handling multilingual data. Please review our detailed documentation for developers, which can help you configure your data tables correctly:
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.
Problem: The client was unable to access the Translation Tools tab in the WPML plugin to retrieve the migration code for a staging site. This issue was compounded by a connection error message advising to check the internet connection.
Solution: 1. Ensure that the WPML plugin is properly registered: - Visit https://wpml.org/account/websites/ - Delete the existing site URL if already registered and re-enter it to generate a new site key. - Copy the new key and enter it under Plugins > Install > Commercial to re-register WPML.
2. Enable the Advanced Translation Editor: - Go to WPML > Settings and select "Advanced Translation Editor". - Fill out the necessary settings in WPML > Settings > AI Translation, including context, target audience, and post-translation actions. - Complete the Setup Wizard in WooCommerce > WPML Multilingual & Multicurrency for WooCommerce.
3. If issues persist, particularly with accessing the Translation Tools tab, check for conflicts with other plugins or themes, particularly those that might affect JavaScript operations or the WP REST API. Disabling conflicting plugins or switching to a parent theme may resolve the issue.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to translate multiple shortcodes containing ids to another string for the translated version on your site. You have added them to the custom XML config, but the Advanced Translation Editor (ATE) only picks up the changed strings, not the shortcode id. The specific shortcodes involved are for ws_form and mwai_chatbot. Solution: We have reviewed your issue and found that the values for these shortcodes only appear when being directly searched for within ATE. By searching for them in ATE, you can manually add the value and thus translate it.
Please note that this solution might be 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 issue persists, please open a new support ticket.
Problem: The client wants WPML to automatically scan internal links from default/custom Gutenberg blocks and ACF Link fields to ensure that users are directed to the correct language version of a page. They encountered issues where changes on the source page were not applied to the translated page. Solution: For ACF Link fields, the translation preference should be set to 'Translate' to allow for automatic scanning of links. For custom Gutenberg blocks, if they are rendered via React using a JSON data prop, the internal links might not automatically update to point to translated pages. In such cases, disabling WPML Translation for the specific page and translating it manually with the default WordPress editor is recommended as a workaround. More details can be found here: Using different translation editors for different pages. Additionally, a separate ticket was created to address the issue of changes not being applied to the translated page, which can be followed here: WPML support forum topic.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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.
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: The client is using WPML's automatic translation feature for their website, where new content created in Dutch (default language) is automatically translated into German, English, and French. However, when requests are submitted in a language other than Dutch, they are not automatically translated into the other active languages. Solution: Currently, WPML does not support automatic translation from non-default languages. The client can manually send these posts for translation via the WPML > Translation Dashboard by filtering the posts and selecting them for translation. For a more automated approach, it might be possible to develop a custom script that programmatically sends posts to the WPML Translation Queue. This would involve using the
wpml_after_save_post
action, which is triggered by the
sendToTranslation
function in WPML. However, this function is restricted to operate only when saving posts in the default language, and modifying this behavior would require changes to the plugin's internal code.
If this solution does not fully address your needs or seems outdated, we recommend opening 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, please visit our support forum at WPML Support Forum.
Problem: The client was unable to translate text fields from a 'Newsletter Popup' created with Elementor in the Wolmart theme, despite following documentation and enabling translation for 'Wolmart Templates' in WPML settings. The XML configuration provided resolved translation issues for 'banner' elements but caused issues with buttons and text fields on those banners.
Solution: We first confirmed the XML configuration was correctly registering fields. We then checked WPML settings and found 'Wolmart Templates' was set to 'Not Translatable'. After making it translatable, the translation issues were resolved, but the client faced RTL support issues with buttons. We suggested that the client might need to contact their theme's support for CSS adjustments related to RTL display.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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. 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.
