Ceecee

@shahzeenfarooq after I reverted from making it an elementor page I tried to replicate the blocks that were there before but I can totally understand what happened there. So on the Cart Page I should remove the Checkout blocks, everything circled in blue in this image ? Is there anyway to import the “original” checkout blocks for the cart? Deleting cart page and reinstalling woo or something? I know the “quick checkout” on the cart Page is preferred by my client.

I do have some questions regarding staging. Say i were to uninstall woocommerce (I wont but just so I understand) , is there cloud somewhere with our shop data that I could download onto another site ? Or is our shop data only kept on our server/our db? I just remember somewhere it had me login to woo and login to jetpack and connect my site.

Also, on my staging site that is just a clone of the live site (all api keys and everything is the same except the url), im seeing some warnings about our stripe webhook config. What’s the right way to handle this connection? Im assuming the warning are because stripe is expecting webhooks to be coming from cochiseharmreduction.org not staging cochiseharmreduction.org.

And I really cannot thank you enough. Its rare these days to actually find a SaaS product whose customer service doesn’t leave you hanging or just shrug and say “its on the lost but not a priority. I know its been 3 years and counting”. I very much appreciate your commitment to helping your users to figure out and make the most of your product.

One thing i do want to flag is the webhook that was active to send ‘order changed’ notifs to my db – i just paused it since we are running tests and i dont want that to affect my live inventory and orders sheet. So just in case that affects anything, i thought i should make a note (to myself too)
Here is the current system report . I really cant thank you enough for your help.

also I have no browser extensions and it’s happening for my customers on their devices as well so isn’t specific to my device or browser.

thank you in advance for your help with this

• This reply was modified 5 months ago by Ceecee.

I have gone through and deactivated everything and turned back on one by one and yes I am happy to do so again while recording.

however it sounds like Moses hit the nail on the head. He said JavaScript validation of the checkout block email address input relies on the user focusing in so when autofill adds the value, the error is thrown even though the email address input has a valid value. There’s a condition somewhere that throws an error if the email wasn’t clicked into, even though Autofill did give it a valid email address.

and worse then that is it throws an error on the frontend but the payment method is charged and an order is created without giving the user feedback that their order succeeded so they hit the Place Order btn again. There are classes and attributes that change on the direct parent of the input (class="wc-block-components-text-input wc-block-components-address-form__email is-active" ) and the input itself when interacting with the input that I suspect are part of what this validation is relying on.

whats the workaround for this? is it toggling the is-active class on the class="wc-block-components-text-input wc-block-components-address-form__email is-active" when the page loads? Or how can i hook into the submit event listener to validate this input before it sends the payment request to Stripe ? should i add a .click() into the input[type=email] on load so even if autofill is used at least its gained focus ?

@fetenlakhal apologies it looks like i replied to you on a different post instead of this one.

if the checkout process (im using the checkout block that comes with the checkout page when installing wordpress, havent edited with elementor for checkout or cart page) is relying on :focus events in each of the inputs , it sounds like thats exactly the problem or at least part of it. Autofill just fills in values, it doesnt create focus into the inputs its filling.