Background of the issue:
We are using Elementor with WPML and we have a problem with updating Elementor CSS after the parent page in the default language is updated in Elementor. Elementor post-{post_id}.css files are not generated for translations after the update. But when we click in Elementor > Tools > Regenerate CSS it fixes styles for translated pages.
Symptoms:
Elementor CSS files for translations are not generated after updating the parent page in the default language.
Questions:
Can you help us with this issue, please?
I was able to solve the issue in the copy of your website, after making some tests. Please make sure to have a full website backup, and follow these steps:
1. Go to WPML > Settings > Custom Fields Translation and change _elementor_css to "Copy";
2. Change the design, as you wish;
3. Make sure to make a small change on the content, like adding a blank space to a text;
4. Save your changes;
5. Update the translation by saving it;
By doing that, the changes were reflected on the translation, on the Front End. It's likely that, when only changing design elements, like margins or paddings, that the update of the translation does not get triggered. Please let me know if it works for you.
thanks for reply, but it does not help to solve problem. We found the problem is not only with css generation but also with new blocks added to default page via elementor.
Steps to reproduce:
Go to page “Kontakt”
Add new elementor widget
Translate it via ATE
Go to translated page “Contact”
Block is not visible at all.
When we click on regenerate css and assets in Elementor > Tools, it fixes css generated files also as translations on the translated page.
We have uploaded the staging site to hidden link.
Please enable me to paste creadentials in private message.
Lucas is not available today so allow me to jump in so you don't have to wait. I 've activated the private field for your next answer where you can provide that information safely (this field is only visible by you and the support team). Don't share your own admin account, create a new one that you will delete when we finish troubleshooting.
IMPORTANT: Before we proceed, please backup your site and database.
From what I understand, it appears that some Elementor "cache" mechanism is preventing you from seeing the updated content on the frontend until you click on "Regenerate Files & Data". Is that correct?
I'll follow your instructions to test in on the Kontakt page.
Thanks providing access however, I followed your instructions and wasn't able to reproduce the issue.
- I added an Elementor widget on the Kontakt page and saved
- I was able to translate that new text in ATE
- I was able to see these changes on the frontend in both languages
Here is a short video of my intervention: hidden link
If I missed something, could you please create another video with Loom.com so I can see the exact steps to reproduce?
Thank you for the walkthrough video. Minute 1:38 I see that, when you save the translation and are redirected to the original language, in the URL you have "referrer=ate&complete_no_changes=0".
It seems that your changes are not applied to the translation. Please give me few minutes to investigation this issue.
I couldn't reproduce the issue on my end:
- No ATE errors have been recorded in the last 2 days.
- I deleted the English translation of that page and created a new one, in case the translation file was corrupted.
Video: hidden link
Please update your profile by adding your first and last name.
If the issue persists, try connecting with my account to determine if the problem is specific to your account.
I try to update username - does not help. Then I try to use your account and it also does not help. But i found that also plugin activation/deactivation somehow purge the "cache" of elementor page. But no cache plugin in in use.
I'm sorry but I can't reproduce the issue so it's hard to help you out. I've created a new video to show you that I have no issues updating and translating a page: hidden link
If it's not related to your account it could be related to your browser or an expired cookie. Could you please try from another browser? Or can you describe step by step how to reproduce the issue?
Hi, we are still working on finding the specific cause of the problem. Right now, we know there might be an issue with our theme as the 2024 theme does not cause the issue.
I am writing regarding the automated mail "Support topic to be closed soon", and I want to make sure that the ticket does not get closed sooner than the 14 days you mentioned in your previous message.
