Mary

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 client created a custom post type with associated custom fields using ACF, translated via WPML. They then used Ninja Table to display these fields. While it works in French, in English, the custom field values still appear in French, and the shortcodes added to the table do not display any content.

Solution:
We recommended modifying the function to dynamically retrieve the post type of the

$post_id

instead of hardcoding it. We also suggested adding error handling for missing fields and allowing dynamic shortcode attributes. Here is the revised code:

// Function to get translated ACF fields using WPML
function get_translated_acf_fields($post_id, $language_code = null) {
    if (!$language_code) {
        $language_code = apply_filters('wpml_current_language', null);
    }
    $translated_post_id = apply_filters('wpml_object_id', $post_id, get_post_type($post_id), false, $language_code);
    if (!$translated_post_id) {
        return null;
    }
    $fields = array(
        'ville'      => get_field('ville', $translated_post_id),
        'publics'    => get_field('publics', $translated_post_id),
        'programmes' => get_field('programmes', $translated_post_id),
    );
    return $fields;
}
add_shortcode('ville_field', 'display_ville_field');
add_shortcode('publics_field', 'display_publics_field');
add_shortcode('programmes_field', 'display_programmes_field');

Additionally, we suggested testing the code without Ninja Table first and ensuring that Ninja Table is set as "Translatable" in WPML > Settings > Post Type Translation, then translating the tables and using their respective shortcodes in each language.

If this solution does not resolve your issue or seems irrelevant due to updates or differences in 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.