Problem: You are managing translations for tags using the WPML 'taxonomy translation' tool and have encountered an issue where the Ukrainian translation of a tag separated from its Russian version. This separation resulted in a 301 redirect, and the Russian version created a duplicate Ukrainian translation with the same name. Solution: The issue arises from a mismatch in the database collation settings. Your database's wp_terms table uses the utf8mb3_general_ci collation, which does not fully support non-Latin characters like Cyrillic, while your WordPress configuration is set to use utf8mb4. To resolve this, we recommend updating the collation of your core database tables, particularly wp_terms, to utf8mb4. This update will support a broader range of characters and should prevent similar issues in the future.
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. If the problem persists, we highly recommend opening a new support ticket for further assistance.
Problem: In Classic Editor, when entering a tag name, the AJAX request (ajax-tag-search) does not return some tags in Ukrainian, even though they exist in the database and are correctly translated in WPML. This issue does not occur in Gutenberg. Solution: If you're experiencing this issue, we recommend you go to WPML -> Languages and check the box for
Adjust IDs for multilingual functionality
. This adjustment should resolve the issue by ensuring that the AJAX requests in Classic Editor correctly recognize the language settings.
Please note that 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 deprecated function warnings in their error logs after updating plugins. These warnings are related to the WPML CMS Navigation and Sticky Links plugins and appear due to the use of PHP version 8.2.7, which is not fully compatible with WPML or WordPress yet. Solution: We recommend disabling the debug mode in WordPress to prevent these warnings from being displayed to visitors. This can be done by editing the
wp-config.php
file and ensuring it contains the following line:
define('WP_DEBUG_DISPLAY', false);
For more information on compatibility and this issue, please visit the official WordPress site: WordPress 5.9 and PHP 8.0-8.1. These notices are expected to be resolved in future updates of the plugins.
If this solution does not apply to your case, or if the problem persists, 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.
