[Waiting for user feedback] Preview of page is heavily outdated because of 'parse_query' hook

Hi,

thanks for your response. I tried to reproduce the issue on your site. Sadly I was not able to. One main difference I see is that on our site we are using the WP Bakery Plugin in combination with WPML. I was not able to install that plugin on your site though.

I actually provided detailed steps on reproducing the issue in this support request initially but the AI summary feature of this forum stripped all that away...

I will try to give a more detailed view here again:

The issue happens when editing a translated page and clicking the "Preview Changes" in the classic (non-gutenberg) editor. Debugging it shows that there is an autosaved revision created correctly when editing the page. Performing the query to fetch the latest revision on the database gives the correct content.

However the preview page calls the 'parse_query' hook of the WPML plugin. This hook somehow determines that the preview should show an outdated version of the page and attaches the id of that revision into the query parameters. That leads to the lookup of the latest version be useless as it already includes the hardcoded id of the revision.

The SQL Query without the WPML plugin looks lilke this:

SELECT
	sg9014_posts.ID
FROM
	sg9014_posts
WHERE
	1 = 1
	AND sg9014_posts.post_parent = 2745
	AND sg9014_posts.post_type = 'revision'
	AND ((sg9014_posts.post_status = 'inherit'))
ORDER BY
	sg9014_posts.post_date DESC

The SQL Query WITH the WPML plugin (and therefore parse_query hook) looks like this:

SELECT
	sg9014_posts.ID
FROM
	sg9014_posts
WHERE
	1 = 1
	AND sg9014_posts.ID = 4469
	AND sg9014_posts.post_parent = 2745
	AND sg9014_posts.post_type = 'revision'
	AND ((sg9014_posts.post_status = 'inherit'))
ORDER BY
	sg9014_posts.post_date DESC

Notice that in the second query the posts.ID is already set. I am assuming this information is coming from some internal cache that WPML is using to determine the revision. Do you have some more information on whats the mechanism there so I can further debug? Maybe you can tell me how I can reset the internal cache if there is something like that?

Thanks!