Feature request

Problem:
The client needed to customize the default translation batch name in WPML Translation Management, which is hardcoded as 'WPML|{lang}|{number}'. They requested a filter to change the prefix 'WPML' to a custom string like 'Help Center'.
Solution:
We reviewed the request and decided not to add a new filter for customizing the default translation batch name. This decision was based on the specificity of the request and the fact that it's the first of its kind in over 10 years of WPML development. Additionally, since the batch name can be manually edited before sending for translation and it does not impact the translation workflow, we concluded that the demand for this feature does not justify a new implementation at this time. However, you are welcome to implement a custom solution if necessary.

If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related 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 open a new support ticket.

Problem:
The client is using the 'Update internal links' feature in WPML to correct links in translated posts that incorrectly point to the original English page. Despite translating content into three languages and having a large number of posts (33,600), the process often stops or breaks around 19,600 posts, displaying an error message. The client seeks a solution to make this process run in the background without needing the admin page to remain open.
Solution:
We discussed three potential solutions:
1. Address the immediate issue by ensuring the 'Update internal links' process does not stop or break.
2. Tackle the underlying problem by ensuring that posts do not point to the original English page when translated alternatives exist.
3. Consider the feature request to run the process as a background task, although this might not be implemented soon.
We recommend focusing on the second solution, which addresses the root cause of the issue. It is expected that internal links in other languages should automatically translate along with the content, making the 'Update internal links' button unnecessary in this scenario. If the client still prefers to pursue the feature request, we can proceed with that, but we suggest reconsidering for a more immediate resolution.

If this solution does not resolve your issue or 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 the problem persists, we highly recommend opening a new support ticket at WPML support forum.

Problem:
If you're experiencing outdated page previews in WordPress while using WPML, it might be due to WPML's parse_query flow setting a fixed single-post ID ('p') on the WP_Query. This issue occurs because during the preview, WordPress queries the latest autosave revision, but the 'p' set by WPML persists, preventing the latest revision from being fetched.

Solution:
We recommend implementing a minimal, safe fix by modifying the WPML_Query_Parser::parse_query method. Here's a step-by-step guide:
1. Open the file located at

classes/query-filtering/class-wpml-query-parser.php

.
2. Locate the section where the post_type is computed.
3. Add a guard early in the method to clear any leftover single-ID constraints for revision queries. Here's the code you should add:

if ( ! empty( $q->query_vars['post_type'] ) ) {<br />  $post_type = $q->query_vars['post_type'];<br />}<br />$pt_is_revision = ( is_array( $post_type ) && in_array( 'revision', $post_type, true ) ) || $post_type === 'revision';<br />if ( $pt_is_revision ) {<br />  unset( $q->query_vars['p'], $q->query_vars['page_id'], $q->query_vars['name'], $q->query_vars['pagename'] );<br />}

This change ensures that preview requests correctly fetch the most recent autosave revision without being pinned to an old revision ID. Normal WPML routing and translated front-end behavior remain unchanged.

Please note that this solution might be irrelevant if it's 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.