Custom Work

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.

Problema:
Utilizzi Gravity Form con l'addon ufficiale per creare articoli su WordPress in un sito multilingua (italiano, inglese, francese), ma quando un form viene compilato in inglese, l'articolo risultante viene creato in inglese anziché in italiano, la lingua base del sito.
Soluzione:
Questo è il comportamento atteso di Gravity Form quando utilizzato in un contesto multilingua. Una possibile soluzione è non tradurre il form o impostare il tipo di post risultante come non traducibile. Questo potrebbe far sì che gli articoli vengano creati sempre in italiano, indipendentemente dalla lingua in cui il form è stato compilato. Se questa soluzione non dovesse essere adeguata, l'unica alternativa sarebbe creare del codice personalizzato, che però non possiamo fornire.

Se questa soluzione non risolve il problema o se è inapplicabile al tuo caso, ti consigliamo di verificare i problemi noti e di assicurarti di avere installato le versioni più recenti dei temi e dei plugin. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.

Problem:
You are trying to get the sitemaps working for all languages on your website using the WPML SEO plugin and Yoast Premium. However, sitemaps are only working for the primary language and not for other languages.
Solution:
We recommend checking if you are using different language domains, as this functionality is primarily available in such setups. You can find more details on this in our documentation: Using WordPress SEO with WPML.
Please note that sitemap generation is managed by Yoast, not by us. If you need separate sitemaps for each language and are not using different domains, you might need to implement a custom solution, as this falls outside the standard behavior.

If this solution does not apply to your case, or if it seems outdated, 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 you still need assistance, please open a new support ticket at our support forum.

Problem:
The client wants to format the language switcher in their website header to display languages with a '/' between them, specifically as 'EN/GR'.
Solution:
If you're experiencing this, we recommend you follow these steps:
1. Enable the language switcher.
2. Configure it to show only language codes by following the instructions here: https://wpml.org/forums/topic/use-language-abbreviations-in-menu-language-switcher/
3. Use custom CSS to add '/' between the languages. Here is an example of how you can do it:

.wpml-ls li.wpml-ls-item a:after {
   content: "/";
    margin-left: 13px;
}
.wpml-ls li:last-child.wpml-ls-item a:after {    
content: "";
}

This solution might be irrelevant if it's 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 this does not resolve your issue, please open a new support ticket at WPML support forum.