Henning

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.