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.
