Custom Work

Problem:
The client is experiencing issues with creating English courses using Learndash on an Italian website. The permalinks for the courses are incorrect and not translated, leading to 404 errors and too many redirects.
Solution:
1. Ensure that Learndash is translated using the WordPress Editor. For more details, visit https://wpml.org/plugin/learndash-lms/.
2. Duplicate the course with WPML and set it as independent. Adjust the permalink settings in WordPress and translate the slug in WPML > Settings > Post Type Translation.
3. Take note, that this issue was related to custom code in the child theme's functions.php file and we provided a workaround for the issue.
5. Verify that the custom post type slug is translated in WPML > Settings > Post Type Translation. For more information, visit https://wpml.org/documentation/getting-started-guide/translating-page-slugs/.

If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. Additionally, 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. For further assistance, visit our support forum.

Problem:
The client is trying to translate customized fields using WPML but encounters an issue where the translations do not appear on the frontend. The client used a custom hook and registered labels to WPML, translating them successfully. However, despite following documentation and using code examples, the translations are not visible on the frontend.
Solution:
1. Ensure the text domain is correct. According to WordPress documentation, the text domain must use dashes, be lowercase, and have no spaces.
2. When using variables in translated strings, use the

printf()

function instead of echoing the variable directly. For example, change:

<p id="popup-title"><?= $popuptitle ?></p>

to:

<p id="popup-title"><?php echo __('Subscribe Now, Save 10%', 'storefront') ?></p>

After making these changes, re-scan the strings in the child theme, translate the string, and check if the translation displays on the frontend.
3. If using a custom text domain like "popup", register it with the following function in your theme's

functions.php

file:

add_action( 'after_setup_theme', function() {
    load_theme_textdomain( 'popup', get_template_directory() . '/languages' );
} );

Refer to the WordPress documentation on loading a text domain for more details.

If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also highly suggest 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.

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.