thomas.zapor_ktm

The problem was some purchasable variations were able to be selected, but when I selected them it displayed the “unavailable” message. But I have it working correctly now.

I think the problem was some variations were set to “Any” that should not have been.

Thanks for your help.

The code is located in a plugin I developed that adds a bunch of customizations that this client wanted on the single product page.

The ajax threshold IS being enforced correctly, that is not the issue. The problem I am having is that when the ajax variation threshold is set to 100000 — forcing all products to NOT use ajax to find variations — variations that should be purchasable are displaying the message that they are unavailable.

No. I had it in my code, I just didn’t include it on this message.

add_filter( 'woocommerce_ajax_variation_threshold', array($this,  'custom_wc_ajax_variation_threshold'), 10, 2 );

Thanks for the response.

The only variations that are missing prices are the ones the client does not want to be purchasable, that is how he disables unpurchasable variations. The attribute options for those variations are correctly being removed from the selects, but the variations that are available are showing the “unavailable” message.

When I remove the add_action for the function below, the correct variations are purchasable, but the options are are displayed for the unavailable options as well, which is what my client does not want.

Here is the function I am using to set the threshold:

function custom_wc_ajax_variation_threshold( $qty, $product )
    {
        return 100000;
    }

I am working on site for a client who adamantly wants only purchasable attribute options displayed on the dropdowns even though some of his products have several thousand variations.

I used the woocommerce_ajax_variation_threshold hook and set the threshold to 100000. That succeeded at removing the unpurchasable attribute options, but now a lot of variations that should be purchasable are showing as unpurchasable, displaying “Sorry, this product is unavailable. Please choose a different combination.”.

Before I added this filter, all possible attribute options were displaying on the dropdowns. The unpurchasable variations were correctly displaying that message and the purchasable variations worked normally.

The production copy of the site is now running WC 2.2 and I am working on updating to 2.5 on a development copy. This issue only started when I upgraded the development copy to 2.4, the 2.2 production site works fine.

Marking this resolved.

I did see other posts regarding yahoo and gmail addresses, however they were not about the same issue I was having.

After thoroughly dissecting then recreating the forms where I was having the issue, I discovered that the error only happened when I checked the “Use HTML content type” checkbox. When I unchecked that box both gmail and yahoo responses worked fine.

Thanks! I’ll be watching for that new version and will update as soon as it is released.

Do you expect it to be available this week?