Custom Work

Problem:
The client needs to extract the URL of each custom taxonomy within a query on a specific page. The code was working correctly before installing WPML and still works if WPML is disabled.
Solution:
When working with WPML, it is necessary to use our hooks such as wpml_object_id and wpml_current_language. Here is an example:

$currentterm = get_field('selezione_categoria', false, true);
$term_id = $currentterm->term_id;
$taxonomy_name = 'product-category';

// Get current language
$current_language = apply_filters('wpml_current_language', NULL);

// Get term children
$termchildren = get_term_children($term_id, $taxonomy_name);
echo '<ul>';
foreach ($termchildren as a child) {

// Get the translated term ID
$translated_term_id = apply_filters('wpml_object_id', $child, $taxonomy_name, true, $current_language);

if ($translated_term_id) {
        $term = get_term_by('id', $translated_term_id, $taxonomy_name);
        echo '<li><a href="' . get_term_link($term->term_id, $taxonomy_name) . '">' . $term->name . '</a></li>';
    }}
echo '</ul>';

Please note that this code is an example, and we cannot provide custom code.

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 the problem persists, please open a new support ticket.

Problem:
I am trying to translate theme strings, but I can't register any. It doesn't matter if I try to do it with function like do_action( 'wpml_register_single_string', 'stegu', 'enter_search_terms', 'Enter search terms' ); or simply using __ . Also, options text fields page from ACF options page can't be translated (it works for acf fields in posts or pages). Link to a page where the issue can be seen: https://test.stegu.pl/

Solution:
For some reasons some of icl tables had positions with id 0. after removing them all works as a charm.

Problem:
You are using pure SQL to duplicate variable products, but the newly created products/variations do not appear in the backend product list or in the product edit page under Product Data => Variations.
Solution:
If you're experiencing this issue, we recommend using the wpml_set_element_language_details hook to programmatically set the default language for your newly created products/variations. To batch add records into wp_icl_translations for these products, you will need to manage the related information in the icl_translations table. For more details on handling this table, please visit WPML Tables documentation.

Please note that this solution might be irrelevant if it's outdated or not applicable to your specific 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 the issue persists, please open a new support ticket.

Problem:
The client wants to set a specific product with a different currency and have other currencies converted from this set currency on a multi-vendor platform using Dokan. The client also inquires if it's possible to set a different main currency for each vendor.
Solution:
We informed the client that currently, WooCommerce Multilingual or WooCommerce does not support setting a specific currency for a vendor, user, or country. However, a future version of WooCommerce Multilingual (5.5) will include a feature to set prices based on the country, but it is still in the early development stage. For now, a custom plugin might be necessary. We suggested checking out the WooCommerce Product Price Based on Countries plugin, although we have not tested this ourselves. For custom development, we recommended contacting certified developers through this link. Additionally, we provided a code snippet using the

wcml_raw_price_amount

hook to convert from the WooCommerce default currency price to another currency, and pointed to the function that auto-updates product prices in other currencies:

$service = \WPML\Container\make( \WCML_Exchange_Rates::class );
$service->update_exchange_rates();

The update_exchange_rates function is defined in the *wp-content/plugins/woocommerce-multilingual/classes/multi-currency/class-wcml-exchange-rates.php* file (line 151).

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 further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
The client is unable to send categories and tags to translators using WPML, and documents are not showing up on the translated site. Additionally, titles and notices were not included in the xliff file and thus not translated.
Solution:
To address the issue of translating categories and tags, we recommend translating the Categories and Tags taxonomy terms manually from WPML>>Taxonomy Translation. Alternatively, create a private post including all the Categories and Tags taxonomy terms, and send that post for translation. For detailed guidance, please refer to our documentation on translating taxonomy terms from a central page and how to translate all taxonomy terms at once.

Please note that the solution provided might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket.