Issue with filters only on attributes with predominantly numeric values
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Quote from knco_it on March 18, 2024, 15:31Hi,
We've purchased HUSKY filters, and I'm encountering an issue with the product attribute filters on the shop page: some of the filters work fine, and some don't work at all.
For the product attributes that don't work, there's nothing different about their importation to WooCommerce. The only difference that I can find is that they seem to be mostly numeric values, whereas the filters that work are linked to atttributes with values that begin with an alphabetic character.
I've tried looking everywhere, in many different settings pages, but to no avail. Please can you help me get this working?
Regards,
Hi,
We've purchased HUSKY filters, and I'm encountering an issue with the product attribute filters on the shop page: some of the filters work fine, and some don't work at all.
For the product attributes that don't work, there's nothing different about their importation to WooCommerce. The only difference that I can find is that they seem to be mostly numeric values, whereas the filters that work are linked to atttributes with values that begin with an alphabetic character.
I've tried looking everywhere, in many different settings pages, but to no avail. Please can you help me get this working?
Regards,
Quote from knco_it on March 18, 2024, 15:58If it's of any use in hinting where the issue might be, when selecting a filter value for a filter that doesn't work, the page width is messed up (almost as if the CSS for the page isn't loading properly). The page is displayed narrower than it should be. The page displays correctly for the filters that work.
If it's of any use in hinting where the issue might be, when selecting a filter value for a filter that doesn't work, the page width is messed up (almost as if the CSS for the page isn't loading properly). The page is displayed narrower than it should be. The page displays correctly for the filters that work.
Quote from knco_it on March 18, 2024, 16:07Private information added to ticket.
Private information added to ticket.
Quote from Pablo Borysenco on March 19, 2024, 12:13Hello
please drop me wp-admin access - https://share.pluginus.net/image/i20230222134241.png ->https://share.pluginus.net/image/i20230222134615.png - I will check it
Hello
please drop me wp-admin access - https://share.pluginus.net/image/i20230222134241.png ->https://share.pluginus.net/image/i20230222134615.png - I will check it
Quote from knco_it on March 19, 2024, 15:31Hi,
Please verify the ticket information.
Regards,
Hi,
Please verify the ticket information.
Regards,
Quote from Pablo Borysenco on March 20, 2024, 12:24Hello
this is a slug conflict.
please try change this slug beam-angle to beam_angle
Hello
this is a slug conflict.
please try change this slug beam-angle to beam_angle
Quote from knco_it on March 22, 2024, 15:00Hi Pablo,
Thanks for taking a look.
Before I make any modifications, could you explain more specifically what you mean by a slug conflict, please? I've taken a look at all of the WooCommerce product attributes, and I cannot see any duplicate slugs. For example, there is only one 'beam-angle' slug.
Are you perhaps referring to the slugs that HUSKY generates? If that is the case, how can I modify the HUSKY slugs?
Regards,
Hi Pablo,
Thanks for taking a look.
Before I make any modifications, could you explain more specifically what you mean by a slug conflict, please? I've taken a look at all of the WooCommerce product attributes, and I cannot see any duplicate slugs. For example, there is only one 'beam-angle' slug.
Are you perhaps referring to the slugs that HUSKY generates? If that is the case, how can I modify the HUSKY slugs?
Regards,
Quote from knco_it on March 22, 2024, 15:09I would add that the default slugs created by WooCommerce when importing products are in the format:
Name: This is an attributeSlug: this-is-an-attributeIf you are indeed referring to the HUSKY generated slugs, is this not effectively a bug? What I mean is, if HUSKY uses exactly the same logic by default to generate slugs based on an attribute name as WooCommerce itself does, and this creates a slug conflict, surely HUSKY should be using different logic to generate a slug?
Regards,
I would add that the default slugs created by WooCommerce when importing products are in the format:
Name: This is an attribute
Slug: this-is-an-attribute
If you are indeed referring to the HUSKY generated slugs, is this not effectively a bug? What I mean is, if HUSKY uses exactly the same logic by default to generate slugs based on an attribute name as WooCommerce itself does, and this creates a slug conflict, surely HUSKY should be using different logic to generate a slug?
Regards,
Quote from Pablo Borysenco on March 25, 2024, 10:37Hello
You have two attributes with the same part of the slug. An example: beam-angle and beam
Problem reading search queries in URLs: product_search24/beam-angle-104/ - the filter looks for a match with the attribute: /beam-angle-104/ And then the search query will look like: get products where beam=angle-104
Hello
You have two attributes with the same part of the slug. An example: beam-angle and beam
Problem reading search queries in URLs: product_search24/beam-angle-104/ - the filter looks for a match with the attribute: /beam-angle-104/ And then the search query will look like: get products where beam=angle-104
Quote from knco_it on March 25, 2024, 11:27Hi Pablo,
Ah, I see. Thank you for the update.
Seeing as both these slugs are valid within WooCommerce, can I make these work by activating an option within HUSKY? For example a search URL:
FROM => product_search24/beam-angle-104 TO => product_search24/?beam-angle=104...or would a future update of HUSKY be able to take account of this? I find it hard to see this as not being a bug, considering the two attributes work fine within the confines of WooCommerce itself.
King regards,
Hi Pablo,
Ah, I see. Thank you for the update.
Seeing as both these slugs are valid within WooCommerce, can I make these work by activating an option within HUSKY? For example a search URL:
FROM => product_search24/beam-angle-104 TO => product_search24/?beam-angle=104
...or would a future update of HUSKY be able to take account of this? I find it hard to see this as not being a bug, considering the two attributes work fine within the confines of WooCommerce itself.
King regards,
Quote from Pablo Borysenco on March 25, 2024, 13:02You can disable SEO URL - And everything will work correctly
In fact, these attributes are absolutely correct, but attributes with the same slug will cause a conflict in the SEO URL (as part of the url)
You can disable SEO URL - And everything will work correctly
In fact, these attributes are absolutely correct, but attributes with the same slug will cause a conflict in the SEO URL (as part of the url)
Quote from knco_it on March 25, 2024, 13:22Pablo,
Ahh! That's fantastic! Thank you for your help.
Kind regards,
Pablo,
Ahh! That's fantastic! Thank you for your help.
Kind regards,