Custom Work

Problem:
The client is developing a site using a Blocksy child theme and has implemented custom code for WooCommerce warnings in a file named 'ufi-warnings.php'. This code adds a product tab for UFI warnings and allows selection of UFI numbers for products. The client used WPML to translate the product tab into Slovenian and scanned the child theme for custom code translations from Croatian to Slovenian. However, the client encountered issues with the text domain in localization functions.
Solution:
We advised the client to ensure that all hard-coded strings in their PHP code are wrapped in WordPress localization functions like

__()

and

_e()

, and to specify the text domain as a string. This is crucial for the parsing tools to correctly distinguish between different text domains. The client was incorrectly using a variable for the text domain, represented as

$this->text_domain

, which should instead be passed as a string.

For more information on proper localization practices, we recommended visiting: WordPress Developer Resources.

If this solution does not resolve your issue or seems irrelevant due to updates or differences in your case, please open a new support ticket. We also 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.

Problem:
The client needed the Finnish, Latvian, and Lithuanian flags in their WPML language switcher to link to external partner sites instead of internal translations, but the existing jQuery code was not functioning.
Solution:
We recommended adding a custom function to the

functions.php

file of the client's theme. This function modifies the language switcher to include external links for the specified languages. Here is the code to implement:

function custom_language_switcher_links( $languages ) {<br />    $languages['external_1'] = array(<br />        'url' => 'https://www.changepartners.fi',<br />        'native_name' => 'Suomi',<br />        'translated_name' => 'Finnish',<br />        'country_flag_url' => 'https://cdn.wpml.org/wp-content/plugins/sitepress-multilingual-cms/res/flags/fi.svg',<br />        'language_code' => 'fi',<br />        'code' => 'fi'<br />    );<br />    $languages['external_2'] = array(<br />        'url' => 'https://www.changepartners.lv/',<br />        'native_name' => 'Latviešu',<br />        'translated_name' => 'Latvian',<br />        'country_flag_url' => 'https://cdn.wpml.org/wp-content/plugins/sitepress-multilingual-cms/res/flags/lv.svg',<br />        'language_code' => 'lv',<br />        'code' => 'lv'<br />    );<br />    $languages['external_3'] = array(<br />        'url' => 'https://changepartners.lt/',<br />        'native_name' => 'Lietuvių',<br />        'translated_name' => 'Lithuanian',<br />        'country_flag_url' => 'https://cdn.wpml.org/wp-content/plugins/sitepress-multilingual-cms/res/flags/lt.svg',<br />        'language_code' => 'lt',<br />        'code' => 'lt'<br />    );<br />    return $languages;<br />}<br />add_filter( 'icl_ls_languages', 'custom_language_switcher_links' );

Please ensure to back up your site fully before implementing this solution. If this solution does not resolve your issue or seems outdated, we recommend checking related 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.

Problem:
You are trying to set the thousand separator and decimal separator per language in WooCommerce Multilingual & Multicurrency, specifically for displaying prices in Euros with the correct formatting for different countries like Ireland, where the expected format is €1,914.00 instead of the European format €1.914,00.
Solution:
Currently, there isn't a direct way to adjust these settings through the UI for secondary currencies. However, we can achieve this by using WooCommerce filters. We have added the necessary code as a Code Snippet on your site. Here is the code you can use:

/**
 * Force formatting euro prices for the Ireland language
 */

add_filter( 'wc_get_price_thousand_separator', function( $value ) {
    $current_language = apply_filters( 'wpml_current_language', null );

    if ( $current_language === 'en-ie' ) {
        $value = ",";
    }

    return $value;
}, 11 );

add_filter( 'wc_get_price_decimal_separator', function( $value ) {
    $current_language = apply_filters( 'wpml_current_language', null );

    if ( $current_language === 'en-ie' ) {
        $value = ".";
    }

    return $value;
}, 11 );

This code will specifically change the thousand and decimal separators for prices when the site’s language is set to Irish English ('en-ie').

If this solution does not resolve your issue or seems outdated, we 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.

Problem:
You are developing a site and want the WordPress API to respond in English, despite the main website language being different. You tried using the WPML Hook with

do_action('wpml_switch_language', 'en');

but it did not work.
Solution:
We recommend using the

rest_request_before_callbacks

filter to force the WPML language for specific API endpoints. Here is an example of how you can implement this:

add_filter('rest_request_before_callbacks', function ($response, $handler, $request) {<br />    // Specify the endpoints you want to target (or apply globally).<br />    $target_endpoints = ['/wp/v2/posts', '/wp/v2/pages'];<br />    <br />    if (in_array($request->get_route(), $target_endpoints, true)) {<br />        // Switch WPML language context to English.<br />        do_action('wpml_switch_language', 'en');<br />    }<br />    <br />    return $response;<br />}, 10, 3);

Please note that we do not provide support for custom coding issues, but only guidance and examples as shown above. If you need further assistance, you might consider hiring a WPML Contractor.

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.