Feature request

Problem:
The client requested two enhancements for the WPML plugin to optimize translation time. First, an automatic fill-in feature in the media gallery of the post being translated, similar to a find and replace function, to rename multiple media titles at once. Second, a feature to mark all text boxes as 'completed' in manual translation mode before publishing, to facilitate bulk actions.
Solution:
We have acknowledged the client's suggestions and have forwarded them to our development team for consideration in future updates.

Please note that the solution provided might be irrelevant if it is 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 the issue persists, please open a new support ticket at WPML support forum.

Problem:
The client needs to automatically create a duplicate of each Spanish (Spain) page/post for Spanish (Mexico) on their multilingual site, but only for certain pages.
Solution:
We recommend using the WPML hook for duplicating posts automatically. First, ensure you back up your site and database. You can implement the following code in your theme's functions.php file or a custom plugin:

add_action( 'wp_insert_post', 'my_duplicate_on_publish' );
function my_duplicate_on_publish( $post_id ) {
    global $post;
    if (is_null($post) || (defined( 'DOING_AUTOSAVE' ) && DOING_AUTOSAVE) || (isset( $post->post_type ) && $post->post_type == 'revision')) {
        return $post_id;
    }
    remove_action( 'wp_insert_post', 'my_duplicate_on_publish' );
    $is_translated_in_es_mx = apply_filters( 'wpml_element_has_translation', '', $post_id, 'es-mx' );
    if ( !$is_translated_in_es_mx ) {
        do_action( 'wpml_admin_make_post_duplicates', $post_id );
        do_action( 'wpml_set_element_language_details', [
            'element_id' => $post_id,
            'element_type' => 'post_' . $post->post_type,
            'trid' => wpml_get_content_trid( 'post_' . $post->post_type, $post_id ),            
            'language_code' => 'es-mx',            
            'source_language_code' => 'es'
        ] );
    }
    add_action( 'wp_insert_post', 'my_duplicate_on_publish' );
    return $post_id;
}

This script checks if a post is a new or updated Spanish post and duplicates it for Spanish (Mexico) if no translation exists. Modify the condition inside the function if you want to limit this behavior to specific post types.
For more details on the hook used, visit WPML admin make post duplicates.

If this solution does not apply to your case, or if it seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we encourage you to open a new support ticket.

Problem:
You are using WP-CLI to list all media IDs in the trash across all languages but the command only returns media IDs for the main language.
Solution:
We have identified two potential workarounds to include media IDs from all languages:
1) Use the WP-CLI parameter

--suppress_filters=true

which allows the command to work across all languages.
2) Use the parameter

--url="https://yourwebsite.com/en"

to force WP-CLI to work in the language based on the URL.

Additionally, our 2nd Tier Support suggests modifying the code in

wp-content/plugins/sitepress-multilingual-cms/classes/query-filtering/wpml-query-filter.class.php

. Replace the existing

posts_where_filter

function with the following code to include a condition that checks for the 'lang' parameter in the query:

public function posts_where_filter( $where, $query ) {
	if ( $query === null || $this->where_filter_active( $query ) === false ) {
		return $where;
	}

	$requested_id = isset( $_REQUEST['attachment_id'] ) && $_REQUEST['attachment_id'] ? $_REQUEST['attachment_id'] : false;
	$requested_id = isset( $_REQUEST['post_id'] ) && $_REQUEST['post_id'] ? $_REQUEST['post_id'] : $requested_id;
	$requested_id = (int) $requested_id;

	$default_language = $this->sitepress->get_default_language();

	$post_language = $this->post_translations->get_element_lang_code( $requested_id );
	if (isset($query->query["lang"])) {
		$post_language = $query->query["lang"];
		$requested_id = "1"; //hack needed because then $current_language will not get the $post_language, but will call for get_current_language
	}

	$current_language = $requested_id && $post_language ? $post_language : $this->sitepress->get_current_language();

	$condition = $current_language === 'all' ? $this->all_langs_where() : $this->specific_lang_where( $current_language, $default_language );
	$where     .= $condition;

	return $where;
}

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 these solutions do not resolve your issue, please open a new support ticket at WPML support forum.

Problema:
Stai utilizzando l'API REST di WooCommerce per tradurre le categorie di prodotti sul tuo sito. Quando tenti di tradurre una sottocategoria, la traduzione funziona, ma non è collegata alla categoria principale tradotta. Ti chiedi se 'translation_of' sia il parametro corretto da usare nella chiamata API per collegare la traduzione alla categoria principale.
Soluzione:
Al momento non esiste un modo per sincronizzare le gerarchie delle categorie tradotte programmaticamente tramite l'API. Tuttavia, puoi esplorare la classe

\plugins\sitepress-multilingual-cms\classes\troubleshoot\class-wpml-troubleshoot-sync-posts-taxonomies.php

e scrivere del codice personalizzato per gestire questa sincronizzazione. Se necessiti di assistenza nello sviluppo, ti consigliamo di consultare uno dei nostri contractor.
Se questa soluzione non risulta pertinente, potrebbe essere perché è obsoleta o non applicabile al tuo caso. Ti consigliamo di verificare i problemi noti, controllare la versione della correzione permanente e confermare di avere installato le ultime versioni dei temi e dei plugin. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.