Orders processed but not added to Store
Expresso Store
I’m using the sample templates, EE7.5.14 and Store 6.0.0. This is an updated version of Store from the old version that I had running on EE3.
I am able to complete an order using Stripe as the payment processor. I receive a notification that the order has been processed from Stripe and an email from EE saying that a new member account has been created.
Issues:
At checkout, {segment_1}/order/ORDER_HASH does not work, the browser redirects to the homepage of the site. I also tried “store_example/order/ORDER_HASH” but that results in the same redirect to the homepage.
User is unable to log-in with the credentials (email / password) that are created at checkout. The user can only access their account if they do a password reset.
Order not added to Store. Orders that are placed are not showing up in the Store add-on under “Orders”
As a result of Orders not being added to Store, the following also occurs:
3.1 Purchase is not listed in user account - Once the user gets logged in to their account, the order is not listed in their account. This is not surprising, since Store doesn’t have an order listed.
3.2 Email notifications from Store are not being sent. I have two notifications set up within Store (Admin Notification and Customer Order Notification). Each sends details of the order that was placed.
This is the store using the example templates: https://overnightaccountant.com/store_example/
Hi,
Thanks for getting in touch about this! (I went ahead and updated your request above and added numbers so we can more easily reference them.) I see from the other thread that your updating from Store 3.0.0.
I’m wondering if these issues are all stemming from issues around the member account having issues with the creation process as part of checkout flow.
Can you review the [Updating Order Fields From an Older Store Version](https://exp-resso.com/docs/settings_order_fields.html to confirm the member fields have been updated accordingly for the version 6 changes?
Thank you!
-Tom Jaeger
I did have $config[‘legacy_member_templates’] = ‘y’ in my config file. (I set it to ‘n’) I wasn’t using the mapped member fields in the previous version. Do I need to make any other changes?
Hi,
We just released Store 6.0.2, and it should fix the issue you’re running into. Feel free to reach out if there are any more issues youre still running into!
Thanks, Matt
Thanks! I’ll take a look.
Thanks, the 6.0.2 version takes care of the order / member issue.
I’m still having issues with my final checkout page. Checkout works if I use the provided templates but when I use the store_example/checkout-stripe template in place of checkout3 I get the following error.
Credit Card authentication has failed. Error: A token may not be passed in as a PaymentMethod. Instead, use payment_method_data with type=card and card[token]=tok_1RyCzYEAYjxUMEhwdhvuKPEA.
I also receive the same error when I take the code straight from the store_example/checkout-stripe.html and add it to my checkout3 template that worked with the previous version of Store. Is this error indicative of something that I’m doing wrong?
One thing I did notice is that on the standard store_example/checkout3 page, you have to select the Payment Method. I only have one (Stripe) and selecting it displays the CC details box which I then add to complete checkout. The select payment method option is not displayed on the Stripe page. I don’t know if this is related or not, just something I noticed.
Thanks for the update on version 6.0.2 resolving the order/member issue - that’s great to hear!
Regarding your checkout page issue, I’d recommend sticking with the checkout3 template instead of trying to use the stripe template. The checkout3 template is designed to work properly with the current version and handles payment method selection correctly, which is why you’re seeing it work as expected.
If you need any specific customizations, I’d recommend cloning the checkout3 template and then making your needed modifications to that cloned version. This way you’ll maintain the core functionality that’s working while being able to customize it to meet your specific needs.