[Escalated to 2nd Tier] Automatic translation speed
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.
WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Background of the issue:
We are attempting to automatically translate over 100,000 products on our site hidden link using WPML. We previously inquired about the speed of the automatic translation process, but the chat was closed before we could respond.
Symptoms:
The automatic translation process is slowing down. Initially, the translation queue grew to 10,000 items on the first day, but now, almost a week later, it has only reached 15,000 items total.
Questions:
Is there a reason why the automatic translation process is slowing down?
Is there anything we can do to speed up the automatic translation process?
my name is Marcel and I will take over your ticket. Could you please provide me with site access for further testing?
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to a testing site where the issue is replicated.
You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
-Please make a backup of site files and database before providing us access.
-If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
I am currently creating a backup and don't yet see the input fields for FTP and WordPress access. I assume these fields will appear once I send this message to start the chat. If that’s not the case, could you please make these fields visible or enable the private box?
The input fields will appear once you accept the disclaimer and backup. You can use a placeholder email like noreply@wpml.org, as this address should be added to the secure fields to prevent any actual email from being sent.
In this case, it would be best if you create a copy of the site using WP Staging Pro so we can test it first on the cloned version. Please note that I won’t be installing any plugins on your live site. Since there's no need to go through any order processes, disabling outgoing emails shouldn't be necessary. We'll work directly on the clone, isolating this issue first and reviewing the debug.log.
We’re still investigating this issue. The logs initially show a gateway error, followed by re-queued jobs being sent to our editor. This points to a potential server communication issue, but we’ll also review the editor logs for further insights.
Good to hear you’re still investigating the issue. Here’s a quick status update: on the first day, the automatic translation added around 10k items to the translation queue; by the end of the first week, the total reached about 15k items, and now, two weeks into the automatic translation process, we’re at 35k items total.
Its a little bit of a problem, because at the current rate the translation queue will still take over 5 weeks to complete.
If there’s anything we can do to help, feel free to ask. Regarding the staging website information we shared: the WPML settings for translation are still set to ‘Different domain,’ but it may be useful, when testing, to switch to ‘Different language in different folders.’
Thank you for the information. As mentioned previously, we suspect a server-side issue, as the REST-API request seems to be blocked. Could you please provide us with a duplicator copy of the production site? This will allow us to test it in a different hosting environment and confirm if the server is contributing to the interference.
I made a copy using Duplicator and would like to share the file via Google Drive. However, I don’t want to make the link publicly accessible. Do you have an email address I can use to share the folder with you?
I am hesitant to send the Google Drive link due to security reasons, as the link would be publicly accessible.
Before I send it, I have a question. The automatic translation process seems to be slowing down. Is there a way to limit the automatic translation to just one category? If we could divide the 100k products into smaller groups, such as 10k products per group, perhaps the automatic translation process would be faster.
If there is another way to limit the automatic translation, could you please share that with us, or provide some code that could accomplish this?
If this option isn't possible, we will consider sharing the link instead.
as mentioned earlier, the private reply field is activated, so the link will be shared privately.
The automatic translation process seems to be slowing down. Is there a way to limit the automatic translation to just one category? If we could divide the 100k products into smaller groups, such as 10k products per group, perhaps the automatic translation process would be faster.
Limiting the translation would not resolve the issue if the REST-API request remains blocked. We need to investigate whether your server is causing the request to be blocked. Testing in a local server environment could help us identify the cause.
