Caleb Burks

The cart widget sounds ideal for this.

Widget: http://cld.wthms.co/7DKfkR
Frontend: http://cld.wthms.co/rgSmC5

It is up to your theme how this looks, or if there is a sidebar on the shop page though.

Yea, I don’t think you’ll get to use the data arg. Will need to look for your data being posted if possible.

Before woocommerce_after_checkout_validation is called, shipping methods themselves are brought in via $chosen_shipping_methods = WC()->session->get( 'chosen_shipping_methods' );

So maybe save your custom fields to the session then access that way?

I did a quick looksy, and seems that is how the Local Pickup Plus extension goes about doing things with their custom fields in the same area. The WooCommerce Mailchimp plugin might be another one to look at as I think it also adds a field outside the traditional area.

When doing the conflict testing (default theme, all other plugins disabled), I recommend doing two things:

1) Re-saving a specific product with a SKU. Just save the product admin page.
2) Doing a test checkout with that product, using a gateway like check payments.

Then see if the SKU shows up or not.

SKUs show for me in the order preview: http://cld.wthms.co/ws04rs, and in the order details: http://cld.wthms.co/4fv9sS. So there is definitely something on your site intefering with default behavior (assuming you are using the latest version of WooCommerce)

Just adding a setting won’t do much, what you really need is to display nothing on the main shop page.

And doing that will take some customization. Will need to check if the archives are pulling up the main shop page, and conditionally not output products:

https://github.com/woocommerce/woocommerce/blob/master/templates/archive-product.php

https://docs.woocommerce.com/document/conditional-tags/

Have you tested this with only the WooCommerce plugin, and a default WordPress theme?

I believe the cause of your problem is separate from the original user’s though, so please open up a new thread if you find the problem to still occur after following this guide: https://docs.woocommerce.com/document/woocommerce-self-service-guide/#section-4

So, it actually does do some fancy injecting now in WC 3.3+ if the theme doesn’t declare WC support specifically: https://woocommerce.wordpress.com/2017/12/09/wc-3-3-will-look-great-on-all-the-themes/

If the theme does declare WC support (or a default WP theme), then a page like “Shop” is taken over. The reasoning, afaik, is pretty much just that WP didn’t and doesn’t have a great way to manage post type archives. So we have a shop page that allows for content editing, but then have to inject that into the actual archive template. The alternative is not using an actual archive, but shortcodes instead to list out a posts (products) loops.

You’ll find this is the same behavior as the “posts page” in WP core. This page is manually set as the posts page in settings (same as shop page), and is then overridden as an archive page rather than an actual page. You just don’t notice this case as much, because themes all adjust for the posts page.

This is probably what you will want: https://developers.google.com/maps/documentation/distance-matrix/start

We integrated with this API in https://woocommerce.com/products/woocommerce-distance-rate-shipping/. Not useful for your situation, but just a use case 🙂

Could you paste a copy of your site’s System Status Report here? You can find it at WooCommerce > Status.