I was just testing this out, and my process was interrupted before I could verify the Stripe integration, at the Delivery step --- because I hadn't yet set up my Locations and Shipping in the admin. So, I emptied the cart, set all that up, redeployed for good measure, and tried again as the customer. Again, the Delivery step stops me -- no options appear and I can't advance to Payment. Any ideas about what I might try? Thanks for the great content and the super-useful one-click deployment script!
Hey, this sounds odd! I have never seen the delivery step causing trouble - in fact, it should not be necerssary to setup locations, you sould be able to just choose the predefined "Standard Shipping" or "Express Shipping" during the checkout flow. Did you remove these two options from the admin dashboard?
@@funkyton Thanks for replying! No, I didn't do anything like that. I'm starting to suspect that Medusa 2.0 isn't all that stable; I keep running into things like this that I can only rectify by doing a new one-click deployment from your script, which of course won't be viable once I have customers and order histories to maintain. The last one that smelled a little similar was when I ran the deployment, added a product, then went back into settings to add a USD currency option, then added a USD price to my product instead of EUR. The price never showed on the page, even if I deleted the product and created a new one, which also prevented me from adding the item to the cart. I could only get a price to reappear if I changed it back to EUR. That marked my third or fourth needed new deployment.
@@JaredGallardo Yes, there's quite a few open issue on github, and I have found a number of things as well. So I agree not 100% production ready without tinkering at this point. But I am quite hopeful, because many issues that I have found in the past have already been patched, so I assume stability will increase. And if you don't have complex customizations, in yout project, it's realatively easy to update dependencies to get the latest fixes... Anyway, I will let you know, once I have tested the stripe integration again. I had no issue getting past the delivery step without Stripe setup just now, will check again asap, with stripe configured.
@@JaredGallardo I did a test earlier today, on the latests version of the template (2.0.1). And I had no trouble getting past the delivery step at checkout. I just prefilled shipping info, and chose "standard shipping". Now, I did not change any countries or regions, I just used to seed data pre configured Europe region. I suspect that when you setup your region (US?) that, something is missing. Maybe the standard shipping isn't available in the region you have setup. I know medusa supports per region delivery, which suggests that you have to enable at least one shipping method in the region you setup. So, if I were you, I would try to mess around with the region setup, adn shipping setup and hopefully be able to resolve it that way. If something got messed up in you database, you can try to temporarily connect to a clean db and reseed. Instrucionts here: ruclips.net/video/6hKahRqL9YQ/видео.htmlsi=0lwt19UaON22zdJY While keeping your current database, in case you have spend a lot of time setting up products and such
Do you know about paypal payments im using medusa 2.0.1 and i tried installing paypal payments to my backend via npm install medusa-payment-paypal and it is outdated is there another way to do this?
Unfortunately, there are still many 1.x npm packages that haven't been updated to support the 2.0 architecture. I don't have any experience with the PayPal module myself, but I know most people are using the Stripe module, and I think that's why it was converted even before the 2.0 launch. The PayPal npm module has fewer than 1000 weekly downloads 😬. So, I would be a little worried about the future maintenance of that module. I think we need someone to submit a pull request to the GitHub repo to get it updated, as I don't think (just a guess) that the Medusa core team is prioritizing it right now. 😫 Personally I am patiently waiting for the MeiliSearch module to be 2.0 compatible. But I also think this has low priority, as this is also a lesser used module
I was just testing this out, and my process was interrupted before I could verify the Stripe integration, at the Delivery step --- because I hadn't yet set up my Locations and Shipping in the admin. So, I emptied the cart, set all that up, redeployed for good measure, and tried again as the customer. Again, the Delivery step stops me -- no options appear and I can't advance to Payment. Any ideas about what I might try? Thanks for the great content and the super-useful one-click deployment script!
Hey, this sounds odd! I have never seen the delivery step causing trouble - in fact, it should not be necerssary to setup locations, you sould be able to just choose the predefined "Standard Shipping" or "Express Shipping" during the checkout flow.
Did you remove these two options from the admin dashboard?
@@funkyton Thanks for replying! No, I didn't do anything like that. I'm starting to suspect that Medusa 2.0 isn't all that stable; I keep running into things like this that I can only rectify by doing a new one-click deployment from your script, which of course won't be viable once I have customers and order histories to maintain. The last one that smelled a little similar was when I ran the deployment, added a product, then went back into settings to add a USD currency option, then added a USD price to my product instead of EUR. The price never showed on the page, even if I deleted the product and created a new one, which also prevented me from adding the item to the cart. I could only get a price to reappear if I changed it back to EUR. That marked my third or fourth needed new deployment.
@@JaredGallardo Yes, there's quite a few open issue on github, and I have found a number of things as well. So I agree not 100% production ready without tinkering at this point. But I am quite hopeful, because many issues that I have found in the past have already been patched, so I assume stability will increase. And if you don't have complex customizations, in yout project, it's realatively easy to update dependencies to get the latest fixes... Anyway, I will let you know, once I have tested the stripe integration again. I had no issue getting past the delivery step without Stripe setup just now, will check again asap, with stripe configured.
@@funkyton Much appreciated!
@@JaredGallardo I did a test earlier today, on the latests version of the template (2.0.1). And I had no trouble getting past the delivery step at checkout.
I just prefilled shipping info, and chose "standard shipping".
Now, I did not change any countries or regions, I just used to seed data pre configured Europe region. I suspect that when you setup your region (US?) that, something is missing. Maybe the standard shipping isn't available in the region you have setup. I know medusa supports per region delivery, which suggests that you have to enable at least one shipping method in the region you setup.
So, if I were you, I would try to mess around with the region setup, adn shipping setup and hopefully be able to resolve it that way.
If something got messed up in you database, you can try to temporarily connect to a clean db and reseed. Instrucionts here: ruclips.net/video/6hKahRqL9YQ/видео.htmlsi=0lwt19UaON22zdJY
While keeping your current database, in case you have spend a lot of time setting up products and such
Do you know about paypal payments im using medusa 2.0.1 and i tried installing paypal payments to my backend via npm install medusa-payment-paypal and it is outdated is there another way to do this?
Unfortunately, there are still many 1.x npm packages that haven't been updated to support the 2.0 architecture. I don't have any experience with the PayPal module myself, but I know most people are using the Stripe module, and I think that's why it was converted even before the 2.0 launch. The PayPal npm module has fewer than 1000 weekly downloads 😬. So, I would be a little worried about the future maintenance of that module. I think we need someone to submit a pull request to the GitHub repo to get it updated, as I don't think (just a guess) that the Medusa core team is prioritizing it right now. 😫
Personally I am patiently waiting for the MeiliSearch module to be 2.0 compatible. But I also think this has low priority, as this is also a lesser used module
Thank you so much for the feedback I think I’m just gonna use Medusa v1 instead
@ also still a really solid option for most use cases! 🙂