[Picflick]

Good day,
I am experiencing an error when my customers check-out with a product… there is a throbbler loading icon by the ‘checkout’ button that indefinitely loads (see https://ibb.co/jn6zNYP).
To Reproduce – Go to any product, Add card, Click check-out, Scroll down as if you about about to click ‘pay’, See loading icon constantly spinning.
Expected behavior – The page should load fully and no throbbler showing. This confuses users and they will wait forever before clicking checkout.
I have performed a conflict check by deactivating all the plugins and themes, an slowly activated them to see which is causing the issue – I have identified that MultivendorX Pro plugin is causing this issue. See here: https://www.loom.com/share/3ede0e50c0514b5f9d6a1e27573da39e?sid=185669db-8d19-44b8-915f-ce11033a8f88
I am not sure what the error is but it seems that it is preventing the JS code. Please can you assist debugging.
Thanks,
PicFlick

[Sangita Support Squad]

This reply has been marked as private.

[Picflick]

This reply has been marked as private.

[Sangita Support Squad]

Hi there,We’re unable to access the admin dashboard. When trying to log in, we’re seeing this issue: https://tinyurl.com/246sp6nb.

Could you please provide the correct admin access so we can proceed with assisting you further?

[Picflick]

My apologies Team – I have assigned the administrator role. Please try again

[Sangita Support Squad]

Hello there,

Thank you for sharing the admin access. We’ve logged into your site and deactivated all plugins except WooCommerce, MultiVendorX, MultiVendorX Pro, and WooCommerce PayPal Payments. After testing, we did not encounter any issues with the checkout process. You can review the test in this video: https://www.awesomescreenshot.com/video/43397635?key=30b3a1414b7680b4bff73a53561e1494.

Regarding the error in the vendor setup wizard, as mentioned earlier, the issue is not related to MultiVendorX. The error is coming from the Jetpack plugin:Uncaught Error: Call to undefined function Automattic\Jetpack\Forms\Dashboard\get_current_screen() in /wordpress/plugins/jetpack/15.0-a.5/jetpack_vendor/automattic/jetpack-forms/src/dashboard/class-dashboard-view-switch.php:327

We kindly recommend reaching out to the Jetpack team for further assistance with this issue. If you’d like, you can loop us in at contact@multivendorx.com when writing to them, so that if anything is required from our side, we can communicate accordingly.

In the meantime, if you need any further assistance, please don’t hesitate to let us know.

[Picflick]

Hi,

I sincerely appreciate the time taken to investigate our website. I recognize that it did work with those 4 core plugins activated.
I have done some additional testing my side. I proceeded to re-activate every plugin one-by-one and refreshed the checkout page until I found the issue. I suspect that it is ‘WooCommerce.com Update Manager’. Will you please be able to test this on your end and confirm? It would really help me by having a second party confirm.
The reason also why I was struggling to identify the issue was because I was refreshing the browser which retained the cache and cookies. When I was testing, I closed the browser each time I activated a plugin to ensure that that it was completely fresh, which led me to identifying that ‘WooCommerce.com Update Manager’ may be causing the issue. Looking forward to your response on this.

Regarding the error in the vendor setup wizard, I have been speaking with wordpress.com. They have found what is causing the issue and I have included contact@multivendorx.com in the conversation for you to see.

Thanks again for the great interaction and support.

[Sangita Support Squad]

Hello there,

Thank you for getting back to us with the updates. We’re glad to hear that you were able to identify the conflicting plugin. Since conflicts with third-party plugins fall outside our scope, it may be best to reach out directly to the team responsible for that plugin—they’ll be in the best position to assist you further.

Regarding the setup wizard issue, as you’ve already contacted us over email, we’ll continue the conversation there and get back to you shortly.

In the meantime, if you need any additional assistance from our side, please don’t hesitate to let us know—we’re happy to help wherever possible.

[Picflick]

Hi Sangita,
I have an update to share…
When we activated only the core plugins (see https://ibb.co/spfmqYFg) and ran the Check Conflicts test, the PayPal checkout displayed correctly every time — no spinning throbbler. This is when either Themify or Storefront or Twenty-twenty-four themes are activated. Once we activated MultivendorX Pro, the issue started appearing intermittently: sometimes the checkout loads fine, but other times the throbbler spins indefinitely. This suggests a potential conflict interaction between MVX Pro + PayPal plugin.
Would it be possible for your team to take a closer look at our staging site with this in mind?
Thanks and regards,
PicFlick

[Sangita Support Squad]

Hello there, Thank you for getting back to us.

We’ve rechecked the issue on the staging site you shared, but we were not able to reproduce any problem with the PayPal plugin during checkout. You can view our test recording here: https://www.awesomescreenshot.com/video/44464239?key=3bba3f59fa4cb8ae4dfaa57f37632ccc. We’ve tested this multiple times without encountering the issue.

Since you mentioned that the loading issue appears intermittently, could you please check if any specific error message or console error is displayed when it occurs? Having that information will greatly help us troubleshoot the problem more effectively.

Looking forward to your update.

[Picflick]

Hi Sangita,

Thanks again for rechecking this for us. Unfortunately you did not test the correct PayPal plugin. Let me share more details…

I only have the following plugins activated – MultivendorX, MultivendorX Pro, WooCommerce, WooCommerce PayPal Payment (the official PayPal payment gateway for WooCommerce).
My theme is active but it is not conflicting.
There are only 2 Payment gateways activated under WooCommerce >> Payments (please see: https://ibb.co/1G2SvHZK).
1) WooCommerce PayPal Payment – comprises of A) debit/credit card and B) PayPal checkout
2) MVX PayPal Marketplace. This is your payment gateway to set up recurring subscriptions.

