Our WPML comes up for renewal next month, what's the status of this? There's been no updates for well over a month now and this is really causing problems for our Woocommerce related stuff.
I totally can understand how crucial WCML is for your operations, and we truly appreciate your patience and understanding during this time.
We want to assure you that our development team is actively working on resolving these challenges. The delay is partly due to the complexity of the issue, which requires significant refactoring as I mentioned before for a sustainable solution. Our goal is not only to address the current concerns but also to enhance overall performance and compatibility.
While I don't have a specific update or timeline to share at this moment, please rest assured that this is a top priority for our team. As soon as we have any update on this, I will surely inform you. We are confident that the upcoming WCML update will include the necessary fixes and improvements.
We appreciate your patience and understanding in this matter. Your satisfaction is important to us, and we are committed to resolving this as efficiently as possible. Please feel free to reach out if you have any further questions or concerns.
I hope this message finds you well. Sorry for the delay in responding due to the weekend.
We are truly sorry for the inconvenience you've experienced with our product, and we understand your concerns, especially with the renewal approaching.
I want to assure you that your issue has received our full attention. Since implementing WooCommerce API support in WCML, this is the first performance issue we've encountered, and our development team has been actively working on a resolution.
During our thorough testing, we've discovered an effective measure that significantly improves performance. By disabling the "Copy taxonomy to translations" option, we've observed a remarkable 31% improvement in performance. This option can be easily disabled by navigating to "WPML > Settings > Posts and pages synchronization" in your settings.
Would you please check again by disabling that same option? We are committed to integrating a permanent solution in the upcoming version of our plugin to prevent future issues. Your satisfaction and continued trust in our solution are incredibly important to us, and we are here to support you every way we can.
Thank you for your patience and understanding. Please let me know the update and we'll be more than happy to help you further.
We did some testing by disabling this feature, but we aren't seeing any significant improvement.
We haven't tested this by adding new products and updating those, but updating existing ones through the API is very slow without any truly noticeable speed difference.
The small API payload will still run ten's of seconds compared to <1s without WCML enabled.
Is there a timeline for the upcoming version containing the fixes?
Sorry to hear that the result hasn't met your expectations. However, I want to share that adjusting the settings has positively impacted our performance profiler for the existing products as well. Could you try synchronizing the products and check again? Here are the steps for syncing products:
- Please go to WPML > Support > Troubleshooting
- Select 'Products' from the dropdown under "Clean up"
- Click on the "Synchronize Post Taxonomies" button.
- After that, click on the "Clear WPML Cache" button as well.
Please wait till the process is finished. Once done, please try to Bulk update the product again via REST-API.
I already have shared the Feedback with the dev team and they are surely going to assess further.
The problem is currently on our top priority list, and our team is testing the solutions from every angle. While we can't provide a specific ETA for the release of the fix, please be assured that I will keep you updated with any new information/updates as soon as I have any.
Thank you for understanding and I truly appreciate your patience and kind cooperation in this matter.
After some testing we can notice a slight increase, but it's still taking a long time to completely a small 25 product batch size. While with WCML disabled it's almost instantaneous.
Thank you for patiently following the suggestions.
Since adjusting the configuration hasn't improved the situation, it would be better if you could run a profiling session on your site to identify the problematic script or file. Profiling will give us a clearer view of what's causing the issue. You can use the Code Profiler plugin(https://wordpress.org/plugins/code-profiler/) or Blackfire(a third-party tool), both excellent for monitoring site performance and pinpointing delays.
If you're okay with this, please conduct a profiling session, replicating the scenarios where delays occur. The resulting report will be crucial for our analysis. Kindly share this report with us, as it will significantly enhance our ability to diagnose and resolve the issue.
We understand that this might require additional effort on your part, and we greatly appreciate your willingness to collaborate with us in this detailed capacity.
If you need any guidance on profiling, or if you have any other questions or concerns, please do not hesitate to contact us. We're here to support you every step of the way.
Thank you once again for your cooperation and commitment to improving your site's performance. We look forward to receiving the profiling report and moving closer to a resolution.
I apologize for not replying before, the reply notification got buried in my inbox.
The problem is with the API, the /wp-json/wc/v3/products/batch URL to be exact, the Code Profile plugin only works with the normal user facing URL's. I have included the frontpage code profile results.
The website has been perfectly responsive for users etc, but the API is very slow if the WCML is enabled.
The code profiler is effective for assessing frontend performance, but for API analysis, we suggest using the Blackfire tool. If you have access to Blackfire, it enables you to evaluate the API's performance and provide us with the resulting report. For comprehensive instructions, please consult this guide: hidden link
If you find the tool too complicated to use, don't worry. I'll pass your feedback on to our team to see if we can explore alternative ways to investigate the issue.
The slowdown is caused by the WCML as disabling it solves the problem. So I'd rather no get a paid service to tell me that, thank you though for the suggestion. Only the plugins shown in the Code Profiler are enabled and the API payload is [{"id": 31741, "stock_quantity": 0}].
Thank you for the update. I've passed your feedback to the team and they are looking into it. As soon as I have more information from them, I will inform you.
I appreciate your patience and kind cooperation in this matter.
Hi,
I hope you're doing well. I'd like to share an update that I received from the team.
Given that the site is only accessible internally, it is essential to obtain an API performance profile report to understand the reasons behind the solution not being effective on your end. Blackfire is indeed a subscription-based service, but, you can use the xDebug's "Profiler", which is a free alternative for assessing API performance. To understand the process of using the Profiler of xDebug, please check this documentation: hidden link.
This step is important for in-depth analysis and to facilitate precise enhancements. Please be assured that the issue is now advancing toward the release pipeline, and we are hopeful that the report you share will help us identify potential areas for refining the solution.
I truly appreciate you're continued patience and cooperation in this matter.
I've enabled a private field for you to securely share the information. As there are no dedicated fields to upload such a file, kindly upload it to Google Drive/One Drive and add the share link in the private field.
Thank you once again for your effort and kind cooperation.
Best regards,
Prosenjit
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
