[Waiting for user feedback] Attribute Syncronisation not working
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/
I've reviewed the entire conversation you had with my colleague Waqas and understand the issue. Since the attribute synchronization needs to run across approximately 31 languages on your site, the script will require more time to complete. After examining the WPML Debug Info, I noticed that the current max_execution_time setting on your site is set to 30, which is not sufficient to allow the script to finish executing, given the large number of languages in use.
Please increase the `max_execution_time` for your site to at least 300, and then try running the attribute synchronization again. For guidance on how to increase the `max_execution_time`, please refer to this guide: hidden link
Once updated, please clear the caches from your site and browser before running the attribute synchronization.
I hope it will help. Please feel free to let me know if you need further assistance in this matter. I'll be happy to help.
We have increased the max_execution_time to 60 minutes. And I have tried syncronising the attributes again, but with no luck. It was stuck at 15 products left for the past 50odd minutes.
With the access you provided, I inspected the issue directly on your site. Using the network request panel in the browser's debugger tool, I observed that the last product synced was the GPD WIN 4 Gaming Handheld PC (post_id: 107). After that, the process stopped running, resulting in a Cloudflare timeout error. Please check the attached screenshot(103937).
To investigate further, I deleted the GPD WIN 4 Gaming Handheld PC product and then tried restoring it from the Trash, but the timeout error occurred again. Please refer to the attached screenshot for details. So, the timeout error doesn’t occur just during attribute synchronization; it also happens when trying to restore items from the Trash.
It appears the issue may not be solely related to configuration or plugins but is likely tied to server-side settings, specifically with Cloudflare. Could you please try the suggestions in the following threads and see if they help resolve the issue?
- hidden link
- hidden link
... and this article: hidden link
I hope these resources will be helpful. If the issue persists, it would be best to reach out to your hosting administrator and ask them to investigate the root cause of the timeout error when restoring items from the Trash or running attribute synchronization. Since they have access to the server error log, they may be able to provide better insights into what might be causing the issue and offer guidance on resolving it.
You could also request the server error log from them and if they find that WPML or one of its add-ons is contributing to the issue, please feel free to share the log with us. We’ll be happy to review it and assist you further.
I took your suggestion and decided to completely turn off Cloudflare for the website just to see if the issue lays within Cloudflare (As if it were, it would be easier to pinpoint)
Hi There!
I hope you're doing well. Sorry for the delay in responding due to the weekend
Thank you for the update. Although you mentioned that Cloudflare is disabled, I rechecked and still noticed the Cloudflare warning after some time. Please refer to the attached screenshot.
Could you kindly confirm that Cloudflare is fully disabled on the staging site you’ve shared? If the issue persists even after ensuring this, it would be best to contact the server administrator for further investigation. Since the issue is not limited to synchronization but also affects WooCommerce functionalities, there might be another underlying cause. Reviewing the server error logs could help the administrator identify the issue or provide insights into what might be causing it.
If you can obtain the server error log immediately after running the attribute synchronization or restoring something from the trash, please share it in your next response. I’ll review it and assist you further with this issue.
I have disabled cloudflare and launched syncronisation, after I saw it failed -> I re-enabled it and replied back to you. I can 100% confirm its not cloudflare, as I never got any CF error, only syncronisation not moving forward.
While we investigate the issue, could you kindly disable Cloudflare on the site? This will allow more detailed error information to be logged in the server's error log, as we are currently experiencing a server error. Once Cloudflare is disabled, please rerun the attribute synchronization or try deleting a product and then restoring it. If the server error occurs again, please contact the server administrator and request the latest server error log.
Once you have the updated logs after the error, kindly copy them and share them in your next response. The logs may contain more detailed information about the error, which will help us find a solution more quickly. If needed, I will escalate the issue to the 2nd tier team for further investigation.
I hope you can understand. Looking forward to your response and appreciate your patience and kind cooperation in this matter.
It’s possible, but to rule out the cause of the issue, it would be best to remove or disable anything that stands between your site and the server (such as a CDN). This will allow your site to communicate directly with the server. We can then try again, and if the issue persists, we can check the server error logs to identify the exact cause of the problem.
I hope you can understand. Please give it a try and if you're able to get the Server error log, please share that in the next response. I will check and let you know what to do next.
