Open
Reported for: WP All Import Multilingual 2.3.0
Overview of the issue
Whenever you import content using WP All Import and the WPML All Import add-on, you will see the imported post translations perfectly on the front-end. However, you will encounter issues if you try to update them using WPML’s translation editors:
- The Classic Translation Editor displays content in the default language instead of the imported translations
- The Advanced Translation Editor displays blank translations
This is because when you import multilingual content, WPML does not create translation jobs, which are needed for string segmentation.
Workaround
To edit or update your imported translations, please switch to the native WordPress editor and use manual translation.
The Classic Translation Editor also displays blank translations if we import and edit reusable blocks.
Hello there,
I’m afraid that it happens with both editors as explained in the overview of the issue. As a workaround, please switch to the native WordPress editor and use manual translation in order to edit or update your imported translations,
Is it OK that we import the current contents to our new website under construction before you fix the issue? That means this issue is due to the WPML main plugin set, not due to the import plugin. Otherwise, should I wait the import process until you fix the issue?
Hello there,
This fix may take some time. I recommend you to import your contents and then follow the workaround here provided.
If you have any issue, please start a chat in our support channel. We will be happy to help you there.
Regards
Hi, do you have any schedule to fix this issue? I think it is crucial problem for many WPML users. I updated the WPML Multilingual CMS and WPML String Translation for the latest versions, but the symptom (see https://x.gd/FZFxJ I wrote before for the details) is the same.
Hello there,
I understand the importance of this issue, however fixing this it is not simple and will take some time.
I’ll update this erratum once I have any news.
Thank you for your understanding.
Hi, our development team is considering adding (writing) “patch” codes to the current import plugin (or CSV files to be imported). Could you tell me which fields of which table in the database are managing this translation alignment?
If you tell me your schedule to fix this issue, we can wait until then, but, I suppose you have no schedule to fix this. So, we cannot wait any more.
Hello,
This process is achieved in several tables depending on the content that it’s going to be translated. I think the following documentation will give you a wider idea of the tables structure and how the translation process works:
https://wpml.org/documentation/support/wpml-tables/
I hope it helps
Hello again,
Does your development team have a schedule of fixing this issue in the near future?
If not, we have to develop patch program to copy tables of database from our current website to a new website.
I guess the translation editor get each string in Block Editor from `value`of wn_sn_icl_strings (source lang) and wp_icl_string_translations (target lang). Is it correct? Does `status` value “10” mean the translation is finished?
Does another table wp_icl_translate contains data for custom fields and entire content?
What is another table wp_icl_translation_status used for?
If you have more detailed document of the tables, it would help our development.
Hello there,
There is not a schedule yet for this issue. Regarding your questions, yes, that’s valid for strings and status “10” means that the translation was finished and sent.
If you are planning to release a glue plugin for this, you can consider being part of our Go-Global program where we can bring you a better assistance and help you developing your new plugin.
https://wpml.org/documentation/support/go-global-program/
Is this an issue with importing in general with WPML/WPML Import and Export plugin, or an issue with the WP Import Export plugin specifically? I’m wondering if a different import plugin, rather than WP Import Export, would work?
Hello Ellen,
This issue is reported for WPML All Import plugin. You can try a different alternative as WPML Export and Import.
Hi Andrés,
I have been using WPML Export and Import (along with WP Import Export Lite), and still experienced this. Your support team directed me to this page.
Thank you for your feedback, Ellen. Indeed, this can happen when importing posts and their translations, as we don’t have any translation job for them.
That’s why we don’t have pre-filled fields in the translation editor and manual translation is needed.