lcaseres

Hi Phil, hope you are well.

We have noticed that the last release of Age Gate included the integration for Husky filters:

3.4.0
Added – Integration for WOOF/Husky

We have installed the last version of both plugins in a test environment but weren’t able to make it work.
Can you provide any documentation or explanation about the way it works?

Here is our use case:

• We’ve set Product Category “Category 1” as age restricted.
• We navigate the standard woo product category and the Age Gate shows up properly.
• We navigate the Shop page which shows the Husky filters on its sidebar. Then, we select “Category 1” from the Husky filters but no Age Gate is shown.

Please let me know if you need any aditional detail.

Thanks very much in advance.

Hi @mediawebster,

Thanks for your reply!

We need to show the Age Gate form when the user selects a category filter corresponding to an age restricted categoty. Here is the use case:

1. The user navigates a product category page, let say: /product-category/clothing/
2. The website shows the product category page which includes a left sidebar with Husky filters. Whithin those filters there are child categories of “clothing” and some of them are age restricted. Let say we have an “adult” child category.
3. The user selects the “adult” child category from the Husky filters.

• Actual behavior: Husky shows “adult” products without restriction. The URL is set as: /product-category/clothing/?swoof=1&product_cat=adult&really_curr_tax=475-product_cat.
• Expected behavior: The Age Gate form is displayed.

Notice that if the user navigates directly the standard woocommerce category at /product-category/clothing/adult then the Age Gate form is shown. I suppose this is because the user is in the standard Woocommerce URL. Otherwise, when navigating the same category from Husky filter, the URL is different (/product-category/clothing/?swoof=1&product_cat=adult&really_curr_tax=475-product_cat) and not recognised by Age Gate as a restricted category.

Please let me know if I’m not being clear.

Thanks in advance for your help.

Hi there,

Same issue here.

Any ideas will be appreciated.

@qtwrk,

Sorry for that. Here is the new ticket number: #201429

Thanks!

Hi @qtwrk!

I’ve created the support ticket: #544352

Look forward any suggestion.

Thanks in advance!

• This reply was modified 11 months, 1 week ago by lcaseres.

Hi @qtwrk.

Here it is: NMAUAUDH

Thanks very much.

Hi @qtwrk.
Thanks for your answer.

I’ve already checked the option Cache -> Woocommerce -> vary for mini cart but it is still behaving as I described above. Any other idea? Is there any detail I could provide to help you evaluate the problem?

We’re referring to the message that appears in WooCommerce when we try to add more quantities to the cart than are available in stock. The message displayed is: “You cannot add that amount of ‘product name’ to the basket because there is not enough stock (X remaining).“

The issue is that when we have Litespeed cache enabled, this message does not show up, and we are looking for a way to ensure that this message is excluded from Litespeed’s cache.