Problem: The client needed to retrieve the currency list with the exchange rates for their site using WPML and was unsure which hook to use. Solution: We advised the client to access the currency list and exchange rates through the
_wcml_settings
option in WordPress, which is a serialized array containing WooCommerce Multilingual (WCML) settings. Specifically, the
currency_options
key within this array holds the necessary data. Here is a step-by-step guide on how to retrieve this information:
function get_wcml_currency_rates() {
$wcml_settings = get_option( '_wcml_settings' );
if ( ! isset( $wcml_settings['currency_options'] ) ) {
return [];
}
$currency_options = $wcml_settings['currency_options'];
$rates = [];
foreach ( $currency_options as $currency_code => $currency_data ) {
// WCML may store 'rate' as string or float
$rate = isset( $currency_data['rate'] ) ? floatval( $currency_data['rate'] ) : 0;
// Only include if rate is > 0
if ( $rate > 0 ) {
$rates[ $currency_code ] = $rate;
}
}
return $rates;
}
//For testing
$rates = get_wcml_currency_rates();
echo '<pre>';
print_r($rates);
echo '</pre>
<p>';<br />
// Output might be: ['USD' => 1.08, 'GBP' => 0.86, 'AUD' => 1.64]<br />
Please note that we do not typically provide custom code solutions. For further customization, you might need to hire an independent contractor.
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.
If this solution does not resolve your issue or seems outdated, please check the related known issues and verify that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client is attempting to save custom field data for a WooCommerce variable product using the WPML plugin. They have added custom price fields but encounter an issue where the product page reloads and displays nothing after saving the variable custom field data. Solution: We clarified that the 'wcml_product_custom_prices' filter is intended for currency conversion, not for language translation or updating postmeta on translated products. To handle custom fields correctly across different languages, the client should ensure that they are using the WPML object ID filter to get the correct product ID for each language. This approach helps in storing custom field values separately for each language. If the client is not planning to use different prices per language but wants to enable translation of the custom field, they should: 1. Add the custom field for each product (_purchase_cost). 2. Enable the translation of that custom field per language via WPML. 3. Store the custom field values separately for each language, ensuring that the values are saved correctly when the product is edited in different languages. For further assistance, 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 at https://wpml.org/forums/forum/english-support/.
Problem: The client was experiencing issues with translating a WooCommerce composite product into Italian using WPML. The translation process was not functioning correctly, sometimes affecting the default English product as well. Specifically, when scenarios were added to composite products, the component dropdown options were not displaying correctly in the Italian version, though they worked fine in English.
Solution: We advised the client to ensure that all plugins were up to date and to use the Advanced Translation Editor (ATE) for translating products. It was important to translate using ATE rather than the WordPress Editor to avoid issues with saving changes and to ensure the translation process was handled correctly by WPML. We also suggested translating the products step-by-step using ATE and checking if the issue persisted. If problems continued, we recommended deactivating the WPML plugins temporarily to verify if the issue was indeed related to WPML or if it was an issue with the WooCommerce Composite Products plugin.
Please note that this solution 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 problem persists, please open a new support ticket here.
