This topic has 8 replies, 4 voices, and was last updated 9 years, 1 months ago ago by Eva Kemp
I have this ecommerce grid fullscreen page
http://lococostyle.com/jewellry/
and I would add my 4 category filter bottons in an other pull-down menu?
How to display them?
thank you in advance
Hello,
Sorry, but your question is unclear. What filter do you want to add and where?
Best regards,
Jack Richardson.
Hello,
I clarify my request:
I need to add 4 filters botton that correspond to my 4 product categories: EARRINGS BRACELETES NECKLACES BACIAMANOS above the shop product grid in this page:
http://lococostyle.com/jewellry/
I want to add them above the text and the divisory black line, on the left side, next to the existanting bottons (Orden Predeterminado and the other two ones) for let that customer can filter all the existanting productos by the avalaible categories product. If doesn’t enter in the same line, I would like to create a different line for them, immediatly under the first filters line.
If I choice the widget sidebar template this 4 filter category bottons automatically appears on the left side, but If I change the template layout in full screen visualization they doesn’t appear more and I need to customize the template.
I hope it’s clearer,
at your disposition for any request
Thank you
Chiara
Hello,
I’ve added Woocommerce Product Categories widget to “Additional Shop Widget Area” in Appearance > Widgets. Please check the page now.
Regards,
Eva Kemp.
That’s it!
Only a detail: why the box area doesn’t adapt automatically at the text width?
How to enlarge the botton width?
thank you in advance
Hello Webacto,
please try following css code:
#woocommerce_product_categories-2 .dropdown_product_cat{
width:228px; margin-top:15px;
}
Regards,
Stan Russell.
Great!
Thank you
Hello,
You’re welcome.
Regards,
Eva Kemp.
Tagged: buttons, category, filter, fullscreen, grid, shop, templates, woocommerce, wordpress
The issue related to '‘how to display category filter bottons in shop grid fullscreen page?’' has been successfully resolved, and the topic is now closed for further responses