Problem: The client is manually translating a site that uses Elementor and wants to ensure that their method of translating pages using WPML manual translation and then editing with Elementor does not cause any issues. Solution: We confirmed that the client's approach to manual translation is appropriate. It is important to translate each page independently to prevent the translated pages from syncing with the default language page, which would result in manual translations being overwritten by any updates to the default page. We provided a link to the documentation for translating pages independently: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/#:~:text=Translate%20independently. Additionally, we advised the client to consistently use the same method for translation to avoid any potential issues.
Problem: The client is trying to figure out how to add both staging and live domains in the WPML account when using a staging site to translate the site before pushing it to the live site. Solution: If you're experiencing this issue, we recommend registering your site as a staging site and then changing it to production when you're ready to go live. You can find more information on how to do this in our documentation: What is the difference between production and development sites in WPML?
Alternatively, if you prefer to have separate licenses for your staging and live sites, you can register both sites separately. Multilingual CMS account allows you to register up to three sites. For instructions on how to install and register WPML, please refer to our documentation: How to install WPML
If this solution doesn't look relevant to your situation, please open a new support ticket in our forum: WPML support forum
