Problem: You are trying to locate the hreflang tags in your sitemap using WPML, WPML SEO, and Rank Math SEO, but cannot find them despite having checked the 'as early as possible' option in WPML -> SEO options -> Display alternative languages in the HEAD section. Solution: Hreflang tags will not appear in your sitemap but should be visible at the top of your page source due to your current settings. You can verify their presence by viewing the source of your page. For example, you might see entries like:
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client is using ACF Pro with a Gallery field set to 'Hide from library', which works correctly in the primary language by hiding images from the WP Media Library. However, in the secondary language (Swedish), the images are still visible in the media library. Solution: We first clarified that the 'Hide from library' feature might be misunderstood as it is intended to limit file selection to those uploaded to the post, not hide them from the Media Library entirely. We also identified that the 'Frontend Admin' plugin, which is not compatible with WPML, might be causing the issue. We recommended contacting the plugin author to request compatibility with WPML through our Go Global program (https://wpml.org/documentation/support/go-global-program/).
If this solution does not resolve your issue or seems irrelevant, we highly recommend checking related known issues (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.
Problem: You are using the User Ranks widget from GamiPress on your site with Elementor Pro and have translated the strings in WPML's String Translation. However, the widget does not translate on the frontend in the secondary language. Solution: Elementor Widgets cannot be translated directly using WPML > String Translation. Instead, you need to use the WPML Translation Editor, which by default supports all widgets that come with Elementor and Elementor Pro. Custom Elementor Widgets require an XML configuration to be translatable with the WPML Translation Editor. This configuration should ideally be provided by the plugin author in a
wpml-config.xml
file in the plugin's root directory. You can find a guide on how to register page builder widgets for translation here. If the plugin author does not provide this configuration, you can create one yourself and store it under WPML > Settings > Custom XML Configuration. Additionally, we offer a program to assist theme and plugin authors in making their widgets compatible, which you can mention to the author: here. Alternatively, you can use the WordPress Editor as the translation method. Instructions for translating with the WordPress editor can be found here.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues here, 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 here.
Problem: The client needed assistance with translating BuddyBoss Group Types using WPML. Solution: 1. Navigate to WPML > Settings > Custom Field Translation and click on "Show system fields". 2. Locate the fields as shown in the provided screenshot here https://wpml.org/forums/topic/buddyboss-group-type-translation/#post-15380730 and set them to "Translate". 3. When editing a Group in the WordPress Editor, ensure the correct Group Type is selected in the right sidebar. 4. Switch the language using the top admin bar and verify that the translation uses the translated Group Type.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we encourage you to check the related known issues and confirm that you have the latest versions of themes and plugins installed. If necessary, please open a new support ticket for further assistance.
Problem: The client is trying to translate group types in BuddyBoss and use the same group in different languages, but is facing an issue where a group type for a given group can only be assigned in one language. When switching to a secondary language, no groups with the translated group type are found.
Solution: Even though it is possible to translate group types with WPML, it is not yet possible to translate Groups. A request has been made internally go our development team to review the possibility of adding such a feature in a future version of our add-on BuddyPress Multilingual.
Problem: The client is unable to translate the content of the gender field (Male / Female) in BuddyPress, even though the word "Gender" gets translated. Solution: We recommend using the following custom code to translate BuddyPress profile fields:
//WPML Workaround wpml_compsupp-7149
add_filter( 'bp_get_the_profile_field_value', 'wpml_compsupp6144_translate_buddypress_profile_fields', 10, 3 );
function wpml_compsupp6144_translate_buddypress_profile_fields( $value, $type, $id ) {
if ($type == 'textbox' || $type == 'wp-textbox' || $type == 'wp-biography' || $type == 'gender') {
//remove html tags from value and limit it's size, so we can use it as string name
$filtered_value = substr(strip_tags($value), 0, 60);
//register string
do_action( 'wpml_register_single_string', 'BuddyPress Profile Fields', $type.' - '.$filtered_value , $value );
//translate string
$value = apply_filters('wpml_translate_single_string', $value, 'BuddyPress Profile Fields', $type.' - '.$filtered_value );
}
return $value;
}
Problem: The client needs to display all posts in all languages on a listing or social media website with frontend submission, without translating them. The issue is that the Translation Management (TM) only allows duplicating content from the site's default language, and not in bulk for content created in other languages. Solution: We regret to inform you that we do not plan to implement a feature for duplicating original content not created in the site's default language in bulk. However, we offer a hook that can be used on the Frontend to create duplicates in WPML when a post is published, regardless of the post's default language. You can find more information about this hook here:
Problem: The client needed assistance with making the Google Reviews shortcode visible on the translated pages of their Custom Post Types (CPTs) without needing to translate the shortcode itself, as the review score remains the same across all languages. Solution: In this case, the problem was solved by going to WPML -> Settings and setting the "Reviews widgets (grw_feed)" to not translatable.
If this solution doesn't seem relevant to your situation, please feel free to open a new support ticket with us.
Problem: The client is experiencing issues with taxonomies not being automatically added to translated terms in custom post types. The client only wants to translate Elementor templates and expects the terms added to custom post types in the original language to be automatically available in all translated versions.
Solution: We explained that taxonomies are not automatically copied to translated custom post types. The client needs to translate the custom post types first, which will then allow WPML to copy the taxonomies. We asked if the client had translated the custom post types after creating those taxonomies.
If this solution does not seem relevant, we encourage the client to open a new support ticket for further assistance. Please visit our WPML support forum.
