Performance

Problem:
The client is experiencing slow saving times in the WordPress dashboard when editing slugs with Yoast SEO, with saving operations taking up to 4 minutes.
Solution:
We recommend trying the workaround provided in the WPML errata for backend slowness and duplicated queries. You can find the details here: WPML Backend Slowness Workaround.
After applying the workaround, please test the saving speed while other plugins are deactivated to ensure that no other plugins are affecting the performance.

If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at WPML 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 slow site performance due to frequent calls to /wp-json/wpml/tm/v1/ate/jobs/retry and /wp-json/wpml/tm/v1/ate/jobs/sync, which trigger multiple admin-ajax.php calls on every admin page load.
Solution:
We recommend the following steps to improve performance:
1. Check the ATE Error logs by navigating to WPML->Support->ATE Error logs and review the top 5 logs.
2. Deactivate the plugin 'User Import Export for WooCommerce Add-on' when it is not in use.
3. In WPML > Settings, adjust the 'display as translated' settings for post types, taxonomies, and custom fields to 'Translatable only show translated items'. For example:
- Pages: Set to 'Translatable only show translated items'
- Downloads Products (product): Set to 'Translatable only show translated items'
4. Disable the WPML Media Translation add-on if you are not using a different image per language.
5. Run WPML troubleshooting actions via WPML->Support->Troubleshooting, specifically:
- Set language information
- Fix Terms Count
- Remove Ghost Entries
- Cleanup and Optimize string tables

These steps helped reduce the dashboard loading time from 2.04s to 1.63s with WPML activated.

If these steps do not resolve your 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. If the problem persists, please open a new support ticket.

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

wp-content/plugins/acfml/classes/Strings/FieldHooks.php

, modify the

add_hooks

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.

add_action( 'rest_api_init', function() {
    if ( wp_is_serving_rest_request() ) {
        add_filter( 'acfml_should_translate_acf_entity', '__return_false' );
    }
}, 5 );

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.