I am trying to translate all the products in my site (about 16000). In another ticket that I opened https://wpml.org/forums/topic/the-automatic-translation-has-been-stuck-for-a-long-time/
I talk about the impossibility for me to enable the automatic translation because it breaks the site. So at the moment I select some products manually and click translate with credits. Now it happens that sometimes the site admin page is inaccessible like in this video below hidden link
I'm sure that is wpml because if I deactivate it I have no issue.
It happens also that if I can access to the site admin page and I need to translate something, the translations load without any result forever. I need to go in translation managment, tools and select all in progress translation and delete it, look the video below: hidden link
Generally I didn't select more than 10 product to translate each time, but in the case below I left a night with an automatic task that every 10 minutes clicked on wpml page to select some product to translate. Before it worked, but for a few days it didn't't. The next morning I found what you can see in this video hidden link
You have all the access from the other ticket. The site has two level of cache, wp-rocket for pages and redid-cache for database. This is the last implementation because I thought that was an issue with site performance, but it didn't change anything with wpml, I notice only sometimes a better site performance.
I configure the wp-config with
The issue is getting worse, but it has been there for some time. I tried in the past to deactivate almost all plugin (I only left woocommerce and strictly related plugin), but it didn't worked.
By now the production site is often unusable, with the shop owner demoralized because of this...
The staging site I provided in the other ticket is a little less problematic because I didn't use it to translate and also because there so less network traffic in that site
Thank you for contacting WPML support. We apologize for the delay in responding to your message. We are currently experiencing a high volume of support requests.
I understand this ticket was created to troubleshoot the error shown in the attached screenshot, as the issue with the automatic translation is already being handled in the other ticket, and I also see it was escalated to our second-tier support.
Regarding the message:
"Some taxonomies in your site are forced to be untranslatable. This is causing a problem when you're trying to run a multilingual WooCommerce site."
It happens when a plugin or a theme sets a product-related taxonomy not to be translatable. To fix this issue:
Go to WPML > Settings > Taxonomy translation and make sure all the related product taxonomies are set to (click on the lock to unlock) 'Translatable - only show translated items' or 'Translatable - use translation if available if available or fallback to default language'.
For example, product_cat (Product category) should be translatable.
I didn't mention in this ticket
"Some taxonomies in your site are forced to be untranslatable. This is causing a problem when you're trying to run a multilingual WooCommerce site."
because your colleagues just solved in another topic. I open this ticket because if I do some translation with your plugin, the site became a lot slow in the admin page as I show in the videos. Sometimes it gave me gateway error and I think that's not a server error. I check all the ticket you have and I follow every single suggestion but the issue remain. WPML works fine only if I didn't start new translation. It's very frustrating. Your plugin block all the flow of every person who work in our site in the admin page. Also if I updated prices and stock quantity about products with a bulk operation or REST API software, the site became so slow, almost unusable for lot of hours. did you see the video I made for you?
Thanks Daniele
I can see that the other ticket is still active and has been escalated to our second-tier support.
To ensure a smooth process, kindly provide any updates or findings related to the issue in that ticket. This way, we can avoid starting over and keep track of all the necessary information.
