Forum Replies Created
-
Posts
-
Justin, in order to avoid the issue with Source and Token, we have completely removed this flow from our code and implemented Payment Indent.
In order to implement this payment indent, now if you are using stripe direct payment mode, then as per stripe API, only one vendor’s products can be purchased for one order. This is only for direct payment mode.
Dear All,
We sincerely apologize for our inability to provide a solution thus far.
We extend our gratitude to Justin for sharing the code, although it did not resolve the issue for us. We continue to encounter the same error.
Justin, can you share the stripe payment settings of MultiVendorX, so we can apply the same on our end.To be transparent, debugging this issue has proven more challenging than anticipated. Starting tomorrow, we will allocate one team to develop a new solution from scratch while another team continues to debug the existing problem. We hope to achieve a resolution soon.
In the interim, we propose a temporary solution: utilize WooCommerce Stripe to receive payments from customer and MultiVendorX Stripe Connect to process payments to vendors.
On behalf of the MultiVendorX team, we apologize for any inconvenience caused.
Hello there, It seems like that the migration was not done properly on you end earlier hence you were getting those warning messages. We have just deactivated the plugin on your end and activated ot again and now no warning messages are coming on your end as the migration took place successfully.
Kindly check and let us know if you need any further assistance from our end.Thanks for sharing the information with us. Our team is looking into the issue. Kindly provide us somer time. As soon as we will add a fix for the issue we will keep you posted.
@chipweb, as we are not able to recreate the issue on our end, hence we need to debug this on your end.
Please share a temporary admin, ftp access so we can check.
While sharing the access, don’t forget to mark the response as private.Hi Chipweb, we tried to recreate the issue, however we tried all the scenario , still we don’t have those errors.
But we added further checking on our end. Kindly install the plugin from this zip and test https://www.transfernow.net/dl/202403015k6dAk6n
Let us know whether this fixed the issue.
Hi, we will release an update by today EOD with this fix.
However if you want, you can use this fixed version of the plugin from here https://www.transfernow.net/dl/20240301eF31jJmR
Hi, sorry for the missed reply.
As per the log, it seems like your enquiry was “Hello, I added the plugin to a website and I got this error : “Could not add product Formation Ayurveda 201 to cart, this product/vendor is not eligible to be paid with PayPal Marketplace ” when I try to add a product to cart”
Please check with your PayPal team, whether the paypal id of the vendor is eligible to be piad via paypal marketplace api.
Please keep us posted.
Hi, sorry for the missed reply.
As per the log, it seems like your enquiry was “Hello, I added the plugin to a website and I got this error : “Could not add product Formation Ayurveda 201 to cart, this product/vendor is not eligible to be paid with PayPal Marketplace ” when I try to add a product to cart”
Please check with your PayPal team, whether the paypal id of the vendor is eligible to be piad via paypal marketplace api.
Please keep us posted.
@MaxenceTP, thanks for sharing the error. We will fix this in our next update.
In the mean time, if you can share a temporary admin, ftp access our team can fix that in your site.
While sharing the access, don’t forget to mark the response as private.@l.gan, sorry to see this issue on your end.
However we are still not able to recreate this on our end. Can you please for the time being roll back (https://wordpress.org/plugins/wp-rollback/) to the previous version. Then share a staging access (which is a exact replica of your live site), then share the admin, ftp access so we can check.
Looking for your co-operation regarding the same.
Hi SuedePflow, let me assist you here, our plugin only triggers these mails and ask your email server to sent them to the recipients. As you can see in the email log, that you shared, those emails has been triggered properly.
Now, your email server is not able to deliver them to the recipients. So kindly contact your email server admin to locate the issue.
Please do keep us posted.Hi @MaxenceTP, sorry to hear that you have faced this issue.
Our team has tested the flow with the latest version of WooCommerce, but didn’t face any issue.
So, can you please share a temporary admin, ftp access so we can check and assist you with this.Also, please do share how to recreate the issue for your site. While sharing the access, don’t forget to mark the response as private.
Hi KC, thanks for the further clarification.
In that scenario, you might want to consider using the PluginHive plugin. However, it’s essential to note that we haven’t tested it ourselves. For more effective assistance, their plugin support would be better equipped to help you.
Let us know if you need any further help.
