Problem: The site is using the Header Footer Code Manager to load a snippet with a noindex tag into the head of the source code for specific pages. They are trying to ensure that the translated pages on your site have the same noindex tag as the original pages. The noindex tag is present in the original page's code, but it is missing in the translated versions. Solution: To include the noindex tag in the translated pages using WPML, you need to modify the code in the header-footer-code-manager plugin. Follow these steps: 1. Open the
file. 2. Locate line 550. 3. Open the .../wp-content/plugins/header-footer-code-manager/99robots-header-footer-code-manager.php file
Look for line 550
Replace:
case 's_pages':
$is_not_empty_s_pages = self::hfcm_not_empty( $scriptdata, 's_pages' );
if ( $is_not_empty_s_pages ) {
// Gets the page ID of the blog page
$blog_page = get_option( 'page_for_posts' );
// Checks if the blog page is present in the array of selected pages
if ( in_array( $blog_page, json_decode( $scriptdata->s_pages ) ) ) {
if ( is_page( json_decode( $scriptdata->s_pages ) ) || (!is_front_page() && is_home()) ) {
$out = self::hfcm_render_snippet( $scriptdata );
}
} elseif ( is_page( json_decode( $scriptdata->s_pages ) ) ) {
$out = self::hfcm_render_snippet( $scriptdata );
}
}
break;
With:
case 's_pages':
$is_not_empty_s_pages = self::hfcm_not_empty( $scriptdata, 's_pages' );
if ( $is_not_empty_s_pages ) {
// WPML workaround for compsupp-7802
$original_ids = json_decode( $scriptdata->s_pages);
foreach ( $original_ids as $original_id ) {
$translated_ids[] = apply_filters( 'wpml_object_id', $original_id, 'page');
}
// Gets the page ID of the blog page
$blog_page = get_option( 'page_for_posts' );
// Checks if the blog page is present in the array of selected pages
if ( in_array( $blog_page, json_decode( $scriptdata->s_pages ) ) ) {
if ( is_page( $translated_ids ) || (!is_front_page() && is_home()) ) {
$out = self::hfcm_render_snippet( $scriptdata );
}
} elseif ( is_page( $translated_ids ) ) {
$out = self::hfcm_render_snippet( $scriptdata );
}
}
break;
This modification ensures that the noindex tag is applied to translated pages as well. If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket.
Problem: The client was unable to see the 'Weight (kg): 8,5' header in the translation editor and needed to manually add and translate this segment. Solution: We recommended the following steps: 1. Open the default text in the WordPress Editor. 2. Remove the 'Weight (kg): 8,5' entirely and manually re-add the text without copying and pasting from any other source. 3. Save the changes. 4. Update the translation and check if the text now appears in the translation editor. 5. If the text appears, proceed to add the translation. Additionally, for segments under review or needing formatting, apply the same HTML formatting in the translation using the formatting markers available in the 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.
Problem: The client was unable to add a language switcher to the navigation menu because WPML did not recognize existing menus, likely due to using a Full Site Editing (FSE) Block Theme. Additionally, there were issues with translations appearing as 'In Progress' or disappearing from the list. Solution: 1. Since the site uses an FSE Block Theme, the 'Appearance → Menus' section is unavailable. We recommended adding a Language Switcher block directly in the templates using the Block Editor. For guidance, see the Language Switcher Block Guide. 2. For the disappearing translations, we advised: - Go to 'WPML > Translation Management'. - Select the Navigation Menu 'Navigation 4 Menu' and the template part 'HeaderMy1', then send both for translation. Detailed instructions can be found here: how to send jobs for translation. - After sending, check 'WPML > Translations' to see the jobs listed and take over the translation jobs. 3. If issues persist or if the solution seems outdated or irrelevant, 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 unable to complete translations because the navigation menus are permanently marked as "In progress" and you encounter the message "Save all sentences before finishing". Solution: 1. Check the translation status in WPML > Translation Management. If a translation has been assigned to another translator, it won't appear in WPML > Translations. To address this, resend the page or template for translation from WPML > Translation Management. This action allows you to either reassign it to a different translator or take over the translation yourself. 2. If you open the Advanced Translation Editor for a page that is fully translated, its status will change to "In Progress." To finalize it, simply edit the translations as needed and click "Complete Translations." If you need to reassign the translation, follow the same steps as mentioned above by resending the page or template for translation.
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 for further assistance.
Problem: The client is experiencing issues with their WPML setup on a site under development. Specific problems include the homepage not behaving as expected in translated versions and confusion about URL slugs for translated pages. Solution: 1. For the homepage not appearing correctly in translated versions, ensure that the translated page is defined as the homepage in WordPress settings. This setup typically changes the permalink to include a language code (e.g., /de) when configured correctly. 2. To address issues with URL slugs in translations, the configuration of WPML needs to be checked. If the client wishes to have specific slugs that match the page titles, they can adjust this in WPML settings. Detailed guidance on configuring slugs can be found in the WPML Slug Translation Guide. 3. If the translation progress shows less than 100%, the client should click the "+" in the segment within the advanced editor to complete the translation.
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, feel free to open a new support ticket at WPML Support Forum.