Now this scenario is for a customer checking out to purchase a single product, not a recurring subscription, so I only want them to be able to have the option to choose from #1 above (I will develop the custom code for this). BUT the throbbler is still appearing (see https://ibb.co/v6qDZsnc). I am explaining here that the ‘Proceed to PayPal’ button is not supposed to render like that – it should look like this: https://ibb.co/MxhKxbWK or https://ibb.co/R4pRcLkn. When I deactivate the MVX PayPal Marketplace then it consistently loads – see detailed video here: https://www.loom.com/share/9b034e74faad40cbb38825a24659df22.

Please add a product to cart and navigate to /checkout page when MVX PayPal Marketplace is deactivated and when MVX PayPal Marketplace is activated. You will see the difference.

Appreciate your assistance troubleshooting this. Thanks

[Sangita Support Squad]

Hello Pickflick,

Thank you for getting back to us with the details. We have reviewed the flow on your end, and as you mentioned, it seems there is a conflict between our PayPal Marketplace module and the WooCommerce PayPal Payments plugin. Since this issue involves a third-party plugin, identifying the root cause and implementing a fix would require considerable time and effort. As we shared earlier, our development team is currently dedicated to the MultiVendorX revamp, working hard to deliver it as quickly as possible. Given this, assigning them to debug this conflict right now would be quite difficult.

As a potential workaround, the flow you described—where the PayPal Marketplace option is loaded only for subscription products—is a feasible solution. The issue occurs only when all the payment options appear together in the checkout, so if the payment options are separated as per this flow, the throbber issue should not occur.

That said, in our revamped version, we will ensure that no such conflict occurs for our users, providing a smoother and more reliable experience.

Thank you for your patience and understanding—we truly appreciate your support as we work on these improvements.

[Picflick]

Hello Team,

Thank you for your response, but I must stress that your reply is not acceptable. The issue is very clearly a conflict within your PayPal Marketplace module. When only WooCommerce PayPal Payments is active, the checkout works perfectly and consistently. The moment this payment method is enabled, the PayPal checkout begins to break. That is not a “third-party issue” — it is an incompatibility directly introduced by your plugin.

This should not require “considerable time and effort” to identify. It is a direct and reproducible bug that occurs 100% of the time and can be demonstrated in a few clicks. Brushing this off as something for a future revamp is not a valid solution, especially when businesses like ours are relying on your plugin for real transactions.

This is a critical checkout bug that cannot wait for a long-term revamp cycle – it requires a patch, or at the very least, a hotfix to allow both plugins to operate together. Given that you have acknowledged the conflict, I must insist that this issue be escalated to your development team to assist with the workaround proposed (limiting the PayPal Marketplace option to subscription products only).

I reiterate, this issue directly impacts our sales flow and prevents us from offering customers the seamless checkout they expect. We purchased MultiVendorX Pro in good faith with the understanding that it integrates with WooCommerce and PayPal properly. At present, it does not.

Please confirm whether this issue will be addressed promptly. Otherwise, we will have to consider our options, as continuing to operate with broken checkout functionality is not viable.

[Sangita Support Squad]

Hi there, We sincerely apologize for the inconvenience this issue has caused you and your business.

We truly wanted to assist you, and our intention was never to cause any disruption to your checkout flow. Regarding the custom code for the payment option flow, our initial recommendation was based on the current workaround available. We understand that this situation has caused frustration, and we completely acknowledge the impact it has on your sales and operations.

That said, I have escalated your issue to our development team for immediate attention. As soon as I receive an update from them, I will keep you posted.

We appreciate your patience and understanding while we work to resolve this issue, and we are committed to helping you restore a seamless checkout experience as quickly as possible.

[Sangita Support Squad]

Hello There,

Thank you for your understanding. We have looked further into the conflict, and it seems the issue at checkout occurs when the Payment Button Type is set to Smart Payment Buttons. However, if you set the button type to Standard, the issue no longer appears (https://tinyurl.com/22xhajqd).

Currently, we are unable to access your previously shared staging site, so we cannot verify this on your end. Could you please set the button type to Standard by going to Woocommerce >> Settings >> Payments >> MVX PayPal Marketplace, test the checkout again, and let us know the results? Once confirmed, we can proceed accordingly.

Thank you for your cooperation.

[Picflick]

Hi Sangita,
Hope all well.
I’d like to provide an update on this… I proceeded to develop custom code and inserted a snippet into our functions.php. This resolved the error.
I appreciate your suggestions, however we required a more robust solution that would work with the smart buttons. It is unfortunate that we are not able to use the full functionality of other plugins due to the incompatibility of MVX. I do hope that your development team prioritise ensuring that core functionality (like PayPal payments) can work properly in your new released.
Thanks and regards,
PicFlick

[Sangita Support Squad]

Hi PicFlick,
Hope you’re doing well too.

Thank you for the update. I’m glad to hear that you were able to implement a custom solution on your end and resolve the issue.

We truly appreciate your feedback regarding the compatibility challenges and understand how important it is for core functionalities—especially payment options like PayPal—to work seamlessly with smart buttons and other plugins. Please rest assured that our development team is actively addressing these concerns as part of the upcoming revamp. The new version is being built with improved compatibility and stability in mind, so experiences like this are significantly reduced.

Thank you again for sharing your thoughts and for your patience throughout this process. If you need any assistance in the meantime, feel free to reach out.

[Sangita Support Squad]

As you may already know, we have released the revamped versions of our plugins. We kindly request you to update to the latest version on your end and check accordingly.
Following this, we will be closing this thread for now. If you encounter any issues with the latest version or have any questions, please feel free to create a new support thread, and we’ll be happy to assist you.

[Author]

Posts