MultivendorX Pro
-
Posts
-
-
-
-
We have already replied here https://multivendorx.com/support-forum/topic/error-when-updating-mx-pro-to-the-latest-version-and-several-mx-inlets-are-not/#post-214501. Kindly check.
-
-
-
-
-
-
-
-
-
-
Hello kevajo, We’ve reviewed the configuration of your test site and replicated it on our end. Upon placing an order on our site, the suborders were generated smoothly without any issues. However, when attempting to place an order on your test site, we encountered difficulties due to the checkout configuration.
So it would be better if you can create a new test site that will be an exact replica of your live site (where the issues will be replicated accordingly) and share the test site url, temporary admin and ftp access with us so that we can help you to solve the issue on your end.
While sharing the access don’t forget to mark your reply as private. -
-
Hello there,We have already added support for the HPOS feature of WooCommerce in our 4.1.0 version of MultiVendorX and the 1.3.0 version of MultiVendorX pro.
So as you are using older versions of both the plugins hence the notification is coming on your end.Once you will update the plugins to the latest versions you will not get the warning any more
-
-
Hello @kevajo, First and foremost, we sincerely apologize for the delay in implementing the fix in our core plugin. We fully understand your situation and the importance of keeping your plugins updated to the latest versions.
To address the issue, could you please provide us with a staging site that replicates your live site? On this staging site, we will update the plugins to the latest versions and then apply the fix for the ‘Allowed memory size’ issue. Once resolved, you can download the corrected plugins from the staging site and apply them to your live site.
Please note that our development team is currently handling some preassigned tasks, so there might be a slight delay in addressing the fix on your staging site. Rest assured, we are working diligently to resolve this as quickly as possible.
Thank you so much for your patience and understanding. We appreciate your cooperation -
-
-
-
Thanks for sharing the FTP details with us. Our dev team will look into it accordingly.
Please note that our development team is currently handling some preassigned tasks, so there might be a slight delay in addressing the fix on your staging site. Rest assured, we are working diligently to resolve this as quickly as possible.
Thank you so much for your patience and understanding. We appreciate your cooperation. -
-
Hello Kevajo,
Thank you for your cooperation and understanding. We apologize for the delay. Our dev team has been busy with preassigned tasks, which caused the delay in addressing your issue.
Rest assured, our team will add a fix for the “Allowed memory size” issue on your end as soon as possible . We will keep you posted on the progress.
Thanks again.
-
-
-
-
Hello @kevajo, First of all, we are extremely sorry for the delay. We completely understand how important it is for you to upgrade to the latest version of the plugin to benefit from the latest fixes and enhancements. Unfortunately, our development team is currently a bit occupied with further development, which has caused the delay in addressing your issue.
We understand the critical nature of the “Allowed memory size” issue and expect that by next week, our team will be free from their current work and able to focus fully on your site. We will keep you posted as soon as we address the issue.
We kindly request that you keep your site access open for our team. We are truly grateful for your understanding and cooperation thus far. -
-
@kevajo, We sincerely apologize for the extended delay in addressing your issue. Your patience and cooperation throughout this process have been truly appreciated.
As previously mentioned, our development team has been heavily engaged with critical projects over the past few weeks, which unfortunately led to a delay in resolving your specific concern.
We want to assure you that your issue has not been forgotten. Our team is planning to start working on a fix for your site by next week. We’ll keep you updated on our progress and inform you promptly once the fix is implemented.
In the meantime, we kindly request that you share the staging site(a exact replica of your live site) access and FTP access available for our team. This will ensure we can proceed without any access-related delays when we begin work on your issue.
Thank you again for your understanding. -
-
-
Hello @kevajo, We’ve applied a fix for the allowed memory size issue on your staging site. Please download the updated plugin from there and use it on your live site.
Note that this fix is currently applied only to your staging site and has not yet been added to our core plugin. Please avoid updating the plugin on your end until we notify you to do so.
We’ll keep you informed when the fix is incorporated into the core plugin.
Let us know if you need any further assistance.
-
-
-
-
-
-
-
-
-
Hi @kevajo, We’ve created orders with multiple products and varying stock quantities on your site but didn’t encounter any issues with suborder generation. You can review this on your staging site.
Could you please provide a detailed step-by-step guide on how to recreate the issue? This will help us assist you more effectively in resolving it.
-
-
Hello, Thank you for sharing the details with us. We are able to recreate the issue on our end, and our team will investigate it further. We plan to include a fix for this in our upcoming update.
You can track the progress of this issue here: https://github.com/multivendorx/MultiVendorX/issues/813.
-
-
Hello There, As shared earlier we have already filed this issue in our github and our team will add a fix for this in our future updates. Once the fix gets implemented we will surely keep you posted.
You can also keep track of the progress of the issue from here https://github.com/multivendorx/MultiVendorX/issues/813.
-
-
Hello, We apologize for the delay. We’ve just released an update today with various fixes. Rest assured, we will keep you updated as soon as we have a fix for the issue you mentioned.
In the meantime, you can track the progress of this issue here: https://github.com/multivendorx/MultiVendorX/issues/813.
-
-
-
Hello Kevajo, We have not implemented the fix for the issue with suborder regeneration in our latest update.
But not to worry. Hopefully in our next update we will be able to implement the fix and once the fix is implemented on our end, we will add the same for you as well.
Thanks for your understanding and cooperation so far. -
-
Hi @kevajo, Thank you for your patience and understanding. Our team hasn’t yet had the opportunity to address the suborder regeneration issue you mentioned, but we’re actively working on it.
We’re optimistic that our next update will include a fix for this issue, and we’ll make sure to apply it to your site as well.
We apologize for the delay and truly appreciate your continued patience and support.
-
-
Hi @kevajo, We have updated the plugin on your staging site and implemented the fix. Please check to see if everything is functioning correctly.
If all looks good, you can download the updated plugin from your staging site and apply it to your live site.
If you have any further questions, please don’t hesitate to reach out.
-
-
-
Please LOGIN to reply to this topic
