Problem: The client is experiencing a decrease in page speed after installing WPML on their website. Solution: We recommend the following steps to improve your site's performance: 1. Disable "Adjust IDs for multilingual functionality" under WPML -> Languages -> Make themes work multilingual, especially if you are using well-known themes like Astra. 2. Reduce the overall page size by compressing media files using plugins like EWWW. 3. Install and configure a page caching plugin such as Super Cache, W3 Total Cache, or WP-Rocket. 4. Implement object caching with Redis to enhance backend performance. This requires support from your hosting or VPS and can be set up using the Redis Cache plugin. Note that some caching plugins like W3 Total Cache also provide object caching. 5. Ensure that the Query Monitor plugin is only active during testing phases to identify slow queries and not enabled in production as it can degrade performance.
If these steps do not resolve the issue or if the solution 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 open a new support ticket.
Problem: The client is experiencing 'Deadlock found when trying to get lock; try restarting transaction' errors in their PHP error log, followed by fatal errors. They have already truncated the icl_background_task table as a preliminary step. Solution: We recommend performing a full site backup before proceeding with any further steps. After ensuring the backup is secure, please follow the workaround provided in our errata page to address backend slowness and duplicated queries which might be related to your issue. You can find the detailed instructions here: WPML causing backend slowness and duplicated queries.
If this solution does not resolve your issue or seems irrelevant due to being 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You have unwanted translated contents in your database that you wish to delete. Solution: If you're experiencing this issue, we recommend you follow these steps to remove the unwanted translations: 1. Take a full backup of your site and database. 2. Navigate to WPML > Support > Troubleshooting. 3. Click on the following buttons: - Clear the cache in WPML - Remove ghost entries from the translation tables - Set language information - Cleanup and optimize String tables After completing these steps, please check if the unwanted entries are still present in the database. If they persist, provide more details about the table and a screenshot of the entries you wish to remove for further assistance.
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.
Problem: After upgrading from WPML 4.6.3 to 4.6.11, a significant performance regression was observed, specifically with the 'WPML Multilingual CMS' and 'WPML String Translation' plugins. This issue was evident in REST API calls, where the time to execute 7 queries increased from approximately 10 seconds to 55 seconds. Solution: We recommend implementing a workaround by modifying the logic in the plugin files to exclude REST requests. Specifically, in the file
method to check for REST requests before executing hooks. Here is the suggested change:
public function add_hooks() {
if (!strpos($_SERVER['REQUEST_URI'], 'wp-json')) {
add_action('acf/update_field_group', [$this, 'registerGroupAndFieldsAndLayouts']);
add_filter('acf/load_field_group', Fns::withoutRecursion(Fns::identity(), [$this, 'translateGroup']));
add_filter('acf/load_field', [$this, 'translateField']);
add_action('acf/delete_field_group', [$this, 'deleteFieldGroupPackage']);
}
}
Important: Please ensure to make a full site backup (files and database) before implementing this workaround.
Update!
We are soon to release a new version of ACF Multilingual, version 2.1.4. The update will overwrite the fix suggested in this ticket. (In the file: wp-content/plugins/acfml/classes/Strings/FieldHooks.php). Our developer suggests a better workaround that will work with version 2.1.4. Add the following function.
It is important to note that the above snippet will only work with ACF Multilingual version 2.1.4
It's recommended that the snippet be added as a Must-Use plugin. Alternatively, you can add the function to the functions.php file of your theme.
**** Important! Please make a full site backup (files and DB) before you proceed with those steps****
Note: wp_is_serving_rest_request introduced in WP 6.5 relies on the REST_REQUEST global. But keep in mind that standard HTTP requests could also call REST endpoints internally (to pre-load REST request results with the normal request). The client might want to disable the ACF entity translation on a wider scope.
If this solution does not resolve 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
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.
