Claudiu Lodromanean

Hi.

If you’re setting the placeholder by attachment ID it should automatically crop/resize to match your store’s catalog/product page settings.

If you’re setting the placeholder by image URL, you’ll want the image to be the same aspect ratio as the rest of your site, as WooCommerce can’t automatically resize/crop it.

Hope this clears things up.

Hi,

A few other people seem to be having this same issue. I’m investigating and following up if a patch is needed at https://github.com/woocommerce/woocommerce/issues/21646.

Thanks.

Hi,

A few other people seem to be having this same issue. I’m investigating and following up if a patch is needed at https://github.com/woocommerce/woocommerce/issues/21646.

Thanks.

You are having some sort of fatal PHP error on your site. If you have error logging you will have to check the error logs to see what the specific error is, otherwise a generic fatal PHP error could be coming from anywhere (plugins, themes, etc.).

If you have WP CLI available you can run the command wp wc update to run the updater. Hope this helps.

Hi,

Products are not currently set up with Preview Update support, so changes to images, etc. wouldn’t have shown up in the preview even if the button was present.

We may add Preview Update support for products and add the button back in the future, but it was removed because it did nothing. Hope this clears things up.

Thanks.

@dielange is there anything in your error logs (if you keep error logs)?

The actual checkout page on your site loads fine and trying to checkout without filling in the info correctly refreshes the page with the missing address info notices. I can’t really test placing a proper order to see the problem, as I’d need to buy something.

Hi,

Are you referring to order notes? Can you explain in more detail which notes are not being received and/or what sort of notes system you have set up? This will help us to be able to recreate the issue so we can see if there is a problem.

Thanks.

Hi,

It got moved a release or two ago and is no longer a top-level tab in the settings. It should be under WooCommerce > Settings > Advanced > REST API. Hope this clears things up.

Thanks.

Hi Pete,

This is due to the WC 3.4.6 security release which created a whitelist of roles shop managers are allowed to edit. Most likely your membership plugin has not updated to add the role to the whitelist yet. You can read more about this at https://woocommerce.wordpress.com/2018/10/11/woocommerce-3-4-6-security-fix-release-notes/

Easiest fix for your situation is to add the code snippet at the bottom of that linked post to your functions.php (or wherever you add code snippets) and change the part where it says “$roles[] = ‘editor’;” to “$roles[] = ‘member'” (or whatever the slug is for the member role the membership plugin adds). Hope this clears things up.

Thanks.

Thanks for the heads-up. We’ll patch this soon. You can follow at: https://github.com/woocommerce/woocommerce/issues/21546

Sounds like you have Geolocate with Page Caching Support enabled. You can turn it off in your WooCommerce settings, but if you are using a page cache (e.g. varnish) users may not get geolocated properly.

You could just use a variable product with attributes for Grip, Shaft, and Club Head. You can also set up custom images for each variation of the product for the preview. No custom development needed. Hope this clears things up. https://docs.woocommerce.com/document/variable-product/

You should be able to use the ‘woocommerce_checkout_fields’ filter to modify the pre-filled values of any of the checkout fields. See: https://github.com/woocommerce/woocommerce/blob/fd722da88ab5c42afe55965773229e33aec74ca8/includes/class-wc-checkout.php#L242 Hope this helps.

If your host is serving cached pages (e.g. with Varnish) this could cause the issue. When the ajax request is made there is a security nonce included with it (https://github.com/woocommerce/woocommerce/blob/84965af5e3b8c3fd92442b4a0765fcc20ce9438b/assets/js/frontend/checkout.js#L289). This nonce is periodically expired and a new one is created. If this nonce has expired you will get the error you are seeing if you try and use it, which would happen if the host was serving cached pages. Hope this helps.