Custom Work

Problem:
The client was facing an issue where the text in the first level of a two-level list was not appearing translated on the front-end in WPML, despite being translated in the WPML translation editor. The issue was temporarily resolved by adding a colon at the end of the first level, but this was not a satisfactory solution.
Solution:
We discovered that the problem was related to incorrect HTML structure within the list. To resolve this, we recommend:
1. Switch to the code editor in your WordPress editor.
2. Copy the entire HTML structure of the problematic list.
3. Use ChatGPT or a similar tool to check and correct the HTML structure.
4. Replace the corrected HTML and save the changes.
This approach should ensure that the translations display correctly without needing to add unnecessary punctuation.

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 function intended to add a page slug as a class to the body tag does not work on WPML translated versions of the site, causing issues with page-specific styling.
Solution:
To ensure the function works with WPML translated versions, you need to modify the function to use WPML's hooks for managing translations. Here is a step-by-step guide:

function add_slug_body_class_wpml_fallback( $classes ) {
$original_id = get_queried_object_id();

// Check if WPML is available
if ( class_exists( 'sitepress' ) ) {
$current_lang = apply_filters( 'wpml_current_language', null );
$translated_id = wpml_object_id( $original_id, 'page', true, $current_lang );
} else {
$translated_id = $original_id;
}

// WPML logic continues
if ( $translated_id ) {
$post_type = get_post_type( $translated_id );
$post_slug = get_post_field( 'post_name', $translated_id );

if ( $post_type && $post_slug ) {
$classes[] = $post_type . '-' . $post_slug;
}
}

return $classes;
}
add_filter( 'body_class', 'add_slug_body_class_wpml_fallback' );

Before implementing this solution, ensure to back up your site and have FTP access ready as a precaution. This modification involves developer-level changes, which are usually beyond standard support scope. For more details on WPML's hooks, visit WPML Hooks Reference.

If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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, please visit our support forum.

Problem:
You are trying to set the width of the language selector in the menu to less than the default minimum width of 200 px when using flags only. This issue arises because the 'Menu language switcher' configuration in the 'Languages' section does not apply changes when adding a language switcher to the beginning or end of an existing menu. Additionally, the menu selector does not detect and list new navigation blocks.
Solution:
The client inserted a class in an outer element of the language selector and applying custom CSS to adjust the width. This approach allows you to override the default settings and achieve the desired width for your language selector. If you're experiencing difficulties with this solution or if it does not fully address your issue, please check our related known issues and verify that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so at our support forum.