I just checked both links. I see 6 lines in both the sandbox and the live site. I'm not necessarily denying that it is WPML related. The problem is, in order for me to escalate it, I need to be able to CONFIRM that it is WPML related and so far, I am not able to do that. Please see attached screenshots. I included the URL in the screenshot so you can note which site is which, with both showing 6 lines in the 3rd paragraph.
On the sandbox site, it looks the same to me on the backend Elementor edit screen and the fronted - 6 lines in both places. So it appears to be working as expected there. I was never able to see the 5 lines in the staging site. Hopefully Elementor can figure out what's going on there. They are welcome to use the sandbox site for testing if needed.
Sure, I will reach out to Elementor and not expecting a different answer. They will blame WPML again. I doubt they would have a different opinion based on your opinion alone.
Based on your reply to me (seeing different things at different places), I do not know what to think anymore. I bluntly proved you everything you needed to know.
See the sandbox snapshots from the Elementor frontend editor to the live site (outside of Elementor). The result clearly show there is NO issue outside of WPML.
As I have asked of you from the very beginning, in order to determine that this is related specifically to WPML, I need the following screencasts:
1. You editing the page in Elementor using the same content and showing that with WPML active, the text lines show 5 lines of text on the backend and 6 lines of text on the frontend.
2. DEACTIVATE WPML and show that you cannot reproduce the issue using the same content, and showing that in the backend Elementor editor, that there are 5 lines of text on the backend and 5 lines of text on the frontend.
This will indicate that the issue only happens when WPML is active. Since we can't reproduce the issue on the sandbox site, and since I can't reproduce the issue on your staging site (otherwise I'd be happy to test this and grab the screencasts myself), then I will need you to do these screencasts on the live site where the issue is happening. Please keep in mind, even when you deactivate WPML, the pages will still all exist, they will just all be under one language and one domain. You can still edit them using Elementor.
By the way, it doesn't really matter WPML plugins are activated or not. What matters, as suggested by Elementor, is that the page is CREATED by WPML or not. All non-translated pages work just fine, meaning the display the same on the live site compared to within the Elementor editor.
The only discrepancy is that different computers may display things differently. I asked on discussions.apple.com, and sure enough someone with a MacBook Air was able to see what you see, 6 lines on non-translated pages, which is different than on my own MacBook. Most likely because I do not use the default display resolution on mine. Elementor suggested I use a different type of text size value. Not interested! The other types are much worse.
"The content is already there in the sandbox for you to play with. Since I do not understand you, wouldn't simpler for you to test it out yourself??" - I have stated multiple times that I am not able to reproduce the issue on any site - the sandbox site that I created, the staging site that you created, and I don't have access to the live site.
"Unless I can replicate the issue with WPML deactivated, I see no point of bothering Elementor with something I cannot see myself." - This is precisely what I need to see, that you are not able to reproduce the issue with WPML deactivated. I need a screencast of you testing this with WPML active and compared to with WPML deactivated. With WPML deactivated, you will see your translated pages in the full list of pages. They don't disappear simply because WPML is deactivated, so this should be simple to test.
"All non-translated pages work just fine, meaning the display the same on the live site compared to within the Elementor editor." - Since Elementor is saying it's WPML's fault, let's try this. With WPML enabled, you can create a page in any language. So, create a page in your second language instead of translating it. Then, see if the issue reproduced. If not, translate this page from secondary language to default language. Does the issue occur now on the translated page?
Please make sure you have a screencast of this last step. Since I am not able to reproduce the issue, I will need the screencast to send to our compatibility team if indeed it reoccurs in the translated pages only, when translting from second language to default and vice versa.
