[Sangita Support Squad]

It’s been long and we have not heard back from you. We presume your query is resolved now. We are closing this thread. If you need help or face issue in future please do create a new support ticket.

[Sangita Support Squad]

It’s been long and we have not heard back from you. We presume your query is resolved now. We are closing this thread. If you need help or face issue in future please do create a new support ticket.

[Sangita Support Squad]

Hello there, Thanks for getting in touch with us.
For the modification that you are looking for on your end, you can simply use a plugin like https://wordpress.org/plugins/woo-free-shipping-per-product/ on your end. Using this plugin you can create a shipping class and name it free-shipping then, assign the class to any product you need.
But please note we have not tested the plugin with MultiVendorX hence can not assure you about the compatibility. You can surely check the plugin on your end with MultiVendorX and let us know if you need any further assistance from our end.

[Sangita Support Squad]

Hello @MaxenceTP, Our team has already replied to you over the email so kindly check there.

[Sangita Support Squad]

Hi there, We have full confidence in the functionality of our beta version and believe it will perform flawlessly. However, to ensure a smooth experience for all our users upon the official release, we value feedback on how the beta version operates in various environments.
Once we’ve received confirmation from all users, we’ll proceed with the official release of the fixed version, tentatively by Friday or Saturday.
In the interim, we kindly request that you provide a staging site (a replica of your live site) with sandbox access added. This will enable us to conduct comprehensive testing there and ensure everything functions correctly on your end.
Thank you for your ongoing cooperation.

[Sangita Support Squad]

Hello @Tandy R M Silva, Currently we do not have any readymade custom code on our end for the modification you are looking for. But not to worry you may surely use custom code on your end to achieve your required flow on your end.
Do you have a developer on your end so that our team can guide them accordingly regarding the customisation.

[Sangita Support Squad]

@marchisotti.luca,
We deeply regret the inconvenience you’ve endured over the past week. Please understand that this situation arose due to sudden changes implemented by Stripe. While we have confidence in our beta version, we do not recommend using our beta version on your live site yet.
However, there are three alternate solutions available to ensure your payment flow continues smoothly:

Contact the Stripe team to temporarily disable the hCaptcha for your site. Once our fixed version is released next week, they can re-enable it for your Stripe account.

Use the WooCommerce Stripe payment gateway on your site to receive payments from customers. This way you will not be losing any revenue.
Then, use our Stripe Connect module to pay your vendors. This method ensures uninterrupted payments on your site and payment transfer to the vendor.

Alternatively, create a staging site (a replica of your live site) and provide us with your sandbox access. We’ll conduct comprehensive testing of the payment flows using our beta version on your staging site. Once all testing is completed successfully, you can implement our beta version on your live site.

Rest assured, we’re committed to resolving this issue swiftly and ensuring a seamless payment experience for you and your users.

[Sangita Support Squad]

Hello @Stacy Schnabel, sorry for the inconvenience you have faced. Kindly share the site url, temporary admin and FTP access of your site with us. We will check this and make the corrections accordingly.
While sharing the access don’t forget to mark your reply as private.

[Sangita Support Squad]

@marchisotti.luca, you can still use the current version of Stripe that you have for your site. Just contact Stripe team and ask them to disable the ReCAPTCHA settings for your stripe profile, it is that easy. Then you can keep accepting money using our current stripe module.

Having said so, you can also use the BETA version of Stripe. But as shared earlier, we are using latest stripe payment flow, which doesn’t support multivendor cart checkout for Direct payment mode of stripe.

[Sangita Support Squad]

Hello there, We sincerely apologize for the inconvenience you’ve experienced. Rest assured, we’ve addressed the issues with both Paypal Marketplace and Stripe Marketplace, and these fixes will be included in our upcoming MultiVendorX Pro update.
Our beta versions have undergone thorough testing and are functioning smoothly. However, if you’d like, please provide us with a staging site (a replica of your live site) along with your sandbox accesses. We’ll test both the Stripe Marketplace and Paypal Marketplace on your staging site, ensuring everything works seamlessly and after that you can use the same MultiVendorX Pro on your live site.
Also while sharing the access of your staging site don’t forget to mark your reply as private.

[Sangita Support Squad]

Hi there, Thanks for getting in touch with us. It seems there are some issues on your database that is why the option to add enquiry form fields is not appearing. So kindly add the below code in the functions.php file of your current active theme on your site –

add_action('init', 'fix_catalog_issue');
function fix_catalog_issue(){ 
delete_option('mvx_catalog_pro_enquiry_form_data');
}

Copy

After adding this code refresh the Enquiry form settings page and you will get the option to add form fields there.
After this you can remove the code from the functions.php file.

Let us know if you need any further assistance from our end.

[Sangita Support Squad]

Hi @marchisotti.luca, We use the source and token configuration of Stripe. But it is now conflicting with Stripe’s own hcaptcha settings. That is why we are asking the users to get in touch with the Stripe team and ask them to disable the hcaptcha settings for the time being. After that you will not face any issue with payments via stripe marketplace.
However, rest assured that to mitigate the issue with Source and Token conflicts, we have completely removed this flow from our code and implemented Payment Indent instead. This transition is currently underway and may require some time for implementation.
As part of this Payment Indent implementation, if you are utilizing Stripe’s direct payment mode, please note that according to the Stripe API, only one vendor’s products can be purchased per order. This limitation applies solely to the direct payment mode.

Thanks for your cooperation and understanding so far.

[Sangita Support Squad]

It’s been long and we have not heard back from you. We presume your query is resolved now. We are closing this thread. If you need help or face issue in future please do create a new support thread.

[Sangita Support Squad]

Thanks for the update.We are closing this thread. If you need help or face issue in future please do create a new support ticket.

[Sangita Support Squad]

Hello there, We have already added fix for this. Kindly update the MultiVendorX Pro to the latest version and check. If you need any further assistance please do let us know.

[Author]

Posts