Problem: You are trying to translate text from Gravity Forms, but it is still showing in the original language. The translated text is not displayed; instead, the original text appears. Solution: We recommend checking the workaround provided on the WPML errata page for issues related to Gravity Forms not translating correctly. You can find the specific workaround here: Gravity Forms Image Choice Field is not translated.
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 you still encounter problems, please open a new support ticket at WPML support forum for further assistance.
If you're experiencing issues editing investment pages on your site using WPML, and encountering an error due to a compatibility conflict with JetEngine when manually translating the Post Type.
Solution:
We recommend trying the following steps as a temporary workaround after ensuring you have a full site backup:
1) Navigate to WPML>>Settings. 2) Scroll down to the Slug translations section. 3) Uncheck the Translate custom post and taxonomy base slugs (via WPML String Translation) option. 4) Save the changes.
Alternatively, you can: - Go to JetEngine>>Post Types. - Edit your Custom Post Type (Investments). - Go to Advanced Settings. - Disable the "Show in Rest API" option. - Save the changes.
If this solution does not resolve your issue or seems irrelevant due to being 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 needed, please open a new support ticket at WPML support forum.
Problem: The client is implementing a resume count limit on a multilingual site using WPML. The limit works in the default language but fails in the second language, showing the 'Add Resume' button even when the limit is reached. Solution: We recommend taking a backup of your site and testing the following code to ensure the resume count limit works across all languages:
function resume_manager_count_user_resumes( $user_id = 0 ) {
global $wpdb;
if ( ! $user_id ) {
$user_id = get_current_user_id();
}
// Check if WPML is active
if ( defined( 'ICL_LANGUAGE_CODE' ) ) {
// Get the default language code
$default_language = apply_filters( 'wpml_default_language', null );
// Query to count resumes across all languages (including translations)
return $wpdb->get_var( $wpdb->prepare( "
SELECT COUNT(DISTINCT p.ID)
FROM {$wpdb->posts} p
LEFT JOIN {$wpdb->prefix}icl_translations t ON p.ID = t.element_id
WHERE p.post_author = %d
AND p.post_type = 'resume'
AND p.post_status IN ( 'publish', 'pending', 'expired', 'hidden' )
AND ( t.language_code = %s OR t.source_language_code IS NULL )
", $user_id, $default_language ) );
}
// Default query if WPML is not active (only counts resumes in the default language)
return $wpdb->get_var( $wpdb->prepare( "
SELECT COUNT(ID)
FROM {$wpdb->posts}
WHERE post_author = %d
AND post_type = 'resume'
AND post_status IN ( 'publish', 'pending', 'expired', 'hidden' );
", $user_id ) );
}
// Check if the resume limit is reached and remove the "Add Resume" button
function resume_manager_add_resume_button( $user_id = 0 ) {
$limit = 5; // Set the resume limit (this could be dynamic or configurable)
$resume_count = resume_manager_count_user_resumes( $user_id );
if ( $resume_count >= $limit ) {
// Add custom code to hide or disable the "Add Resume" button
echo '<style>#add_resume_button { display: none; }</style>';
}
}
If this solution does not resolve the issue, we can provide a WPML test site to further investigate and solve the problem.
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 issue persists, please open a new support ticket at WPML support forum.
Problem: You are trying to translate the 'lang' attribute of the VikRentCar shortcode ([vikrentcar view="vikrentcar" lang="en-US"]) using WPML, but the translation does not reflect on the page. The issue arises because the 'lang' attribute is stored in a custom database table and is not dynamically updated during the localization process. Solution: To resolve this, you need to make the value stored in the custom database tables translatable with WPML. You can follow the guide on making strings translatable in WPML here: String Package Translation. Until this configuration is set, you will need to manually translate the page containing the VikRentCar shortcode using the WordPress editor instead of the Advanced Translation Editor. Additionally, since the VikRentCar plugin is not listed in WPML’s compatibility directory, it is recommended to contact the VikRentCar development team for further support and encourage them to join WPML's Go Global program for better compatibility.
If this solution does not apply to your case, or if it seems outdated, please 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. If further assistance is needed, we highly recommend opening a new support ticket at WPML support forum.
Problem: You are experiencing an issue where internal links are not being auto-translated when using the ACF Link field inside Flexible content. For example, the link remato.com/pricing does not change to remato.com/et/hinnakiri. Solution: We are aware of this issue and it should be addressed in the upcoming release of ACF Multilingual. We recommend installing the beta version of the plugin to see if it resolves the problem. You can check the changelog here.
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 at WPML support forum.
Problem: You are experiencing instability with the Yoast Redirects feature when the WPML SEO plugin is active. Errors occur when saving new redirects, and the domain of the Redirect To URL is missing when both plugins are active. Solution: We recommend disabling the WordPress guess redirects to resolve this issue. You can do this by adding the following code to your
After adding the code, go to Settings -> Permalinks in your WordPress dashboard and update the permalinks. This should help stabilize the Yoast Redirects feature.
If this solution does not resolve your issue or seems irrelevant due to being 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 problems persist, please open a new support ticket.
Problem: The client is experiencing an issue where adding a variable product to the cart results in infinite loading. This problem only occurs when the WPML Multilingual CMS plugin is enabled. Solution: We recommend isolating the issue by simplifying the site environment. Here are the steps we suggest: 1. Switch to a default WordPress theme, such as TwentyTwenty-Four, to check if the issue persists. 2. If the problem still occurs, deactivate all plugins except for WPML and its add-ons, and WooCommerce, without any extensions. Test again. 3. If the issue resolves, reactivate the other plugins one by one to identify which one causes the conflict. *** Important! Please make a full site backup (files and DB) before you proceed with these steps*** *** If your site is live, you might want to try these procedures in a staging environment or a snapshot of your site on your local server or another server. *** The client reported deactivating the Query Monitor plugin solved the problem.
If this solution does not apply because it might be outdated or not relevant 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 at WPML support forum.
Problem: The client reported that WPML overwrites Gravity Form in the latest versions of Gravity Forms Multilingual, despite a previous workaround. They requested a new solution for this recurring issue. Solution: We revisited the previous workaround and found it still applicable. Here are the steps to implement the solution: 1. Open the file at /gravityforms-multilingual/inc/gravity-forms-multilingual.class.php. 2. On line 685, replace:
$snh = new GFML_String_Name_Helper();
with:
$snh = new GFML_String_Name_Helper();
// WPML workaround for compsupp-7768
$check = new \WPML\Utils\DebugBackTrace();
if ($check->is_class_function_in_call_stack('GFFormDisplay', 'process_form')) {
return $form;
}
3. Repeat the same replacement on line 822.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Please 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, visit our support forum at https://wpml.org/forums/.
Problème: Le client ne parvient pas à traduire certains termes ('commande', 'date', 'livraison gratuite') dans les e-mails multilingues malgré l'activation de la localisation des plugins et la recherche dans la traduction des chaînes. Le problème persiste dans toutes les langues (EN, DE, IT, ES). Solution: Nous avons suggéré au client de vérifier si une autre instance de la chaîne existe sous un domaine différent en activant l'option 'Look for strings while pages are rendered' dans WPML > String translation, puis de visiter la page concernée. Plus d'informations sur ce problème sont disponibles ici : https://wpml.org/faq/why-arent-my-translated-strings-showing-up-on-the-front-end-of-my-site/ Nous avons également identifié un problème potentiel de compatibilité avec le shortcode [yaymail_order_date] qui ne traduit pas les dates selon la langue de l'interface. Nous avons recommandé de reproduire le problème dans un environnement sandbox pour isoler le problème de configuration spécifique du site du client. Instructions pour reproduire le problème et partager avec le support WPML sont disponibles ici : https://wpml.org/faq/how-to-reproduce-issues-and-share-them-with-wpml-support/ Si cette solution ne s'applique pas ou semble obsolète, nous vous recommandons vivement de vérifier les problèmes connus ici : https://wpml.org/known-issues/, 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.