Symptoms:
The content either imports as a Draft and remains as a Draft (ignoring the _wpml_import_after_process_post_status field set up in my import template) or it imports as Published and will display the secondary language content in the wrong places on the front end until I run the WPML Export and Import. Additionally, the Region taxonomy is not being set correctly after running WPML Export and Import - the result is the default language version of the Region is applied incorrectly, breaking the translated taxonomy archive from correctly showing the content on the front end.
Questions:
How can I ensure that content imported as a Draft is published correctly after using WPML Export and Import?
Why is the Region taxonomy not being set correctly after running WPML Export and Import?
My test import to the sandbox site created has been done via WP All Import, but WPML Export and Import is not installed. When I try to install myself, I get an error. Right now, my import has happened, but the translation piece has not yet been run.
Checking in here. I'm unable to complete the test, because the WPML Export and Import plugin is not installed and active on the sandbox site that was set up. Could you please add that so I can complete the test?
Thank you! I performed 2 tests on the sandbox site, with the following results.
Test 1:
Imported as a Draft with WP Alli Import and configured the _wpml_import_after_process_post_status column to declare that WPML Export and Import should publish the posts after processing. The result was the posts remained in Draft status, but the category did align successfully.
Test 2:
Imported as Published with WP All Import and created a second category that has the same name as it's English counterpart. Strangely, the posts were imported directly to the correct language without running WPML Export and Import, and the category was again aligned successfully.
I am going to try another test in my staging environment. The one thing this sandbox is missing is a custom taxonomy, which is a part of our intended use case. I'll update here once I've run more tests in our environment.
