Background of the issue:
I am trying to preview content changes made to this page in the editor: hidden link. I expected to see a preview that reflects the changes made to the page before publishing.
Symptoms:
An outdated preview that does not show any of the new changes made. This issue only occurs when the WPML Multilingual CMS plugin is active. When the plugin is deactivated, the preview functionality works correctly. A screen recording demonstrating the issue is available at: hidden link
Questions:
Why does the preview functionality break when the WPML Multilingual CMS plugin is active?
How can I fix the preview issue while keeping the WPML Multilingual CMS plugin active?
I’ve already provided access to the staging site, where you can fully inspect the current setup and perform any debugging as needed. Since it’s a working copy of the site that accurately reflects the current state, it should be sufficient for your investigation.
That said, if you still require a Duplicator package for internal debugging purposes, I’m happy to provide one—excluding media files to keep it minimal, as requested.
Please confirm whether the staging site is sufficient, or if you would prefer the Duplicator package instead.
We’ve already provided access to our staging site, where the issue can be fully reproduced and debugged. This environment mirrors the live setup and should be sufficient for investigation.
Please confirm whether the staging access is enough, or if you would prefer the package instead.
Kindly check this as soon as possible — this is very important, as the issue is currently affecting our live site.
I apologize for the delay in responding. I will take care of this ticket; the reply time will be shorter now.
The staging environment should be fine, I'll make a copy if I need to debug locally.
I visited the page and edited it in the backend, and the preview mode worked. Did you mean the Visual Builder? When I tried to enable it, I got a blank page. But, I deactivated WPML and the error persisted. Can you please clarify?
On the other hand, can you please update WPML and its add-ons to their latest version?
We’ve now updated WPML and all related add-ons to their latest versions. However, the issue is still occurring.
Please check the following page for testing: hidden link
To reproduce the issue, please follow the exact steps shown in this video: hidden link
This should help you detect the issue clearly.
If you need any additional information or access, please let us know.
We would appreciate your help in resolving this issue as soon as possible, as it is affecting our live workflow.
We followed the same steps on our end as you did in your local environment, but unfortunately, we’re still experiencing the issue.
Please refer to the video below for your reference: hidden link
Additionally, we have confirmed that there is no server-side caching enabled on the staging site, so caching does not appear to be the cause.
Kindly review this again and let us know if you have any further questions or require additional information.
From the chat interaction I can see that:
1. The issue is not Divi-specific, it happens with only WPML active and default theme
2. The issue is not replicable on a fresh test site
Can you please confirm?
Adding to that, the issue does not happen on a copy of your site on another server.
Everything points to a server issue.
Not sure what else to check there, can you please check with your hosting support for advice?
We’ve already provided multiple videos (including from our staging and local environments) clearly demonstrating the issue. In our previous comment, we specifically mentioned that we tested the setup locally, and the issue still persists — even without any server-related variables. So, this is not an environment-related issue.
Please see the latest video again, where we run the site locally and still face the exact same issue: hidden link
When the WPML Multilingual CMS plugin is deactivated, the preview works perfectly — when it's active, it breaks. This strongly suggests the issue lies within the plugin itself.
We’ve also confirmed with our hosting team that there is no server-side caching enabled, so that is not the cause.
At this point, we ask that you please thoroughly check our staging site (which we’ve already shared) and proceed with actual debugging on your end. We’ve done all we can from our side.
We need a solution as soon as possible, as this is impacting live workflows.
We’ve updated the opcache.revalidate_freq value to 2 as recommended.
However, the issue is still occurring across all environments.
Please refer to the video below for your reference: hidden link
To summarize:
opcache.revalidate_freq is now set to 2 on our staging, local, and live environments.
The issue still persists in all three cases.
Given this, we believe the problem is not related to OPcache settings.
Please review the video and confirm from your end what else could be causing this.
