[Resolved] A problem when importing with WP All Import and Estatik
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing an issue where importing translations for properties using WP All Import in conjunction with the Estatik plugin results in the translations overwriting the original English content instead of updating it.
Solution: We recommend the following steps to resolve the issue:
1. Make sure in the last step in the section that "Records in this import file will be matched with properties on your site based on"... TITLE
This is a better option since your titles are unique either way, and if you use a custom field value it may be the same in EN / HR language and may match it and skip import.
- For each record in this import file, every time this import is run... Create new property from records newly present in this import file
This is needed to create new posts in 2nd language that exist in your files but not on the website, otherways they will be skipped, and only update changes will be made to already existing matching posts.
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.
We have a problem while importing properties into Estatik Plugin with WP ALL IMPORT.
So the idea is to import properties with their english translations (ID 2). These have been imported at some point, however, we have secondary XML with translations (ID 3). These should update / translate properties imported via ID 2.
However, what's happening is, ID 3 is overwritting english translations generated by ID 2. We did set WP ALL IMPORT to different language. Any ideas what I might be missing?
Plugin is Estatik. We have valid licences for:
-Estatik
-Wp ALL import
-WPML
I created a minimal installation of WordPress, WPML, and all necessary WPML add-ons.
You can access the WordPress dashboard using the link below:
- hidden link
Kindly follow the steps below:
- Install wp All import and Estatik
- Setup simple import with 2-3 items
- Try to replicate the issue.
- Share with me step by step guide on how can I check the issue
This will help us to report the probable issue to the compatibility team and solve the possible problem faster.
Ok, I've setup what you asked for. Though, it seems that there are issues with Estatik and WpAllImport, probably something to do with unlicensed version. It's not importing custom fields on your demo site while it does in our enviroment.
Import #1 is main english version, while #2 is secondary language which isn't getting imported properly.
I would also point out, that on your demo version there's another difference. Settings ask for following:
"Records in your file will be matched with Propertys on your site based on..."
Since in our enviroment, property ID code is being imported we have it set there to "Custom field". In your enviroment I have tried other three available options, currently set to POST ID.
since WP All Import Pro is installed now we have very similar enviroment to our own. So here are the steps to reproduce the issue:
1. go to All Import - Manage Imports
2. Click "Run Import" for import #1 - one for English version
3. Proceed to update / import properties. XML should already be uploaded to server, so there's no file you need to add.
Once above is complete do the same with Import #2 - secondary language.
Afterwards go to Estatik - My Listings. You will probably have to switch to English language in top bar (which is the issue as well) as no properties will show.
Once you switch to English version, you should see three imported properties along with their English titles. Edit any of these, and you'll see that secondary language translation is missing.
The issue could be with:
-Estatik
-WPML
-Wp All Import - maybe #2 not setup correctly which I doubt.
We opened ticket with Wp All Import, but they said to talk to you.
thanks for getting back and taking the time to reproduce.
I have checked and could see a few issues in the import template, so I have made the next changes in the HR template's last step:
- Records in this import file will be matched with properties on your site based on... TITLE
I think this is a better option since your titles are unique either way, and if you use a custom field value it may be the same in EN / HR language and may match it and skip import.
- For each record in this import file, every time this import is run... Create new property from records newly present in this import file
This is needed to create new posts in HR that exist in your files but not on the website, otherways they will be skipped, and only update changes will be made to already existing matching posts.
I have run import and it seems to import and connect translation fine, please check.
