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.
instead of string concatenation. Solution: We recommend updating to WooCommerce Multilingual version 5.5.0 or higher, as this update addresses the issue. If the problem persists after updating, or if this solution does not apply to your case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins.
If you still need assistance, we encourage you to open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where the admin notice contains an invalid URL, this might be due to the lack of URL arguments on certain pages like the dashboard. Solution: We plan to address this in a future release. Meanwhile, you can use the following workaround:
Additionally, this issue was resolved in WooCommerce Multilingual version 5.5.0.
Please note that this solution might be outdated or not applicable to your specific case. We highly 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 the problem persists, please open a new support ticket.
Problem: The client reported an issue related to WooCommerce Multilingual. Solution: We resolved this issue in WooCommerce Multilingual version 5.5.0. If you're experiencing this issue, we recommend updating to this version. Please check the known issues page to verify the version of the permanent fix and confirm that you have installed the latest versions of themes and plugins.
If this solution does not apply to your case, or if it seems outdated, please do not hesitate to open a new support ticket. We highly recommend visiting the WPML support forum for further assistance.
If you're experiencing PHP deprecated warnings in your WooCommerce Multilingual plugin, similar to the ones reported where the required parameter $wpdb follows an optional parameter $post_translations in the file class-wcml-products.php, this summary is for you.
Solution:
We have escalated this issue to our developers, and a fix will be included in a future version of the WooCommerce Multilingual & Multicurrency plugin (most probably in 5.5.1). We recommend waiting for this update, which will address the deprecated parameter order issue.
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 problem persists, please open a new support ticket.
