Problem: After updating to WPML 4.7.4 and String Translation 3.3.3, issues arose with post categories not being recognized correctly on the front end when using Elementor. Disabling String Translation temporarily resolved the issue, indicating a compatibility problem between the updated versions of WPML, String Translation, and Elementor. Solution: We identified that the issue stems from Elementor using
term_taxonomy_id
instead of
term_id
, which our code did not anticipate, leading to all results being shown without filtering by a taxonomy term. A fix for this issue will be included in the upcoming WPML 4.7.5 release. Meanwhile, we provided a workaround involving a code modification in
. This modification should be tested on a staging site after taking a full backup. If this solution does not resolve your issue or seems outdated, please check for related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and if necessary, open a new support ticket at WPML support forum.
After migrating from a staging site to a test site, most of the text displays incorrectly, showing special characters and question marks. Additionally, the media section shows blank images, though the images exist.
Solution:
If you're experiencing issues with special characters and question marks after migration, it's likely due to the database collation setting. We recommend changing your database collation to either utf8mb4_unicode_ci or utf8mb4_unicode_520_ci to support non-Latin characters properly. Before making changes, ensure you back up your site fully. You can run the following SQL query for each table:
ALTER TABLE your_table_name CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;
For example:
ALTER TABLE wp_posts CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;
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 issue persists, please open a new support ticket at WPML support forum.
Problem: The user is seeing an error in the WPML Advanced Translation Editor Logs indicating a change in your site's URL. This error appears because WPML has detected a URL change and needs confirmation whether the site has been moved or copied. Solution: First, ensure you have a full backup of your site. Then, follow these steps: 1) Navigate to WPML>>Settings>>Translation Editor. 2) Select the Advanced Translation Editor (recommended) option. 3) Go to WPML>>Translation Management. 4) Check if the Site Moved wizard is showing. If it is, select the option for Changing to a New Site URL and complete the wizard steps. For more detailed instructions, please refer to the documentation on using the Advanced Translation Editor when you move or use a copy of your site.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise 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.
