wbrubaker.a11n

Howdy ??

You can have different shipping rates based on Country/State/Zip e.g.

But that cannot be adjusted on a per-product basis.

Kind regards,

Howdy ??

If you are unwilling to take the site down for this type of testing then I would suggest a staging site to test on and try to isolate the problem there. Many hosts provide an easy method to do this but if yours doesn’t you might want to look into this plugin: https://www.ads-software.com/plugins/wp-staging/

Kind regards,

Howdy ??

Am I correct that the ‘sold individually’ setting achieves what you want to achieve but you do not want the error message to be displayed? If so, that will require some custom code to remove that particular error message. Here is an example code snippet that will remove that particular message: https://gist.github.com/WillBrubaker/3f868bf669357c01803db2a6bd474582

Kind regards,

Howdy ??

The first thing I would suggest is to go to WooCommerce -> Status -> Tools and press these two buttons:

Then reload the product page.

If that doesn’t help, then the above suggestion of deactivating plugins and switching to a default theme will be the next best step to isolate what is causing this.

Kind regards,

Howdy ??

The default column heading for variation descriptions is “Description”.

Kind regards,

Does that same behavior persist if you temporarily switch to a default theme such as Twenty Seventeen or Storefront? If so, then you would need to contact your theme author for resolution.

Kind regards,

Hi there,

The first thing that jumps out at me in that system status report is that the WooCommerce database version is not the same as the WooCommerce version which is an indication that the database update was not completed after updating to WooCommerce 3.4.3.

I would expect an admin notice to be present with a purple button and a prompt to update the database. If so, can you update the database and see if that helps?

If there is no button, you can force a database update by visiting /wp-admin/admin.php?page=wc-settings&do_update_woocommerce=1

Kind regards,

In the call to add_action you have stated that you would pass one argument to your callback function yet you have have not passed any arguments to the callback function. PHP 7 will error on that so perhaps that’s the problem. You might want to check your error logs.

Howdy ??

One way to do this would be with template overrides. If you are unfamiliar with that, there is some documentation about template overrides Here.

You would need to add a required attribute to each of the fields. Here is the line that outputs the email field https://github.com/woocommerce/woocommerce/blob/3.4.2/templates/myaccount/form-login.php#L91 and the one that outputs the password field: https://github.com/woocommerce/woocommerce/blob/3.4.2/templates/myaccount/form-login.php#L98

Kind regards,

Howdy Stonez,

the product name part of that is what is preventing it from working. The class name is product-name so that would be denoted as .product-name

You can use your browser inspector to find the correct elements to target with CSS and it can also be used to test/preview any CSS changes. Here is an example:

Kind regards,

Howdy ??

The first thing that jumps out at me in that system status report is the PHP version. Many people have experienced significant performance increases by updating to PHP 7. I would suggest working with your host to update the PHP version.

Kind regards,

Howdy ??

I think that there may be a conflicting plugin or possibly a conflict in the theme. How we usually address this type of issue is to have you temporarily switch back to a default WordPress theme such as WordPress Twenty Seventeen Theme or Storefront and disable all plugins except for WooCommerce and the Google Analytics Integration. If that resolves the issue, then re-enable features one-by-one until you find the one that’s causing the conflict.

If none of that helps. perhaps a screenshot of the error in the console would provide more context.

Howdy ??

I don’t know that I understand the issue so let me put it in my own words.

A product does not have reviews enabled but you can still retrieve the reviews via a GET call to the REST API and that seems inconsistent with the experience you have when viewing the same product on the site. Is that correct?

If so, the reason for the difference is that when displaying, the display is conditional upon whether the comments are open on the product (which is the equivalent of the ‘enable review’ checkbox). That conditional statement can be seen in code here: https://github.com/woocommerce/woocommerce/blob/3.4.2/includes/wc-template-functions.php#L1667-L1673

When making a GET request to the reviews API endpoint, you are explicitly asking for the reviews and there is no condition that needs to be met and the reviews will be returned by the REST API handler. This is expected behavior.

Kind regards

Howdy ??

Okay I have reset the endpoints.

Has that resolved the issue?

Do you have any recommendations for a plugin that people can use for “account management, password recovery etc”

All of that functionality is built into WordPress so my recommendation would be to not use a plugin to do it.

Then it seems likely that you are experiencing a bug that was fixed in version 3.4.2. Can you please update and let us know if that doesn’t solve this for you?