Problem: Вы пытаетесь удалить теги HREFLANG на определённых страницах, таких как страницы входа и аккаунта, используя пользовательский код, который не работает. Solution: В WPML, вы можете отключить теги hreflang для всех страниц и языков через WPML > Языки > Параметры SEO. Однако, удалить hreflang только для определенных страниц невозможно. В качестве альтернативного решения, вы можете пометить эти страницы как неиндексируемые с помощью плагина Yoast SEO.
Если данное решение окажется неактуальным или не подходит под ваш случай, мы настоятельно рекомендуем проверить список известных проблем, убедиться в актуальности версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов. Если проблема сохраняется, пожалуйста, откройте новый тикет поддержки.
Problem: The client reported significant slowdowns on their staging site after installing WPML, with page load times increasing to 6-10 seconds. This issue was not present on a similarly configured site without WPML. The client tried various optimizations, including disabling WPML SEO and WPML String Translation modules, which improved load times.
Solution: We recommended migrating the site to our Cloudways testing environment to isolate the problem. The client used the Cloudways WordPress Migrator plugin for this purpose. After migration, we discovered that the combination of Admin Columns Pro, ACF, and ACFML plugins significantly impacted performance. We provided a temporary workaround by modifying the
translateField
method in the ACFML plugin to prevent certain processes from executing in the admin area, which improved backend performance. We also advised on general performance enhancements such as using PHP 8, enabling caching, and optimizing database indexes.
Please note that this solution might not be relevant if it's 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 client is experiencing a critical error due to a high number of autoloaded options in their WordPress site, which is affecting site performance. They need guidance on reducing these options, creating a custom XML configuration file for WPML, and whether installing an object caching plugin would help. Solution: To reduce the number of autoloaded options, ensure that the 'autoload' setting for the 'wpml-tm-custom-xml' option is set to 'off'. If it's not, you can adjust this manually. If a wpml-config.xml file already exists on your site, you can manage it under WPML -> Settings -> Custom XML Configuration (tab). If you're unsure whether the file exists, it's safer to leave it as is. For detailed instructions on creating a wpml-config.xml file, visit https://wpml.org/documentation/support/language-configuration-files/. Regarding the installation of an object caching plugin like Redis or Varnish, while it's not directly related to the autoload issue, it is generally recommended to enhance site performance. More information can be found here: https://wpml.org/faq/prevent-performance-issues-with-wpml/.
If this solution does not fully address your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing slow website and backend speeds, suspecting that WPML and its translated content might be causing conflicts or using excessive processing/data/storage space. Additionally, there is concern about a large error log related to WPML. Solution: We reviewed the wp-config.php file via FTP and confirmed that the debug.log was enabled but did not show any serious issues with WPML. To prevent the file from growing and potentially causing storage problems, we deactivated the debug.log. We also clarified that the link provided by the client (https://revoltbikes.nl/wp-admin/admin.php?page=sitepress-multilingual-cms%2Fmenu%2Fdebug-information.php) is not an error log but a debug information page useful for our support team. After checking the site's frontend and backend, we did not observe any significant performance issues. We recommend the client specify where the performance issue is noticeable and why WPML is suspected to be the cause for further assistance.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client is experiencing issues with many autoloaded options in the WordPress database related to WPML, as indicated by the WordPress Site Health Status. Solution: We recommend checking the "Autoloaded" data from the wp_options table using the following SQL query to identify the size of each autoloaded option (size will be in KB):
SELECT option_id, option_name, sum(char_length(`option_value`))/1024 as size FROM `wp_options` WHERE `autoload` = 'yes' GROUP BY option_id ORDER BY size DESC
After running this query, share the results with us for further analysis. It's important to note that WPML requires its autoloaded data for proper functionality, so we do not recommend disabling autoload for WPML-related options. For other plugins or themes, only consider removing options if they are no longer in use, and always ensure you have a recent backup before making any changes.
If this solution does not apply to your case, or if it seems outdated, please check for 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 issues persist, we highly recommend opening a new support ticket for personalized assistance.
Problème : Le serveur monte en charge fortement, utilisant intensivement MySQL, ce qui provoque le reboot du service. Les requêtes MySQL sont nombreuses malgré un faible trafic Apache, et cela semble lié à WPML. Solution : 1. Vérifiez la version de PHP : Assurez-vous que tous les serveurs sont mis à jour vers au moins PHP 7, car la référence à "https://cdn.wpml.org/.fpm/php5.external" suggère qu'un des serveurs utilise encore PHP 5. 2. Examinez le problème avec le plugin GFML : Traitez le problème spécifique lié au plugin GFML en consultant la documentation ici : https://wpml.org/fr/forums/topic/gravity-forms-multilingual-plugin/#post-15898509 3. Envoyez-nous la requête SQL complète qui se produit lorsque le serveur reboot pour une analyse plus approfondie.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: The client is experiencing an issue where WPML String Translation is running too many slow queries, as reported by their hosting provider. Solution: If you're encountering similar issues, we recommend the following steps: 1. Create a backup of your website, or ideally, test these changes on a staging version to avoid disrupting your live site. 2. Navigate to WordPress Dashboard > WPML > Settings and ensure you select the first option for custom post types, especially for 'products' which currently might be using a less optimal setting. 3. Go to WordPress Dashboard > WPML > Support > Troubleshooting and perform the following actions: - Clear the cache in WPML - Remove ghost entries from the translation tables - Cleanup and optimize string tables - Click on "Clear invalid strings" to delete unused or invalid strings.
These steps should help reduce the number of slow queries generated by WPML String Translation. If this solution does not apply to your situation, 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: The client reported that activating WPML plugins causes the MySQL binlog file to increase drastically in size, leading to very slow website performance and occasional inability to log into WP admin. Solution: We recommend updating the WPML plugins to the latest versions. Specifically, update WPML to version 4.6.12 and Strings Translation to 3.2.13. These updates address issues that might be causing the large binlog file. After updating, clear the debug.log to ensure that only new errors are logged. If you don't see the new versions available, please visit your WP admin's plugin installation page and click on the Check for updates button. You can find the plugin installation page here: Plugin Installation.
Please note that the preg_match() errors mentioned are not related to the issue of the MySQL binlog file.
If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues at 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.
Problem: The client reported significant slow performance with the WPML plugin activated, particularly when the String Translation plugin is enabled. The issue persisted despite switching themes and disabling third-party plugins. Profiling indicated that the slowdown was related to the ACF Multilingual plugin, specifically with the handling of WYSIWYG fields in custom post types (CPTs). Solution: We identified a specific code snippet causing the issue in the ACF Multilingual plugin. We recommended modifying the code in the
This change prevents unnecessary processing unless the field contains a link, which should mitigate the performance issue. We are also working on a more permanent solution to be included in future WPML releases.
If this solution does not resolve your issue, or if it seems outdated, 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.
