Problem: The client attempted to automatically translate a Privacy Policy page from English to Hebrew but encountered issues where only the title was translated, and the rest of the text remained in English. Despite having sufficient credits, the system used 5,356 Pay-as-You-Go credits, costing €2.52. This was due to the site registered in the WPML.org account not matching the live website’s ID, leading to credits not being assigned correctly. Solution: We manually moved the translation credits to the correct live site and adjusted the debt so the client will not be charged. We recommend the client to re-register their site with WPML to ensure the WPML.org account reflects the correct instance. Here are the steps to follow: 1. In the WordPress dashboard, go to Plugins → Add New → Commercial. 2. Click Unregister for WPML. 3. Visit https://wpml.org/account/sites/ and delete the existing site key. 4. Back in Plugins → Add New → Commercial, click Register and complete the registration to generate a new key.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported an issue where the admin receives New Order Emails in Hebrew with incorrect left alignment, despite the admin's language setting being Hebrew. This misalignment occurs when the site language is set to English, and the admin's language is set to Hebrew. Solution: We confirmed that this issue is specific to WPML handling Hebrew language emails. We have escalated the problem to our development team for a permanent fix. Meanwhile, we recommend setting the admin language to Hebrew before changing the status of an order that will send an email. Additionally, you can try adding the following code snippet to your theme's functions.php file, but please ensure you have a backup before implementing:
/**
* Fix the text direction attribute when switching language to an RTL language.
*
* @see https://onthegosystems.myjetbrains.com/youtrack/issue/wcml-3838/
*/
add_action( 'wpml_language_has_switched', function ( $newLangCode ) {
/**
* @var \WP_Locale|\WPML\ST\MO\WPLocaleProxy $wp_locale
* @var string $text_direction
* @var \SitePress $sitepress
*/
global $wp_locale, $text_direction, $sitepress;
static $secondaryWPLocales = [];
if (
$wp_locale instanceof \WPML\ST\MO\WPLocaleProxy
&& $sitepress->is_rtl( $newLangCode )
) {
if ( ! isset( $secondaryWPLocales[ $newLangCode ] ) ) {
$text_direction_bk = $text_direction;
$text_direction = 'rtl';
$secondaryWPLocales[ $newLangCode ] = new \WP_Locale();
$text_direction = $text_direction_bk;
}
$wp_locale = $secondaryWPLocales[ $newLangCode ];
}
}, 20 );
Please note that 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: If you're using WooCommerce with WPML, WooCommerce Multilingual & Multicurrency, and encountering an issue where a vendor tries to purchase a membership product with a custom price set in ILS currency, and the subscription with Stripe is not created due to a SQL syntax error caused by the WCML (multicurrency), this might be relevant to you:
WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ')' at line 3 for query SELECT post_id, meta_key, meta_value FROM wp_postmeta
WHERE meta_key IN ('_price', '_regular_price', '_sale_price', '_price_ILS', '_regular_price_ILS', '_sale_price_ILS')
AND post_id IN () made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), do_action('template_redirect'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action('wc_ajax_checkout'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Stripe_UPE_Payment_Gateway->process_payment, WC_Stripe_UPE_Payment_Gateway->process_payment_with_deferred_intent, WC_Stripe_UPE_Payment_Gateway->process_payment_with_payment_method, WC_Stripe_Payment_Gateway->process_response, WC_Order->payment_complete, WC_Order->save, WC_Order->status_transition, do_action('woocommerce_order_status_processing'), WP_Hook->do_action, WP_Hook->apply_filters, wc_update_total_sales_counts, do_action('woocommerce_recorded_sales'), WP_Hook->do_action, WP_Hook->apply_filters, WCML_Synchronize_Product_Data->sync_product_total_sales, WC_Data_Store->__call, WC_Product_Data_Store_CPT->update_product_sales, WC_Data_Store_WP->update_lookup_table, WC_Product_Data_Store_CPT->get_data_for_lookup_table, get_post_meta, get_metadata, get_metadata_raw, apply_filters('get_post_metadata'), WP_Hook->apply_filters, WCML_Multi_Currency_Prices->product_price_filter, WPMLFP{closure}, call_user_func_array, WPMLFPLogic::WPMLFP{closure}, WCML_Multi_Currency_Prices->{closure}, WCML_Custom_Prices->get_product_custom_prices
Solution: We recommend taking a full backup of your website and database first. Then, in the file
This change should resolve the SQL error and allow the Stripe subscription to be created correctly.
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 issues persist, please open a new support ticket.
Problem: After updating WooCommerce Multilingual & Multicurrency to version 5.5.0, a deprecated error appears on each page of the website, indicating an issue with the order of parameters in the code:
Deprecated: Optional parameter $post_translations declared before required parameter $wpdb is implicitly treated as a required parameter in /wp-content/plugins/woocommerce-multilingual/inc/class-wcml-products.php on line 33
Solution: We have released an update, WCML version 5.5.1, which addresses this issue. We recommend updating to the latest version of WCML to resolve the deprecated error. You can view the complete changelog and download the update from here.
Please note that 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: You are trying to translate a string from Hebrew to English using the
wpml_translate_single_string
hook in WPML, but it fails to translate into the website's default language (English), while it successfully translates into Russian. Solution: The
wpml_translate_single_string
hook does not translate into the default language because WPML assumes the string in the default language is the original value and does not store translations for it. To retrieve a translation based on the current language, use the default language string as the source and pass the current language as the target:
This method uses the default language string ('Subject en') as the source, and WPML looks up the appropriate translation for the current language. For further understanding, you might find these guides helpful:
If this solution does not apply to your case, or if it 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: WPML Support Forum.
Problem: The client is facing an issue where translated products on their website do not automatically use the same image as the original product. They want to avoid duplicating the image in the media folder and ensure that the same photo is used across all languages. Solution: We recommend following these steps to ensure that the same image is used across all languages when translating a product: 1. When creating or editing a product in the original language, navigate to the right column to the Language block. 2. At the bottom of this block, select the two checkboxes to duplicate the featured image and the attached media. 3. Save the changes. 4. If necessary, update the product translation and double-check that the translated product now displays the same images as the original. For more detailed guidance, please refer to the first FAQ at the end of our documentation here: WPML Media Translation FAQ.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client experienced an issue where Hebrew URLs were being translated despite settings indicating they should not be.
Solution:We requested the client to update the pages and it's translations which fixed the issue.
If this solution seems outdated or not applicable to your case, we recommend opening 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: After changing the primary site language from Hebrew to English, the WCFM plugin control panel still displays Hebrew strings for both languages. Solution: If you're experiencing this issue, we recommend you try the following steps: 1) Navigate to WPML -> String Translator and check if the string is already translated. Then, go to WPML -> Support -> Troubleshooting, click on "Show custom MO Files Pre-generation dialog box", refresh the page to display the MO files dialog box, and regenerate the MO Files. 2) Ensure you have a backup of your site. Disable all other plugins, leaving only WPML and WCFM plugins active, and switch to the WordPress default theme to check if the issue still occurs.
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 at WPML support forum for further assistance.
Problem: The client is experiencing intermittent 'Internal Server Error' messages when trying to access translated pages on a website with WPML and WCFM installed. The hosting company suggested that the issue might be related to a misconfiguration in the htaccess file. Solution: We recommended the following steps to resolve the issue: 1. Take a backup of the site for safety reasons. 2. Add the following code in the functions.php file of the theme:
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 the issue persists, please open a new support ticket at WPML support forum.
Problem: If you're trying to register as a vendor on a Hebrew website using an English registration form and the Email Verification Code sent to you is aligned to the right instead of the left, this might be due to the language settings affecting the email styling. Solution: We recommend switching the language of your emails before sending them. You can use the
. Replace the existing WooCommerce email header action with a new block that switches the language context based on the user's email. Here's the code you should use:
Ensure to set the text alignment in the HTML body of the email template to respect the left or right text direction based on the language context. At the end of the file, add the following code to switch the language back:
<?php
// switch language back
if( apply_filters( 'wcfm_allow_wpml_email_translation', true ) ) {
do_action('wpml_restore_language_from_email');
}
?>
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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're seeing multiple versions of the 'Single Posts' template in WPML under WP > WPML > Translation Management and WP > WPML > Translations, it might appear that these templates have been duplicated erroneously. Solution: We recommend checking if these duplicates share the same ID by searching for _wp_page_template in your database. This issue might not be caused by WPML, as WPML links duplicates to the original using a trid field, and assigns different IDs to duplicates. To further investigate, try deactivating WPML temporarily after creating a full backup. If the templates still appear, they likely exist independently of WPML and can be removed directly from the database.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML support forum.
