Home›Support›English Support›[Resolved] Request for Assistance with Automatic Translation of WooCommerce Products from English to Polish and...
[Resolved] Request for Assistance with Automatic Translation of WooCommerce Products from English to Polish and...
This thread is resolved. Here is a description of the problem and solution.
Problem: The client operates a WooCommerce store where products are automatically added via a plugin from a supplier in English and needs these to be automatically translated into Polish using WPML. The client experienced performance issues and difficulties in managing translations manually. Solution: 1. Visit WooCommerce > WooCommerce Multilingual & Multi-Currency > Status to identify issues such as untranslated product permalink bases and altered configurations. 2. Translate the product permalink base to English at WooCommerce > WooCommerce Multilingual & Multi-Currency > Store URLs. 3. Set all post types and taxonomies that should be translatable to "Translatable only show translated items" at WPML > Settings > Post Type Translation and WPML > Settings > Taxonomy Translation. 4. For missing WooCommerce store pages in English, use the "Create missing translation" option at WooCommerce > WooCommerce Multilingual & Multi-Currency > Status > WooCommerce Store Pages. 5. Regarding the use of 'LoveCherry importer', it may not be compatible with WPML. We recommend using the WPML Export & Import plugin for importing content.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket at 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 operate a WooCommerce store (hidden link) where products are automatically added via a plugin from a supplier. The products, product categories, and attributes are sent in English, and I would like them to be automatically translated into Polish using WPML. This process needs to be automatic, as new products are regularly added to the store.
Symptoms:
In previous configuration attempts, I experienced a significant drop in website performance. Additionally, I had trouble finding a way to mark products and change their language manually, which prevented me from effectively managing translations.
Questions:
How can I optimize the WPML setup to avoid performance degradation?
Is there a script or tool that can help me change the content's language in the database to streamline this process?
How can I ensure the English version of the site is completely hidden from customers and excluded from search engine indexing, while still generating translations?
If you expect translated products, then the only automatic way would be to use automatic translation while using the mode "Translate everything automatically".
Some taxonomies on your site are forced untranslatable. This causes problems when you try to run a multilingual WooCommerce site.
This is probably caused by a plugin or theme.
Here's what you can do:
1. Temporarily disable plugins to see if this message disappears.
2. Temporarily change the theme to see if this message disappears.
We recommend that you contact WPML Support and let them know about the message you see. You can also offer to submit a copy of the Site Duplicator. We will work with the theme/plugin developer to fix this issue. Until then, here's a temporary solution to keep you on track.
I turn off and turn on the plugins, also try to mark up again main taxonomies as Possible to translate, it wont help. I don't know how to add anything to translatation proces, nothing shows up in translation manager.
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.
The provided account does only allow me limited access to wp-admin.
Also, I do not see any registered products. There might be a conflict between plugins and we might need to temporary disable plugins, to figure out which plugins are causing the issue.
Do you have access to a staging site or could you please allow me full access, so that I can create a copy of the site for testing?
If this will not be possible, do the following:
Could you please make a copy or stage of the site and try running the site with minimal setup to see if the issue persists?
1) Disable any additional plugins apart from WooCommerce, WPML and our add-ons.
2) If the issue goes away, start reactivating the plugins one at a time, or activate them in small groups. This way, check where the issue reoccurs to see the plugin that is causing the issue.
3) If this has not clarified the cause of the issue, please switch to a standard theme such as Twenty Twenty-One to see if the issue may be related to the theme.
Once we have identified the cause, we can then try replicating the issue and then escalate it internally. I will provide a test site with WPML in this case.
If you are unable to set up a copy of your website, please let me know and I will be happy to assist you.
- Product permalink base is not translated
- Custom type product configuration from wpml-config.xml file was altered!
- Custom type product_variation configuration from wpml-config.xml file was altered!
- Custom taxonomy product_shipping_class configuration from wpml-config.xml file was altered!
---
Go to WooCommerce > WooCommerce Mulitlingual & Multi-Currency > Store URLs to translate the product permalink base to English.
---
Go to WPML > Settings > Post Type Translation and set all post type that should be translatable to "Translatable only show translated items".
- Products (product)
- Variations (product_variation)
- Posts (post)
- Pages (page)
- Media (attachment)
- My Templates (elementor_library)
---
Go to WPML > Settings > Taxonomy Translation and set all post type that should be translatable to "Translatable only show translated items".
On WooCommerce > WooCommerce Mulitlingual & Multi-Currency > Status > WooCommerce Store Pages > WooCommerce store pages do not exist for these languages:
English
Click "Create missing translation".
I have solved all these issues on hidden link now. Please test the product translation again.
Thank you, the translation seems to work correctly. Thank you very much!
piotrC-23 confirmed that the issue was resolved on 2024-10-28 14:40:35.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.
