-
## Bug report
When trying to set the fulfillment as send, type error is thrown in the admin-ui.
TypeError
Cannot read properties of undefined (reading '0')
Call Stack
undefined
node_modul…
-
## Bug report
When the product contains at least 2 options and 2 variants and we try to delete the option in the admin dashboard, it will show a successful message, but the option will not be delet…
-
## Bug report
### Describe the bug
Hello, I am having a little bit of an issue, currently building a storefront with the js-client, and I am creating a checkout session with the stripe provider, I…
-
## Bug report
Payment Plugin support `capture` a boolean value that indicates whether payment should be captured manually or automatically.
This option is working perfectly in plugin (e.g PayPal, St…
-
## Steps to reproduce
* Create a product and add a simple variant.
* Variants > Edit Variants
* For the 1st variant select the hamburger menu and click Edit Variant
* Try to update anything and Cl…
-
## Bug report
### Describe the bug
Medusa store redirects to 'http://localhost:8000/order/confirmed/cart_xxxx....' after the completion of the order. Hence, the cart doesn't convert into an orde…
-
## Bug report
### Describe the bug
In the medusa-paypal-payment plugin the data parameter of patchOrder (paypal-sdk.ts line 49) is not passed to the HTTP-Client request. Therefore the amount…
-
## Bug report
### Describe the bug
trying to update to latest version of medusa-fulfillment-manual produce an error:
```
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
…
-
Describe the bug
When arranging swaps, the customer should not pay for the return shipping. However, the cost of the return is automatically added. Therefore, we have to manually remove the cost of t…
-
## Bug report
### Describe the bug
After setting up the medusa-payment-stripe (v1.1.48) plugin, we are unable to automatically capture payment in production.
Our Stripe webhook reports a 100%…