Preview not working with WPML 4.6.7

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Our wait time is higher than usual, please make sure you are meeting the minimum requirement - https://wpml.org/home/minimum-requirements before you report issues, and if you can take a look at current Known Issues - https://wpml.org/known-issues/. Thank you.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	8:00 – 10:00	8:00 – 10:00	8:00 – 13:00	8:00 – 13:00	9:00 – 13:00	-
-	11:00 – 17:00	11:00 – 17:00	14:00 – 17:00	13:00 – 17:00	13:00 – 18:00	-

Supporter timezone: America/New_York (GMT-04:00)

Tagged: Bug

This topic contains 3 replies, has 2 voices.

Last updated by Lauren 1 year, 5 months ago.

Assisted by: Lauren.

Author	Posts
October 20, 2023 at 5:34 pm #14626363
usahello	We are seeing another potential issue with WPML, as of the update to 4.6.7 the preview functionality no longer works. If we make an edit to a post and click the "Preview in new tab" button, the edits are not visible in the previewed page. Can you confirm on your end? This is tested on our live site, staging site, and a clean WordPress install with only WPML active.
October 24, 2023 at 2:13 pm #14648635
Lauren Supporter Languages: English (English ) Timezone: America/New_York (GMT-04:00)	This issue has been escalated to our developers and will be fixed in a future release. In the meantime, as a workaround, you can comment out this line in wp-content/plugins/sitepress-multilingual-cms/classes/ATE/Review/ReviewTranslation.php: remove_filter( 'the_preview', '_set_preview' ); I'll update here once we have the confirmation that it has been fixed in a release.
October 24, 2023 at 4:54 pm #14649915
usahello	Thank you for the update. The temporary fix works. I'll be on the lookout for the future release.
October 24, 2023 at 6:48 pm #14650441
Lauren Supporter Languages: English (English ) Timezone: America/New_York (GMT-04:00)	Thanks for confirming that the workaround resolves it. I'll update here when we have an official release.