Feature request

Problem:
You are trying to ensure that when you edit the status of the original Dutch post on your site, the translated English page automatically reflects the same status (Published, Draft, Private). However, the translated English page does not automatically update to have the same status as the original Dutch post.
Solution:
We recommend using a code snippet to synchronize the status across different language versions of your posts. You should add the following code to the

functions.php

file of your theme:

function sync_publish_status_across_languages($post_id) {
    if (defined('DOING_AUTOSAVE') && DOING_AUTOSAVE) return;
    if ('post' != get_post_type($post_id)) return;
    $post_status = get_post_status($post_id);
    $default_language = apply_filters('wpml_default_language', null);
    $translations = apply_filters('wpml_get_element_translations', null, $post_id, 'post');
    foreach ($translations as $lang => $translation) {
        if ($lang === $default_language) continue;
        $translation_post_id = $translation->element_id;
        wp_update_post(array(
            'ID' => $translation_post_id,
            'post_status' => $post_status
        ));
    }
}
add_action('save_post', 'sync_publish_status_across_languages');

Please note, this solution applies only to pages and posts. Ensure you have a full website backup before implementing this code.

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your 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 needed, please open a new support ticket at WPML support forum for further assistance.

Problem:
The client is experiencing excessive database load due to incorrect removal of the WPML_Term_Display_As_Translated_Adjust_Count filter in the function

add_get_term_adjust_count()

. The filter

get_term_adjust_count()

is not being removed correctly, leading to millions of calls per hour.
Solution:
We have escalated the issue to our second-tier support for a detailed examination. Our specialists have identified the problem and are currently working on a solution. We do not have an estimated time of arrival for the fix yet. We recommend monitoring the changelog for upcoming WPML versions to see when the issue is resolved.

Please note that this solution might be outdated or not applicable to your specific case. If this solution does not resolve your issue, 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 do not hesitate to open a new support ticket at WPML support forum for further assistance.

Problem:
The client's SEO team noticed that the hreflang tag and the canonical URL have the same structure, which was not expected.
Solution:
We have resolved this issue in a later version of WPML. We recommend updating to the latest version of WPML to ensure this issue is addressed.

If this solution does not apply because it might be outdated or not relevant 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 you still experience issues, please open a new support ticket at WPML support forum.

Problem:
You are trying to save data on an ACF option page in various languages using ACFML, with fields set as 'copy' to maintain the same values across all languages. While the backend shows values correctly copied and locked, the frontend still displays values from the main language (Italian). Even after updating the value in the main language, you need to manually update it in each secondary language to reflect changes on the frontend.
Solution:
The behavior you're experiencing is expected when using ACF fields with the copy translation preference. To apply these values to the secondary languages on the frontend, you must re-save the options page in those languages. This process is necessary to ensure consistency across languages as currently implemented by WPML and ACFML. For more details, you can refer to our documentation here: Translating the ACF Options Page Custom Fields with WPML.
If this manual update process is cumbersome, we can submit a feature request to explore the possibility of automatically copying the options page values into the secondary languages upon saving the default language options page. Please let us know if you would like us to proceed with this request.

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 issue persists, please open a new support ticket at WPML support forum.