Problem: The client reported that their homepage only displayed in English despite having translated the site into four languages using WPML. Additionally, they encountered an issue where the logo disappeared when navigating to a translated page. Solution: 1. We identified that redirections were causing the German and Portuguese versions of the homepage not to display. We recommended checking and adjusting these redirections and ensuring that all translations are published. 2. To address the site's performance and possibly related issues, we advised increasing the WordPress memory limit. This can be done by adding the following line to the wp-config.php file:
This line should be placed above the 'That's all, stop editing! Happy blogging.' line. Further verification of the WordPress memory limit can be done through WPML -> Support. 3. Regarding the disappearing logo on translated pages, we needed further investigation into the site's configuration. We requested access credentials to examine the settings more closely and asked the client to describe how they edit the logo.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing a 301 error (Too many redirects) when trying to view all translated products on their website. They are unsure if recent plugin updates could have caused this issue. Solution: We identified that the issue was related to the handling of taxonomy slugs for product categories. We recommended modifying the code to ensure that the slug for each product category is correctly decoded. Here is the code we suggested adding to the site's functions:
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client has translated an article into French using WPML, but the paragraphs from the original text are missing in the translation, resulting in the text appearing as one big block without any line-breaks. Solution: If you're experiencing similar issues with paragraph formatting in your translations, we recommend the following steps: 1. Open a translation job using our Advanced Translation Editor. 2. Go to the top right corner of the translation editor. 3. Click the gear icon. 4. Disable the option 'I prefer bigger segments'. 5. Close the editor and resend the form to translate again via WPML > Translation Management.
Please note that this solution might be irrelevant if it's 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 at WPML support forum.
Problem: You are trying to update to the latest version of WPML and encountering issues due to an Elementor bug. Despite rolling back Elementor and Elementor Pro to version 3.25.5, WPML fails to update, and the String Translation plugin is stuck in a loading loop. Solution: We recommend checking the specific errata related to the Dokan Pro and WPML update issue, which might be causing the update failure and the loading loop in the String Translation plugin. You can find more detailed information and potential fixes here: https://wpml.org/errata/dokan-pro-wpml-update-fails-when-is-active/.
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 with us for further assistance.
Problem: You are experiencing an issue where navigating the Careers section in a non-English language redirects to the English job description page instead of the translated version. Solution: We recommend checking and updating the page and its translations in your WPML settings. For example, you can go to the specific job description page in the WPML's Translation Editor and ensure all translations are correctly linked and updated. This approach resolved the issue for the German language version of the site.
If this solution does not apply to your case, or if it seems outdated, please visit our known issues page to check for related problems and their solutions. Ensure you have the latest versions of themes and plugins installed. If the issue persists, we highly recommend opening a new support ticket with us for further assistance. You can do so at our support forum.
Problem: You are trying to translate the Doca listing on your main English website, but it is not translating and instead shows a 'page not found' error. The translated pages for Spanish and Portuguese are resulting in 404 errors and the content remains in English instead of being translated. Solution: The translated listings of the Doca listing have been drafted but not published. We recommend you to publish these drafts. You can do this by accessing the following links:
After publishing, please check if the issue persists.
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 the problem continues, please open a new support ticket.
Problem: If you're trying to manually upgrade the Multilingual CMS in your development environment and facing issues due to a weak local connection that causes the upgrade process to hang and fail, setting your site in maintenance mode. Solution: We recommend downloading the latest version of the plugin from the Downloads section of your WPML.org account. After downloading, manually install the ZIP file on your site. For detailed instructions on how to manually update the plugin, please visit this guide.
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 further assistance is needed, please feel free to open a new support ticket at WPML support forum.
Problem: You are trying to translate the footer of your website using WPML, but despite following the string translation documentation, the footer translation stopped working and appears untranslated in Spanish. Solution: Here's what we recommend you try: 1. Go to Appearance -> Widgets and resave the Footer 2 widget. 2. After resaving, the text of this widget should appear in WPML -> Strings Translation. You can then proceed to translate it. 3. Once translated, the changes should reflect on the front end in Spanish.
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 the problem persists, please open a new support ticket at our support forum for further assistance.
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: The client was experiencing a 404 error when trying to view content translated into English. The expected behavior was to see the same content as in the Portuguese (PT) version, but translated into English. Solution: We reviewed the client's setup and identified that the issue was related to the incorrect translation of the URL slug which included the language code (/en). To resolve this, we removed the language code from the slug translation, ensuring that only the slug part needed translation without including the language code. This adjustment corrected the URL structure and resolved the 404 error.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise checking the related known issues and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: The client reported issues with long delays when saving translations on a page, and the footer not translating correctly despite following provided instructions. Solution: 1. For the issue of delays when saving translations, we recommended refreshing the page as demonstrated in the screen recording: https://go.screenpal.com/watch/cZlwDAneqqk. 2. Regarding the footer not translating, we corrected the string translation to point to the correct language Footer template ID via the WPML String Translation interface.
If this solution does not resolve your issues 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
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: If you're experiencing issues where changing a product's status to 'draft' in the default language (Italian) does not automatically sync the status to additional languages (English/Chinese) on your multilingual site, we have a solution for you. Solution: We recommend adding a custom code snippet to your theme's functions.php file to synchronize the publish status across all languages. Here's how you can do it:
function sync_publish_status_across_languages($post_id) {
// Check if this is a valid post type (product) and that the post is not being autosaved
if (defined('DOING_AUTOSAVE') && DOING_AUTOSAVE) return;
if ('product' != get_post_type($post_id)) return; // Check for WooCommerce product post type
// Get the current post status
$post_status = get_post_status($post_id);
// Get the default language
$default_language = apply_filters('wpml_default_language', null);
// Get all translations of the post in different languages
$translations = apply_filters('wpml_get_element_translations', null, $post_id, 'product'); // Updated for products
foreach ($translations as $lang => $translation) {
// Skip the default language post (we don't want to update it)
if ($lang === $default_language) continue;
// Get the translation post ID
$translation_post_id = $translation->element_id;
// Update the publish status of the translated post
wp_update_post(array(
'ID' => $translation_post_id,
'post_status' => $post_status
));
}
}
add_action('save_post', 'sync_publish_status_across_languages');
Please note that this solution might be outdated or not applicable to your specific case. If this does not resolve your issue, 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: You are experiencing high server response times due to repetitive WPML-related database queries, as indicated by Query Monitor. Despite using Object Cache Pro, these queries remain inefficient and affect page load performance. Solution: We have reviewed your concern and found that a load time impact of 0.5-1.0 seconds is typical with WPML. The duplicated queries you mentioned contribute only 0.0010 seconds to the load time. Additionally, the website's frontend and backend loaded in less than 1 second, and the PageSpeedInsights score was 96, which is very good. Given these observations, the performance impact of WPML queries is within an acceptable range, and significant optimization may not be necessary at this time.
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 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: You are experiencing an issue where some elements overlap the header on your pages after updating WPML. Solution: We recommend adding the following CSS to the custom CSS section of your theme to resolve the overlapping elements issue:
This adjustment should prevent the elements from overlapping the header. If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues 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. You can do so at WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
