Split: Secondly, I went ahead and translated everything automatically.

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client reported that after using automatic translation, some content on the product pages, such as custom fields and images, was not translated, and some strings were not available for translation.
Solution:
1. We advised the client to make custom fields translatable by following the guide at https://wpml.org/documentation/getting-started-guide/translating-custom-fields/.
2. We suggested enabling the "Show 'Multilingual Content Setup' meta box on post edit screen" option in WPML → Settings → Custom Fields Translation to manage custom fields settings directly when editing products.
3. We reminded the client to back up their database before making any changes.
4. We informed the client that media (attachments) set to be untranslatable in WPML → Settings → Post Types Translation would not appear in translations. To fix this, the client should adjust the setting, slightly modify the original product, save it, and then save the translation in the WPML translation editor.

If the provided solution does not apply to your case, or if it's outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please contact us in the WPML support forum at https://wpml.org/forums/forum/english-support/.

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.

This topic is split from https://wpml.org/forums/topic/im-trying-to-translate-pages-from-english-to-slovenian/

Tagged: Documentation request, Exception

This topic contains 6 replies, has 2 voices.

Last updated by Andrey 1 year, 5 months ago.

Assisted by: Andrey.

Author	Posts
March 19, 2024 at 7:13 pm #15428544
andrejR-7	Secondly, I went ahead and translated everything automatically. I spent 45k credits and there but on the front end there is barely anything translated. Even in the menu there are some words translated, some not. On product pages, only a few words are translated. The images are gone. The tables with information are gone. It's a mess. If I try to manually translate the page, most of strings are not even there for translation. Here's an example of "translated" product page: hidden link
March 19, 2024 at 7:43 pm #15428633
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	I understand you may think that you have lost or overused those credits for the text that wasn't translated but don't worry; you haven't lost the translated text, and the amount of the credits was used only for translating available text. The untranslated text may not have been picked up by WPML, so you may need to find and add it to the translation to enable WPML to translate it. For instance, let's consider the page you mentioned earlier: hidden link. Upon checking the original product in Italian, I noticed that you are not using standard WooCommerce fields to fill the product with text, but custom fields instead. To make the custom fields translatable and the image copied, you need to adjust the settings accordingly. Once you do that and manually translate the page, the text from the custom fields will appear for translation, and the image will be copied after the translation is complete. You can even use automatic translation for this product if you want. To make your custom fields translatable, please follow this guide: https://wpml.org/documentation/getting-started-guide/translating-custom-fields/. You can also enable the option "Show 'Multilingual Content Setup' meta box on post edit screen" in WPML → Settings → Custom Fields Translation to display the custom fields settings at the bottom of the page when you edit products that belong to the product. Please remember to backup your database before making any changes.
March 19, 2024 at 9:29 pm #15428925
andrejR-7	Thank you for all your answers, I appreciate it. I've enabled all custom fields under the product, a lot more is translated now, but some fields are still missing and the images have not appeared yet. Should I translate "system fields" too?
March 20, 2024 at 2:47 pm #15432330
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	I am glad to hear that more text was found for translation. Could you point me to the text that does not appear? Usually, the system fields don't contain data to translate. Your Media (attachment) is set to be untranslatable in WPML → Settings → Post Types Translation, so attached images are expected to not appear in the translations. Once you adjust the setting, you should slightly modify the original product, save it, and navigate to the WPML translation editor to save the translation, too.
March 20, 2024 at 3:18 pm #15432545
andrejR-7	The media now shows after I followed your instructions! I'm attaching photos of a sample product where some things are translated and some not. I've marked the non-translated words. The page is: hidden link
March 20, 2024 at 3:19 pm #15432547
andrejR-7	Forgot the attachments:) New threads created by Andrey and linked to this one are listed below: https://wpml.org/forums/topic/split-translating-menu/ https://wpml.org/forums/topic/split-translate-the-theme-strings/
March 21, 2024 at 4:52 pm #15437656
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you! If it's okay with you, I would like to split the last issues into two separate tickets. This will help other users in the support forum who may be looking for similar solutions. The first ticket will address the strings at the top of the page, which is your menu. I will reply to that ticket with this URL: https://wpml.org/forums/topic/split-translating-menu/. The second ticket will address the remaining strings on the page, which may be related to your current theme. I will reply to that ticket with this URL: https://wpml.org/forums/topic/split-translate-the-theme-strings/.