Problem: If you're experiencing issues with the styling of your custom language switcher, specifically with the "Hover" settings for "Other language font color" and "Other language background color" not working as expected on the frontend, this might be due to a CSS conflict or misconfiguration. The hover effect might be incorrectly applied to the current language instead of the available translation links. Solution: We recommend applying custom CSS to correct this issue. You can add the necessary CSS by navigating to WP > Appearance > Customize > Additional CSS in your WordPress dashboard.
.wpml-ls-statics-shortcode_actions a, .wpml-ls-statics-shortcode_actions .wpml-ls-sub-menu a, .wpml-ls-statics-shortcode_actions .wpml-ls-sub-menu a:link, .wpml-ls-statics-shortcode_actions li:not(.wpml-ls-current-language) .wpml-ls-link, .wpml-ls-statics-shortcode_actions li:not(.wpml-ls-current-language) .wpml-ls-link:link {
color: #000000;
background-color: #ffb536;
}
If this solution does not resolve your issue or seems irrelevant because it 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing an issue where WPML is not filtering WooCommerce product categories by language on the frontend. All categories from all languages (Greek, English, Bulgarian) are showing together in category widgets and menus.
Solution: We recommend adding
suppress_filters=0
or
suppress_filters = false
to the arguments in your
get_terms()
function to ensure that taxonomy queries return results only in the currently viewed language. For more details on how to implement this, please refer to our documentation on achieving WPML compatibility for themes and plugins: Filter Correct IDs.
Please note that this solution might be irrelevant if it's 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 for further assistance.
Problem: The client has a custom post type called 'resources' with an accompanying custom Gutenberg block called 'resource feed'. This block is dynamic and displays data from entries in the feed. However, it does not display different content based on the selected language, showing the same content across all languages. Solution: We recommend using the
wpml_object_id
hook to ensure that the
$post_id
refers to the translated post in the currently active language. Here is how you can implement it:
// will return the post ID in the current language for post ID 1
echo apply_filters( 'wpml_object_id', 1, 'post' );
// will return the category ID in the current language for category ID 4. If the translation is missing it will return the original (here: category ID 4)
echo apply_filters( 'wpml_object_id', 4, 'category', TRUE );
// will return the German attachment ID for attachment ID 25. If the translation is missing it will return NULL
echo apply_filters( 'wpml_object_id', 25, 'attachment', FALSE, 'de' );
If this solution does not resolve your issue or 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. We highly recommend opening a new support ticket for further assistance at WPML support forum.
