This thread is resolved. Here is a description of the problem and solution.
Problem: The client is migrating their website from an old WordPress environment using Elementor Builder to a new one using Oxygen Builder, and they are facing issues with importing content in multiple languages using the WPML import-export plugin. Additionally, they are encountering compatibility issues with the Oxygen Builder when translating pages. Solution: 1. Use the WPML Export & Import plugin for migrating content between environments. Ensure to use the same export and import method for consistency. Follow the detailed guide here: WPML Export & Import documentation. 2. For taxonomy issues during import, refer to: Reconnecting taxonomy translations. 3. If using Oxygen Builder, note that it is not fully compatible with WPML. Translations might need to be done manually using the WordPress Editor. Set Oxygen Templates in WPML settings to "Translatable - or fallback to default language if a translation is not available" to avoid issues. For more details, visit: Using different translation editors and Oxygen compatibility issues. 4. For specific template translation issues with Oxygen, consider the workaround provided by the Oxygen team: Oxygen template translation workaround.
If these solutions do not resolve your issues or if they seem outdated, we recommend opening a new support ticket. We also advise checking related known issues at WPML known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum: WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I’ve done a redesign of our website, taggrs.io, in a new WordPress environment. Everything needs to be moved from the old WordPress environment to the new one. The URLs will all remain the same. I’ve downloaded the WPML import-export plugin. We’re migrating from Elementor Builder to Oxygen Builder.
Symptoms:
I found this video, but it’s already 5 years old. hidden link
Questions:
What is the best practice or the right video we should follow?
What are the next steps after downloading the WPML import-export plugin?
Important is to use the same method for export and import.
WPML will create all necessary entries on the exported files.
You can use the built-in export and import tool from WordPress at Tools > Export and then Tools Import.
Or you can use WP All Export or WP All Import. Only make sure to generate separate export files for taxonomies and posts. Then import taxonomies first, and the posts after.
To assign language information and connect translations:
Go to WPML → Export and Import.
Click the Run WPML Import button and let WPML Export and Import automatically go through the steps.
Check your imported content on the backend and front-end. Ensure they display in the correct language and link to translations.
Our WPML Export & Import plugin is designed to import translations.
In your case you would like to replace the original content, correct?
In this case it depends on the ID of each page. If the pages already exist on the site, then a new import would create new pages with new IDs and they will not be connected with any translations.
What you could try is removing the existing pages before importing the new version, but you would need to make sure that the new pages use the same IDs as old ones.
I honeslty never tested this. If you need any further help, let me know.
You might run into issues translating the templates. I suggest you set the Oxygen Templates at WPML > Settings > Post Type Translation to "Translatable - use default language if translation is not available".
If you do not translate the templates, then they should now be applied automatically to the translated posts and pages.
Take note, that you might run into issues trying to translate the template.
It is not compatible with the WPML Translation Editor, but you can use the WordPress Editor for creating the translations.
In this case, as Oxygen is based on JSON, you would need to copy the JSON data from one page or template to another and make the edit direclty inside the JSON field or directly on Oxygen.
Further down in the section on your screenshot you should find a custom post type field for Oxygen Template.
You could try to translate the templates, but if you do not really need to translate them, you could use the option "Translatable - use default language if translation is not available" and simply not translate them.
The Header and Footer are templates or in this case template parts.
We would need to test, if a translation is possible. If not, I can offer that we try to recreate the issue and escalate it internally, so that our compatibility team can work towards a solution.
I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.
You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.
IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may have to install a plugin called "All In One WP Migration" to make a copy of the website where I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site or copy of the website from your server yourself for this purpose. This step would only be required if the issue is replicable on such a staging site.
If you have any questions about creating such a staging site, you can consult your hosting provider. Just take note that WPML should be registered on this site again.
If you are unable to provide such a copy of the site for testing, please let me know on this ticket.
The private response form looks like this: hidden link
Next time you reply, click "I still need assistance."
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.
