We discussed this issue with Elementor support in detail and the last conclusion was that this issue is “a global WordPress indexing issue rather than an Elementor-specific bug, as the post is also unretrievable via the default WP-Admin search for Posts and Pages; Elementor is simply reflecting this underlying core search failure.”
Here's the description of the original problem in a google doc. hidden link
Here are two screen recordings showing the exact issue: hidden link hidden link
At this point it seems like there’s a problem somewhere between WP and WPML in terms of returning the correct results in search and the issue seems to be related to translations specifically. And, importantly, the problem is not 100% reliable, as the doc above indicates. Sometimes this problem can be fixed by relentlessly retrying and if you’re lucky, the right translated post will show up. But, this is, as far as I can tell, almost luck, as nothing from our side seems to directly affect the outcome. Not cache clearing, not permalinks resaving, nothing. It seems random (though I know it probably isn’t - just seems like it to us).
Hopefully you can help? In the next message I can provide access info.
Thank you for the detailed report and for sharing the recordings this is very helpful.
I’ve checked this further on my side and I can see that we’ve had similar reports in the past, which should already be fixed in recent WPML versions. I also tested this on a sandbox site, but I was not able to reproduce the issue there.
I noticed that you are currently using an older version of WPML plugins. Could you please update WPML to the latest version 4.9.2? You can do this by going to Plugins → Add New → Commercial → Check for updates. Before proceeding, please make sure to create a full backup of your site. After updating, please check if the issue still occurs.
If the problem persists, it would be very helpful if you could try to reproduce it on a test/sandbox site and share the exact steps. This would allow us to escalate it more efficiently, as it’s possible I may be missing a specific condition required to trigger the issue.
- hidden link
But based on previous reports, I believe this should be resolved after updating.
