"WooCommerce Multilingual & Multicurrency" slows our site's REST API to a crawl. When using Woocommerce API batch update, to update stock only (25 products at once) it takes close to 4 minutes to run the update, when disabling the plugin, it completes in 2-3s.
Active plugins: Woocommece, WooCommerce Multilingual & Multicurrency, WPML Multilingual CMS and WPML String Translation
Wordpress theme: Twenty Twenty-Three
Memory limit: 512M (PHP & WordPress)
PHP version: 8.0.30
Plugin versions: Latest as of 30/10/2023.
Products: ~1900 in main language + 5 translated languages (translations sync stock etc from main)
All the troubleshooting steps found in the WPML troubleshooting page, etc have been tried multiple times.
Any ideas what could be the problem or where to look for more debug information?
Example partial batch payload:
[{"id": 31741, "stock_quantity": 0}]
I understand the issue you're having and will try my best to assist you in this matter. To get a better overview of the site and server, please share the debug information of the site in the section that will appear below this ticket.
Hello There,
Thank you for trying out the suggestion.
To investigate the problem, I conducted some tests within my development setup. I updated the stock for over 30 products using the REST API via the "Postman" application. With WooCommerce Multilingual activated, the process finished within 8-9 seconds. Here's a screenshot for your reference: hidden link
When I deactivated the plugin, the duration reduced slightly to 6-7 seconds. Such a minor difference is expected since the stock field synchronizes with the translated product. Therefore, during an update, the translated product is updated as well.
Since it takes several minutes on your end, there might be a configuration related to the API causing the delay. Would you please check and confirm that the WooCommerce Legacy API is not enabled on your site? Please follow the steps below.
- Go to "WooCommerce > Settings > Advanced → Legacy API"
- Ensure that the "Legacy REST API" option is disabled.
You can also switch to a default theme like 'twenty twenty-one' and check if the issue persists there or not.
Let me know the update. I will be happy to help if you need further assistance in this matter.
Since the issue is happening in a minimal setting, could you please verify if there are any restrictions in place for the REST API on the server? Additionally, if there's any server-side caching active, consider clearing those caches too.
If the issue persists even after that, a closer inspection will be required to understand the root cause of the issue. 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 have a testing site where the issue is replicated.
You will find the needed fields 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 backup 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
Hello There,
Thank you for sharing the DB and Site dump.
Unfortunately, the site dump is returning a Fatal Error which is why, I can't proceed further.
Instead of sharing the WordPress file, will it be possible for you to create a migration package using the All-in-one Migration plugin and share the package with us? This process is more easier and recommended as well.
Just install the All-In-One Migration plugin(https://wordpress.org/plugins/all-in-one-wp-migration/) on your site and create an export file by excluding the Revision, media files and comments(Screenshot: hidden link). Once the export file is ready, Download the file, upload it to Google Drive, and share the link to the file. FYI, the files and database will be included within the downloaded file.
You can also check the guide on exporting using the AIO Migration plugin: hidden link
I have enabled a private field for you so that you can securely share the file(Simply add the link as you did before).
I will deploy the package and investigate the issue further. Looking forward to your response.
Hi There,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
Thank you for sharing the package. I'll proceed to set it up in my local environment for a deeper examination. Once I have insights or updates, I'll surely inform you.
I truly appreciate your patience and kind cooperation in this matter.
I hope this message finds you well. Our development team has conducted a thorough investigation into this matter. We've identified the root cause of the problem, and it appears that resolving this issue will require significant refactoring of the code. I understand that this might be disappointing news, and I want to assure you that we are committed to finding a solution as swiftly as possible.
Please rest assured that we are doing everything we can to resolve this as quickly as possible. I will make sure to keep you updated on our progress and notify you as soon as a solution is available. Additionally, updates will be posted on the Errata page, so we recommend checking there for the latest information.
Your patience and understanding in this situation are greatly appreciated. If you have any further questions or concerns in the meantime, please do not hesitate to reach out.
I'm glad to learn that the issue has been identified. Is there some kind of timeline for a possible fix/workaround? Are we talking days, weeks or perhaps even months?
This issue is critical to us and I'd assume to many others as well, as it prevents any kind of mass product updating.
At this moment, we do not have a specific estimated time of resolution (ETA). I understand this may not be the news you were hoping for, and I sincerely apologize for any difficulties this may be causing you. Please be assured that our team is diligently working to resolve this issue as efficiently as possible.
We value your patience and understanding in this matter. I will ensure to keep you informed with regular updates as we progress towards a solution.
Thank you for reaching out for an update on the ongoing issue. I wanted to let you know that our development team is currently working on resolving the problem. As of now, we do not have any new updates to share, which is why the Errata page remains unchanged.
As mentioned before, a significant refactoring in code is necessary to effectively address the issue. Our team has pinpointed that the root of the problem stems from a specific hook: woocommerce_rest_insert_product_object. There are different actions and logic to sync a product with its translation involved with this. So, we need to be careful about the approach to solve the issue.
We understand the importance of this matter to you, and we are doing everything we can to expedite the process. As soon as there are any developments or updates, we will make sure to inform you promptly.
Thank you for your patience and understanding in this matter.
