If you're experiencing issues with translations not displaying correctly on the frontend when they include Unicode characters like the '📷' (U+1F4F7) camera icon, and the translation only shows the source language text with the icon, this might be due to database collation settings.
Solution:
We recommend updating the collation of your database tables and their columns to
utf8mb4_unicode_520_ci
. After updating, modify and save the page in the original language and update the translation. This should allow the correct display of Unicode characters in translations. If you encounter styling issues in translated text blocks post-update, try the following steps:
1. Open the original language page for editing. 2. Make a small change (like adding a space or a word) and save it. 3. Update the translation. 4. Clear all caches and check if the styling issue persists.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant 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 problems persist, please open a new support ticket.
Problem: If you're experiencing 404 errors on WooCommerce product category archive pages when the WPML String Translation plugin is active, specifically in the default French version, this might be due to incorrect slug translations between French and English. Solution: We recommend checking the WPML > Settings > Taxonomy translation to ensure that the slugs are correctly translated. If the issue persists, try deleting the translations and reconfiguring the 'product' and 'product category' permalinks, then set up the translations again. This approach addresses potential database issues with permalink translations that may have occurred during a recent plugin update.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and check if there's a permanent fix available. Ensure you have the latest versions of themes and plugins installed. If problems continue, we highly recommend opening a new support ticket at WPML support forum for further assistance.
The client reported an issue where the system hung with the message 'unable to retrieve job details' after applying a workaround for a previous problem.
Solution:
We suggested that this might be a temporary issue. As a first step, we recommend checking for any recent errors or warnings related to WPML:
- Look in the wp-content/debug.log file (if debugging is enabled)
- Visit WPML >> Support >> Advanced Translation Editor >> Error Logs to review any recent errors.
Additionally, if the problem remains, please try the following steps:
- Go to WPML >> Translation Management >> Translation Jobs
- Cancel the translation job for the affected page
- Go to Pages >> All Pages
- Please make a small change to the original page and save it
If the issue persists and the provided solution does not resolve the problem, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Also, 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. For further assistance, you can contact us through the WPML support forum.
Problem: If you're trying to enable the WPML plugin on your site but cannot access the wp-admin after doing so, it might be due to a compatibility issue with other plugins or your theme. Specifically, you might encounter an error message preventing access to the wp-admin.
Solution:
First, ensure you are using WPML version 4.7.6 and enable the WordPress Debug log to collect more details about the issue. Modify your wp-config.php file as follows:
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
After enabling debugging, reproduce the issue and check the debug.log file in the /wp-content/ directory for any errors related to WPML. If you find errors such as a PHP Fatal error related to the SimpleXML extension, this indicates that the SimpleXML extension is not active on your server. Contact your hosting provider to enable the SimpleXML extension. For more information, visit the following links:
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, 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.
The client was experiencing errors on their Arabic version of the site after updating string translations.
Solution:
We identified that the issue was due to incorrect translation of placeholders within strings. Specifically, the string "%s days" from the "Payment Plugins for Stripe WooCommerce" plugin was not correctly translated into Arabic. We recommend checking and correcting similar translations.
After making these corrections, we suggest taking a site backup, then verifying the functionality by navigating through the Arabic posts, translating a few posts, and making some test purchases to ensure the issue is resolved.
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. Should the problem persist, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client was unable to translate testimonials and FAQ sections on certain pages of their website using WPML's Advanced Translation. The second page was also disconnected from Advanced Translation, and changes were not reflected on the translated page. Solution: We identified that the client was using custom widgets to display the FAQ and Testimonials, which needed to be registered for translation. We recommended registering the custom Elementor widgets following the guide at https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/. Additionally, we suggested resaving the affected pages to allow the Advanced Translation Editor to resync the content. We also installed a multilingual tool plugin to address errors preventing the completion of translations and deactivated conflicting plugins to further diagnose the issue.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported inconsistencies in product sorting across different language pages on their WooCommerce site, even after previous code adjustments. Solution: We provided custom code to ensure consistent sorting by date, SKU, price, and popularity across all language versions of the site. Here are the steps we recommended:
//Use the below snippet when sorting by price and popularity, so that SKU is used as the secondary sort option:
add_filter('posts_clauses', 'custom_orderby_with_secondary_sku', 20, 2);
function custom_orderby_with_secondary_sku($clauses, $query) {
if (!is_admin() && $query->is_main_query() && is_woocommerce() && isset($_GET['orderby'])) {
$orderby = $_GET['orderby'];
// Define primary column and direction based on ordering
switch ($orderby) {
case 'price':
$primary_column = 'wc_product_meta_lookup.min_price';
$primary_direction = 'ASC';
break;
case 'price-desc':
$primary_column = 'wc_product_meta_lookup.max_price';
$primary_direction = 'DESC';
break;
case 'popularity':
$primary_column = 'wc_product_meta_lookup.total_sales';
$primary_direction = 'DESC';
break;
default:
return $clauses; // Not a target orderby value, leave alone
}
// Set ORDER BY with SKU as secondary sort
$clauses['orderby'] = "
{$primary_column} {$primary_direction},
wc_product_meta_lookup.sku ASC
";
}
return $clauses;
}
If this solution does not resolve your issue or seems irrelevant due to updates or specific circumstances, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
