This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with bulk translations using WPML, resulting in a 504 error even when translating a single post. Credits are being utilized despite these errors, and URLs are showing a '?' at the end of the slug after using WPML. Solution: We recommend increasing the
max_execution_time
to 300. This adjustment was tested by sending 20 jobs at once and it worked as expected. It's also advised to consult with your hosting provider to explore why the 'Bad Gateway' error occurs, particularly to check if large queries are being restricted by the server. Starting with smaller batches of up to five may also help mitigate the issue.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we 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. Should you need further assistance, please open 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.
There are no separate configurations made, this is just a custom post type created for all the products we have on site and we have used ACF plugin to fill the data as per different varities of products inside.
Can you please give a cross check from your side as well, as what is blocking or making the load heavy which stopping the WPML to make bulk translations that would be highly appreciable, I also tried looking into network tab but didn't catch any certain error, or might be I overlooked something which actually needs attention.
Hi Carlos,
I am looking forward to get rid of this BAD GATEWAY request as soon, It will be highly admirable and appreciating, If you get this done on priority, I have cross checked the custom template pages and custom plugins as well, but nothing seems to be misconfigured or the reason to cause heavy load on site. Let me know any of the resources required from my side.
I have escalated this ticket to our 2nd tier of support so our specialists in the 2nd tier can take a deeper look at this issue and isolate its cause. Please don't modify the staging site until a solution is found.
I will keep you updated on the evolution of this ticket 🙂
The custom post type contains a significant number of fields, approximately 1,000+ per post, and the site's max_input_vars is currently set to 10,000. I recommend increasing the max_input_vars limit to 30,000 to see if it resolves the issue.
Additionally, it would be helpful to get insights from the server, possibly by checking the server logs, to ensure we are not exhausting any resources during this operation.
Appreciate the efforts of Technical team, I have increased the memory limit to 512M and max_input_vars limit to 30,000. Here am sharing the Screenshot for server utilization. May be that will help 🙂
Kindly, update them with one more thing i.e. I looked into the WPML settings and found that the table with data fields are already not in the count for translation purposes, so it should not likely impact the bulk translations. Plz refer screenshot.
Hi Carlos,
Any updates please !!
We are really facing this issue since last one month now and a complete one month delay it is. Our stakeholders are loosing patience now. Kindly get this resolved. As your team has got all the access to production and stage site both, kindly conduct tests properly to get closer to the resolution.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Madrid (GMT+02:00)
Hi there!
This is Paola and I will continue with the ticket as Carlos is on holidats.
The second tier replicated the site on localhost, and it works as expected when the max_execution_time is set to 300. I sent 20 jobs at once to test.
As noted earlier, the requests are quite large due to the high number of fields. He recommends you consult your hosting provider to determine why the "Bad Gateway" error keeps occurring; getting server logs from them would be beneficial. Given that they're using WP Engine, it's likely that large queries are being restricted.
Additionally, he suggests starting with smaller batches of up to five to mitigate the issue.
